Use Google Cloud Platform Cloud SQL when you want the stack to include the database connection service for your app while the actual database server runs as a managed service outside the cluster.
That lets teams choose providers per environment, offload day-to-day database operations, and keep the same app-side connection model across development, staging, and production. If you deploy this stack to Google Cloud Platform Kubernetes Engine (GKE), you can keep the managed database in the same provider network as the cluster for faster connectivity and tighter security boundaries.
Managed database providers are useful only when they fit the way the stack connects apps to data. This is what Google Cloud Platform Cloud SQL changes for teams using the Drupal 11 stack.
The external database services in this stack are connection services: they keep connection settings, secrets, and service wiring in one place so your app can connect to a managed database server on Google Cloud Platform Cloud SQL.
Point each environment to the managed database provider that fits it best without rebuilding the stack connection model.
When this stack runs on Google Cloud Platform Kubernetes Engine (GKE), you can keep the managed database server on the same provider for faster network connectivity and a tighter security posture.
Database connection services in this stack
These services are included in the stack to connect your app to a managed database server on Google Cloud Platform Cloud SQL.
Other managed database providers for this stack