Food for Thought: What Restaurants Can Teach Us about Reliability
summary
Compares restaurant failures — late plates, wrong or burnt food, incorrect bills — to SRE symptoms and maps concrete fixes: add staff to scale, hire runners for delivery (routing), use an expediter to check correctness, simplify or remove flaky dishes (refactor or deprecate), and balance seating (load balancing). Describes kitchen practices that translate to ops: mise en place for preparation, the brigade system as role-based incident command, and publicly available recipes as a run book for on-call consistency.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:50Restaurant Failures
- 3:30Restaurant Components
- 5:55Complex Systems
- 6:35Component Complex Systems
- 6:52The Floor
- 9:15Food Delivery
- 14:26Bar
- 14:43Bar vs Floor
- 18:20Multiple User Classes
- 22:21The Kitchen
- 24:39Hierarchy
- 26:00Formalized Communications
related talks
37mImplementing SRE in a Telco with Reliability Enhancing...
25mUnleashing the potential of SRE for modern operations
42mDemystifying SRE and DevOps
30mImproving Reliability w/ Error Budgets & SRE
30mHow Did Things Go Right? Learning More from Incidents
33mThe evolution of farm to table and code to customer
43mLearning from Firefighters to Improve Systems Reliability
47mPersistent SRE Antipatterns: Pitfalls on the Road to Creating a Successful