↑↓ move · ↵ open · esc close
3Back to the workbench
Everything filed under database — essays, notes, playbooks and signals.
Replicas fix read saturation and nothing else. Here is the exact point where adding another one stops paying for itself.
The cheapest way to keep a shared database from becoming a distributed monolith.
When read load is the bottleneck, the cheapest correct answer is almost never sharding.