Backend Study Lab · Games
← All games

Partition Tradeoff Commander

Choose explicit consistency or availability behavior for concrete network-partition scenarios.

Concept
CAP theorem and partition-time tradeoffs
Difficulty
Advanced
Play time
7-10 minutes
Path
Database Reliability

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

Partition Tradeoff Commander is focused practice for CAP theorem and partition-time tradeoffs. It explains why each answer is safe, risky, or production-ready.

Turn CAP slogans into explicit product and data decisions.

Learning objectives

  • Describe partition-time choices concretely.
  • Match product invariants to availability decisions.
  • Separate CAP from normal latency tradeoffs.

How to play

  1. Read the product invariant.
  2. Choose behavior during the partition.
  3. Review the exact tradeoff rather than a product label.

Scoring

  • Correct decisions add 250 points.
  • Misses enter local review.
  • A perfect run scores 1,000.

Backend concept notes

CAP describes the choice forced by a network partition.

Real designs state which operations remain available and which invariants may relax.

Common mistakes

  • Repeating pick any two.
  • Labeling a database permanently CP or AP.
  • Ignoring normal-operation latency.

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.

Scaling Intermediate

Load Balancer Challenge

Route simulated traffic across backend servers using round robin, weighted round robin, least connections, and random strategies.

Time
6-10 minutes
Concept
Load balancing strategies
  • Production Reliability
  • load balancing
  • scaling
  • latency
Play Load Balancer Challenge
Databases Advanced

Replica Consistency Router

Route reads across primary and replicas while respecting lag, freshness contracts, failover, and workload isolation.

Time
8-12 minutes
Concept
Read replicas and consistency-aware routing
  • Database Reliability
  • replication
  • consistency
  • routing
Play Replica Consistency Router
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.

Is partition tolerance optional?

Distributed systems must define behavior when communication fails.

What does PACELC add?

It also frames latency and consistency tradeoffs when no partition exists.

Leaderboard

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

Loading leaderboard...

    Finish the game to load your latest local score.