What is the recommended approach for writing backward compatible database migrations when updating schema versions across multiple microservices simultaneously
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
What is the recommended approach for writing backward compatible database migrations when updating schema versions across multiple microservices simultaneously
1 real search · 1 real-search pass
backward compatible database schema migrations expand contract pattern microservices zero downtime official documentationGoogle ↗
OBSERVED
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 1 queries…
Searches and sources
ChatGPT1 real searches · gpt-6
backward compatible database schema migrations expand contract pattern microservices zero downtime official documentation Google ↗
- Writing Database Migrations for Zero-Downtime Upgrades · docs.openstack.org
- How to migrate data with Prisma ORM using the expand and contract pattern · prisma.io
- Rollback · migration.minimumcd.org
- Shared-database-per-service pattern · docs.aws.amazon.com
- Sync Schema Migrations Across Microservices · zero-downtime-schema.com