Cloud chaos and microservices mayhem

on YouTube ↗38m

" summary

Cloud habits that were fine ten years ago become costly or fragile: a personal Kubernetes cluster burns about €1,000/month as a zombie, a study of ~16,000 servers finds 25% doing no useful work, and microservices often turn into a distributed monolith when a shared data model couples services. The demo builds a BFF + Node front end and uses Pact consumer-driven contract tests: renaming the backend field (torso → stomach) breaks the UI, Pact generates a contract and the provider test fails, catching the regression with little code.

AI-written summary · about

" chapters (7)

1. 0:00Start
2. 6:47release sched
3. 8:30modularity
4. 9:51microservices are not the goal
5. 10:27wishful mimicry
6. 17:06How to test a fire alarm?
7. 17:58contract testing a fire alarm

" related talks

• 34mCloud Chaos and Microservices MayhemHolly Cummins · Jfokus 2021
• 28mCloud Chaos and Microservices MayhemHolly Cummins · jLove 2020
• 48mCloud Chaos & Microservices MayhemHolly Cummins · GOTO Copenhagen 2022
• 41mCloud Chaos & Microservices MayhemHolly Cummins · GOTO Amsterdam 2022
• 51mMicroservices and Microfrontends: Scaling, Learning, GrowingLofi Dewanto, Patricia Erdelen · JCON EUROPE 2026
• 55mMicroservices, Where Did It All Go WrongIan Cooper · NDC London 2025
• 40mThe World after Microservice Migration w/ Service Mesh & Contract TestingD. Mitrovic · GOTO Berlin 2018
• 31mCloud Foundry and Microservices: A Mutualistic Symbiotic RelationshipMatt Stine · Cloud Foundry Summit 2014