Cloud Chaos and Microservices Mayhem

on YouTube ↗28m

" summary

Cloud-native Java causes real failures and fixes: forgotten Kubernetes clusters can cost €1,000/month (one demo cluster burned ~€2,000), a 2017 survey found 25% of 16,000 servers were idle, and the Mars Climate Orbiter failed from unit mismatch showing distributed coupling risk. Practical moves include finops for cost ownership, using Pact consumer-driven contract tests (demo: a React frontend + MicroProfile backend where a refactor broke the contract and tests caught it), and adopting Quarkus-style AOT to hit millisecond startups.

AI-written summary · about

" chapters (12)

1. 0:00Intro
2. 1:30Cloud Chaos
3. 3:51Cloud Management
4. 4:15Unlimited Hardware
5. 4:44Zombies
6. 6:45phinops
7. 8:45footprint
8. 11:03microservices
9. 13:22challenges with microservices
10. 15:55reasons not to do microservices
11. 17:57the test pyramid
12. 19:11fire alarms

" related talks

• 34mCloud Chaos and Microservices MayhemHolly Cummins · Jfokus 2021
• 38mCloud chaos and microservices mayhemHolly Cummins · J-Fall Virtual 2020
• 41mCloud Chaos & Microservices MayhemHolly Cummins · GOTO Amsterdam 2022
• 50mJourneys To Cloud Native Architecture: Sun, Sea & EmergenciesNicki Watt · GOTO Chicago 2019
• 09mThe cloud native elephant in the roomBob Quillin · O'Reilly Velocity Conference 2019
• 59mControlled Chaos: Managing your Microservice Ecosystem for Business AgilityTobias Kunze · DevOpsCon Munich 2019
• 39m10 Tips for failing at microservicesDavid Schmitz · code.talks 2017
• 48mCloud Native JavaKenny Bastani · GOTO Chicago 2018