Backend Study Lab · Games
← All games

Schema Migration Runbook

Choose safe zero-downtime database migration steps for expanding schemas, backfilling data, rolling out indexes, enforcing constraints, and recovering from failures.

Concept
Zero-downtime schema migration planning and expand-contract releases
Difficulty
Intermediate
Play time
6-9 minutes
Path
Data & Performance

Interactive scenario

Playable game area: Make the next backend decision

Use the controls below. Feedback appears immediately and final scores stay in this browser.

Concept notes

Why this decision matters

Schema Migration Runbook is focused practice for Zero-downtime schema migration planning and expand-contract releases. It explains why each answer is safe, risky, or production-ready.

Schema migrations are where tidy local SQL meets messy production reality. This game helps you rehearse the deployment order that keeps both old and new application versions alive while data moves underneath them.

Learning objectives

  • Apply expand-contract thinking to columns, renames, indexes, and constraints.
  • Plan backfills that avoid unnecessary locks and production load spikes.
  • Explain why schema changes must be compatible with mixed application versions.

How to play

  1. Read the migration goal and production constraint.
  2. Choose the next safest runbook step.
  3. Use the feedback to learn why deploy order matters as much as SQL syntax.

Scoring

  • Safe migration steps add points and streak bonuses.
  • Risky steps explain what could break during a mixed-version deploy.
  • Your best migration safety score is saved locally.

Backend concept notes

Production migrations are distributed systems problems in disguise: old code, new code, old data, new data, replicas, locks, and retries can overlap.

Expand-contract releases add compatible schema first, move code gradually, backfill safely, validate, and only then remove old fields or enforce stricter constraints.

Common mistakes

  • Renaming or dropping a column while old app versions still use it.
  • Running huge backfills or index builds in the most blocking mode during peak traffic.
  • Adding constraints before all writers and old rows satisfy them.
  • Treating rollback as simple even after destructive schema changes.

Review misses from this game

Related Backend Study Lab tools

Use tools from the main site when you want to inspect real inputs.

Keep practicing nearby backend concepts while the mental model is fresh.

Reliability Intermediate

Observability Incident Triage

Triage production incidents by choosing useful metrics, logs, traces, queue signals, database evidence, request ids, and alerting strategies.

Time
6-9 minutes
Concept
Production observability, incident triage, metrics, logs, traces, and alerts
  • Production Reliability
  • observability
  • incidents
  • metrics
Play Observability Incident Triage
Databases Intermediate

SQL Index Quest

Choose the best database index for simplified schemas and queries while learning full scans, covering indexes, sort avoidance, and composite order.

Time
7-10 minutes
Concept
Database indexing and query performance
  • Data & Performance
  • Algorithmic Reasoning
  • SQL
  • indexes
  • performance
Play SQL Index Quest
Databases Advanced

Transaction Isolation Arena

Defend database invariants from concurrent requests by choosing transactions, locks, constraints, snapshot reads, and optimistic concurrency.

Time
7-10 minutes
Concept
Database transactions, isolation anomalies, locks, and invariant protection
  • Data & Performance
  • Database Reliability
  • SQL
  • transactions
  • isolation
Play Transaction Isolation Arena

FAQ

Short answers for how this game fits backend interview and study practice.

Why not put every migration in one deploy?

One large deploy couples application behavior, data shape, and DDL locks. Smaller compatible steps are easier to observe, pause, and recover from.

Do all databases support the same online migration features?

No. The game teaches the pattern. Production runbooks still need database-specific checks for locks, validation, concurrent index support, and replication impact.

Leaderboard

Top 10 scores for the current ruleset. No account required.

Loading leaderboard...

    Finish the game to load your latest local score.