You're working at "RwandaPay" — a fast-growing fintech processing thousands of transactions per second. Your caching layer (Redis) just crashed during peak hours. The result? 78,000 failed transactions. $450,000 lost.
Your CTO says: "Build me a caching system that CANNOT lose data. Even if Redis dies. Even if the network splits. Even if servers catch fire. GO."
Build a distributed, fault-tolerant caching system with these impossible requirements:
Core Requirements
Requirement Description Weight
No Single Point of Failure System works if any 2 nodes die 30%
Zero Data Loss Every cached write survives node failures 25%
Self-Healing Automatically recovers without manual intervention 20%
Eventual Consistency Within 5 seconds after healing 15%
Benchmark 10,000 ops/sec on consumer hardware 10%
Top comments (0)