Outlines the Risks Surrounding Distributed Systems
summary
Outlines that the biggest risk is unchecked complexity as distributed systems scale, recommends carving regular time to reduce overhead rather than hoping for a cleanup day, and gives on-call details: 5+ years on call with a 3-minute SLA and 16-hour rotations. Stresses concrete tooling: monitoring and automation are mandatory, and highlights config and runtime techs like chef puppet salt and Docker while arguing small iterative deployments beat paralysis from “perfect” architecture planning.
AI-written summary · about
chapters (5)
related talks
33mWhy Are Distributed Systems So Hard?
41mCultivating Architecture in an Agile World
47mPersistent SRE Antipatterns: Pitfalls on the Road to Creating a Successful
46mPracticalities of Productionizing Distributed Systems
01h 39mPostOps: A Non-Surgical Tale of Software, Fragility, and Reliability
44mYou build it, you run it
29mPractical distributed systems: Building for the real world with chaos engineering
01h 02mTools for simplified large scale systems