Zero Data Loss at Scale
summary
Claims a production system that achieves zero data loss during a regional outage by combining message replication across regions, replay-based recovery and snapshot restores. Architecture uses a message queue with persisted transaction logs, quorum writes to multiple replicas, and peer‑assisted rebuilds for failed nodes. Case study reports successful recovery with end‑to‑end message tracking and monitoring; performance tradeoffs favor eventual consistency for throughput while prioritizing durability and measurable SLA outcomes.
AI-written summary · about
chapters (12)
- 0:00Introduction to Microservice Architecture
- 0:25Understanding Asynchronous Systems
- 1:54Challenges in Distributed Systems
- 2:43Impact on Site Reliability Engineering (SRE)
- 3:45Preventing Data Loss
- 4:14Advanced Recovery Techniques
- 4:56Distributed Acknowledgement Protocol Design
- 6:06Standardizing Message Formats
- 6:56Performance Optimization Strategies
- 8:58Consistency vs. Performance Trade-offs
- 10:18Case Study and Key Takeaways
- 11:13Conclusion
related talks
29mMulti Active-Active and disaster recovery with MongoDB database center
45mChasing unicorns : 0 dataloss and 99.999% availability
30mResilience strategies to level up your workloads
47mDisaster Recovery Strategies for SQL Server
47mDatabase Resiliency
47mDisaster Recovery Strategies for SQL Server
24mFailure is Not an Option: Highly Available Distributed SQL
32mActive Data Guard: Disaster recovery tips and tricks
