Why use Kafka as a write-ahead log for a key-value store?
Writes are first appended to a durable ordered log, one partition per shard, and each replica applies them in order. That smooths write spikes, gives every replica the same sequence for eventual convergence, and lets any replica serve reads without a leader.
Answered in
Serving Derived Data at Scale: From a Read-Only Store to a Unified Key-Value EngineThree generations of a derived-data store: read-only files, a batch plus real-time merge, then hash shards, a Kafka log and delta bulk loads.
Read the full analysisOther questions this article answers
More system design & architecture questions
- What is the architectural difference between an API Gateway and a Reverse Proxy?
- When should an architecture use Layer 4 instead of Layer 7 load balancing?
- How do edge ingress layers prevent backend cascading thundering herds?
- What algorithm is best for sticky sessions without breaking even distribution?
- How can a CDN improve performance for dynamic requests?
- What is the hardest part of operating behind a CDN?
- How can a CDN help with traffic surges or DDoS attacks?
- What is the difference between a Push CDN and a Pull CDN?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design & Architecture beat.