Engineering Resilience at Scale; Lessons from a Distributed Systems Transformation
summary
A large payments platform migrates to an active-active YugabyteDB multi‑data‑center design to remove single points of failure and serve millions of transactions daily while keeping operational overhead low. The project uses phased POCs, CRDTs for cross‑site consistency, routing and caching layers, and automation so the system absorbs failures and failed twice then reached production readiness within a year. Observability, compatibility with existing stacks, and phased rollouts prove decisive for success.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker intro
- 2:43Problem statement and challenges
- 6:41Success criteria and architectural objectives
- 8:50Active-active architecture principles
- 12:22Phased transformation approach
- 13:50Business impact and scalability
- 15:20Lessons learned and critical factors
- 16:25Observability and migration planning
- 17:09Conclusion and Q&A
related talks
29mEnterprise Scale: How a Distributed Architecture Can Deliver Scale and Resilience
34mBuilding High Resiliency into Digital Solutions
25mBuilding a highly scalable system to assure Business Resilience
01h 03mPatterns for Resilient Architecture
23mFireside Chat with Fiserv: Understanding Operational Requirements of Distributed SQL
18mScaling APIs to Billions: Extreme-Scale Reliability
40mThe Art of Embracing Failure at Scale
24mFailure is Not an Option: Highly Available Distributed SQL