Q: Serverless architecture on GCP and data residency concern In general any cloud service provider, GCP in this context, is it not relevant and mandatory for Google to specifically allow consumers to choose data residency and data processing region option for all services? Else serverless option will have serious adoption issue. Please clarify.

A: Google Cloud have two types of the products available: that have specified location and available globally.
You can deploy resources in specific location, multi-regional for:


*

*Compute: Compute Engine, App Engine, Google Kubernetes Engine, Cloud Functions

*Storage & Databases: Cloud Storage, Bigtable, Spanner, Cloud SQL, Firestore, Memorystore, Persistent Disk...

*BigData & Machine learning: BigQuery, Composer, Dataflow, Dataproc, AI training,

*Networking: VPC, Cloud Load Balancing,

*Developer Tools...


Following products are available only globally: Networking, Big Data Pub/Sub, Machine Learning like vision API, Management Tools, Developer Tools, IAM.
For detailed list please check Google Cloud Locations Documentation
Even if the product is available globally, for example PubSub: it is possible to specify where messages are stored.
If the data in transit are the concern, you have to be aware that Google Cloud Platform uses data encryption at Rest. It consists on several layers of encryption to protect customer data.
