AdvancedPrincipalDistributed Systems & Scale65 minutesPro answer

SDV-006

Rebalance stateful shards while live traffic keeps mutating them

Move ownership and state under continuous writes using epochs, snapshot-plus-log transfer, validation, and a rollback that cannot create split brain.

Data MigrationZero DowntimeConsistencyRollback

Interview prompt

Problem context

A stateful service has 256 shards, uneven growth, and several hot partitions. Adding nodes requires moving terabytes while requests continue. Pausing writes violates the availability target, and previous manual moves caused stale writers and divergent data. Design automatic shard movement.

Skills being evaluated

state transferfencingonline migrationcontrol-plane correctness

The full reasoning guide is part of Pro

The scenario and evaluation focus above remain public. Pro unlocks the structured answer, trade-off analysis, follow-up probes, common weak answers, rubric, related reasoning, and any architecture diagram.

Sign in to continue

What the full guide covers

Clarify the decision
Establish scale assumptions
Functional and non-functional requirements
High-level architecture
Data model and flow
Consistency and transaction boundaries
Failure modes and recovery
Security and privacy
Observability and SLOs
Capacity and cost
Alternatives and trade-offs
Evolution and migration
What Staff and Principal candidates should emphasize