Complexity: The Crucial Ingredient in Your Kitchen
summary
Draws a direct line from the Challenger O‑ring failure to microservice failures: a cache hides read pressure until Cassandra slows and Cassandra returning a quorum error (404) makes a downstream service crash. Argues redundancy can mask faults, not fix them, and promotes proactive testing via chaos engineering: facilitation of experiments to uncover systemic weaknesses. Recommends concrete practices—Netflix’s chaos team, feature flags, blue‑green deploys, CI/CD, and regular team practice to build reversible, improvable systems.
AI-written summary · about
chapters (7)
- 0:00Intro
- 4:37Microservice Architecture
- 7:56Redundancy
- 12:48Avoiding Risk
- 14:48The Solution
- 17:54Navigating Complexity
- 19:58Economics of Complexity
related talks
29mDeprecating Simplicity
34mAntics, Drift, and Chaos
01h 04mPredictably Unpredictable
03mDeveloping a Chaos Architecture Mindset
38mChaos Engineering
32mClear the ring for Chaos Engineering
41mOnce Upon a Vulnerability: Building Resilience in a Chaotic World
43mBetter Software Development Systems through Stress