Distributed of systems and teams
summary
Argues that teams must be engineered for consistency, availability and fault tolerance just like distributed systems and that complexity is conserved not removed so microservices shift failure modes. Recommends concrete tools and patterns: containers with image hygiene, Kubernetes for orchestration only when it solves a real problem, deployment helpers like Helm 3 and Draft, event tooling like Brigade, observability with Honeycomb for unknown unknowns, and multi‑cloud, extensible platforms with auto‑remediation and seamless rollouts.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:48Bridget Kromhout
- 6:18CAP theorem metaphor time!
- 7:54containers solve problems
- 11:26Helm Find, share, and use software built for k8s
- 17:20orchestrating containers: a tool, not a goal
related talks
37mKnee Deep in Microservices
57mBuilding Systems that are #neverdone
45mContinuously delivering containerized, highly available microservices
27mThere and Back Again
14mKeynote: Open Source & Operational Excellence
21mAutonomous Teams
51mDeploying And Scaling Microservices
32mOps in the Time of Serverless Containerized Webscale