I haven&#x27;t actually tried it out yet (about to) , but just by reading the instructions on deploying, it looks like you stage your code in a GCS bucket or on a Git repository (Google Cloud Source), so I think your local data would refer to any files in that bucket&#x2F;repository along with your code.<p>*edit note: looks like you can definitely add more files via the package.json and import them as node modules, but I wouldn&#x27;t rely on reading and writing from the file system.<p>As for persistency, if it&#x27;s just Javascript code you can install node modules to accomplish what you want including talking to those cloud APIs. Unfortunately Bigtable might be the exception since I&#x27;m not sure if there&#x27;s a good nodejs client yet (Bigtable only supports gRPC, not REST), but you could use Cloud Datastore instead.<p>Firebase will also be a very popular choice for persistence. Cloud Functions naturally complements Firebase to complete Backend-as-a-Service. The hope of Firebase is you don&#x27;t need a server at all, but sometimes you have logic that really doesn&#x27;t belong on a client (background jobs, &quot;master&quot; logic). Cloud Functions can fill in those gaps.<p>Firebase:
<a href="https:&#x2F;&#x2F;www.firebase.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.firebase.com&#x2F;</a><p>hand-rolled clients nodejs clients for google cloud apis:
<a href="https:&#x2F;&#x2F;github.com&#x2F;GoogleCloudPlatform&#x2F;gcloud-node" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;GoogleCloudPlatform&#x2F;gcloud-node</a><p>auto-generated nodejs clients for google apis:
<a href="https:&#x2F;&#x2F;github.com&#x2F;google&#x2F;google-api-nodejs-client" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;google&#x2F;google-api-nodejs-client</a><p>disclosure: work for GCP