How did Netflix eliminate data drift between Cassandra and Elasticsearch?
Netflix identifies datastore entropy, including Cassandra and Elasticsearch, as a problem the WAL is intended to address. The post describes a general configurable delivery abstraction and use cases; it does not claim the WAL universally eliminates dual writes or guarantees that every pair of stores converges.
Answered in
Netflix’s Distributed WAL: One API for Retries and ReplicationNetflix's Data Gateway WAL uses configurable Kafka and SQS backends for delayed retries, EVCache replication, and eventually consistent multi-partition writes.
Read the full analysisOther questions this article answers
More systems architecture questions
- How did Linear choose to implement multi-region hosting?
- How does Linear route requests to a workspace’s region?
- Does hosting workspace data in Europe by itself guarantee GDPR compliance?
- How did Reddit compare a new Go read endpoint with its Python endpoint?
- Why did Reddit use sister datastores for comment writes?
- What performance result did Reddit report?
- What did Shopify test ahead of BFCM 2025?
- What is Genghis in Shopify’s readiness program?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Systems Architecture beat.