Deprecating Simplicity 3.0
summary
Shows a live microservice visualization called visceral visualization and gives concrete failure stories: a Java library with a memory leak introduced in February causes instances with 40‑minute boot times to fail across an API cluster that was overprovisioned by 50% (repeat outage two weeks apart), a staging Kafka still wired to production causes a six‑minute outage during a game day, and a Cassandra quorum returning 404 makes a downstream service crash. Recommends Chaos Engineering as proactive experiments, using game days, feature flags, blue‑green and canary deploys to reveal safety margins and prefer faultless, organizational learning over root‑cause hunts.
AI-written summary · about
chapters (8)
- 0:00Start
- 17:43Business Logic
- 19:45Root Cause
- 24:05Conduct Faultless Learning Reviews
- 26:35Redundancy
- 44:07KMO: Kitchen Model of Organization
- 46:02Provide opportunities for teams to practice working together.
- 46:33Tools don't create reliability. Humans do.
related talks
32mClear the ring for Chaos Engineering
19mVisualizing cloud architectures in real time with d3.js
26mBreaking Systems for Resilience
31mHundreds of Microservices without breaking your APIs
29mApps, Stacks, and Frameworks: Avoiding “Shiny Object” Syndrome
26mLightning Talk: Think Like a Chaos Engineer: Simulating User Anomalies the Litmus Way
28mThink Backstage! Beyond Plugins
55mJust-in-time Architecture