Why this matters
- Meta, Apple, Slack, and AWS use cell-based architectures at scale for blast radius and capacity planning.
- Cells turn "how big can one cluster get?" into "how many cells do we need?" — a linear scaling question.
- ShardPay routes merchants to home cells; a cell outage affects ~25% of merchants, not the entire fleet.
- Interviewers at staff level ask you to design cell routing, handle cell migration, and justify shared vs cell-local services.
Anatomy of a ShardPay cell
Each cell is a complete vertical slice: ingress load balancers, API gateway, transfer orchestrator, ledger shards, Kafka cluster, and observability stack. A cell serves roughly 300,000 merchants with no runtime dependency on other cells for the transfer hot path.
Cell 1 holds merchants M-000001 through M-300000. Cell 2 holds M-300001 through M-600000. Cross-cell transfers exist (merchant in cell 1 pays merchant in cell 2) but are async sagas with higher latency budget — not the common case.
Key points
- Cell — a self-contained deployment unit with full stack for a subset of tenants. ShardPay's cell 3 runs 847 pods, 12 ledger shards, and a dedicated 9-broker Kafka cluster.
- Cell router — maps tenant to home cell at the edge. ShardPay's router uses consistent hash on
merchantIdwith virtual nodes for even distribution. - N+1 cell capacity — spare cell ready to absorb traffic from a failed cell. ShardPay maintains cell 5 as warm standby at 10% synthetic traffic for continuous validation.
- Shared services — identity, billing, merchant onboarding run globally with smaller blast radius and stricter SLOs. ShardPay accepts that identity outage blocks new logins but not in-flight transfers (tokens cached at gateway).
The rest of this guide is part of Pro
Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.
Still to come · 2 sections
- Routing and migration
- Shared vs cell-local decisions
Test yourself
Answer these before moving on — recall is what makes it stick.