Chaos Engineering at Citi Bank
summary
Converts L2 production support into an SRE/citability engineering team and adopts chaos engineering as a core discipline, running monthly production game days with Ansible one‑touch failover to exercise a full datacenter outage and measure thresholds — example: 100 TPS over 30 minutes with a high‑CPU attack invoked at the 10‑minute mark — holds quarterly Wheels of Misfortune role‑plays for incidents and cyber scenarios, integrates Gremlin with OpenShift, uses Chaos Monkey for random instance kills and an in‑house AP Army, and captures automated measurements while working toward automated normalization.
AI-written summary · about
related talks
41mClear the ring for Chaos Engineering at Vertrieb Deutsche Bahn!
18mChaos Engineering: Break It On Purpose
52mGetting started with Chaos Engineering
57mChaos Engineering Primer
27mChaos Engineering: The Path to Reliability
48mChaos Engineering: The Path to Reliability
14mBenefiting from chaos engineering at Capital One (PRT026)
36mChaos Engineering
