HA Coffee
summary
Home coffee becomes treated as infra with a concrete coffee service architecture: front-end client, backend services, and a cache that fails because a home UPS cannot run compressor-based espresso machines. Generator or Tesla Powerwall are dismissed as too costly or illegal, so design refactors to use gas stovetop devices; device interfaces mismatch until a translation layer called a stove keyline is added. Result is an active–passive load balancer: espresso on mains, mocha maker on gas, implemented as Go example code teaching interfaces and it works.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 0:33High availability defined
- 1:24Coffee as critical system
- 2:04Architecting the coffee system
- 2:48Refactoring and implementation
- 3:41Lessons and conclusion
related talks
45m12-Factor, Cloud Native Enterprise Java Applications
33mBuilding an Enterprise-ready Lambda Experience (with Hands-On Demo)
33mSmart Green Computing Cloud Native Operations
59mInfrastructure as Actual Code
41mLiving on the Edge (Service)
50mCarbon-Aware Computing: Measuring and Reducing the Carbon Intensity of Software
50mBuilding an Application Platform: Lessons from
22mInnovation enabling - for Bosch eBikes