You are deploying a critical application with a stateless, containerized frontend on Cloud Run and a Cloud SQL for PostgreSQL backend. The application experiences unpredictable traffic spikes, and the

Question

Options

• APackage the database schema migration script within the container to be executed on every
• BConfigure the CI/CD pipeline to use the :latest container tag for deployments, with database
• CSeparate CI/CD pipelines for database schema migrations from application deployments. When
• DUse a single CI/CD pipeline that first applies database schema changes and then deploys the

• A
  6% (4)
• B
  26% (16)
• C
  55% (34)
• D
  13% (8)

Explanation

Following SRE and DevOps best practices, database schema migrations should be managed separately from application deployments to ensure safe rollbacks and reduce coupling. Using gradual traffic splitting for Cloud Run allows canary-style rollouts - gradually shifting traffic to the new revision and instantly reverting to the previous one if issues arise. This approach minimizes risk during spikes, enables rapid rollback, and keeps schema changes controlled and auditable in their own pipeline.

No community discussion yet for this question.