Mitigating Against Large Scale Systemic Failures in E-Trading
summary
Availability depends on time of day: an outage at market open causes outsized P&L, regulatory and reputational damage. Real incidents include London and US exchanges example and a hardware failure Dec 23 that stopped trading twice; systemic causes are latent bugs, Night Capital cascading orders from version skew, poison‑pill market feeds and volatility spikes. Defenses used are multi‑location, staggered deploys and segregated flows, plus architectural fixes: reduced blast radius via service variants, isolated core with graceful degradation and exercised cross‑system failovers.
AI-written summary · about
chapters (7)
- 0:00E-trading system constraints
- 1:21Incident impact on trading
- 2:43Operational resilience strategies
- 4:06Hidden risks in trading systems
- 6:52Debugging latent failures
- 7:34Architectural failure reduction
- 9:58Summary of mitigation efforts
related talks
01h 06mPatterns for scalability and availability in (trading) systems
51mExperience Developing, Debugging, and Deploying a Hot-Swap Trading System
29mBuilding Resilient Systems
30mWhat Breaks Our Systems: A Taxonomy of Black Swans
20mMarket Data: Applying SRE Techniques to Legacy Designs
31mWhat Breaks Our Systems: A Taxonomy of Black Swans
42mArchitecting for Failures in Microservices
41mTracing Real-Time Distributed Systems