Cloud Chaos & Microservices Mayhem

on YouTube ↗41m

" summary

Cloud and microservices realities: JVMs pick GC heuristics by container size causing long pauses in tiny containers, startup time and memory become direct costs, and Quarkus AOT helps shrink footprint. FinOps data shows about 25% zombie servers doing no useful work; horror stories include a €72k bill and an $11k incident. Microservices often become a distributed monolith when domain models are duplicated. Concrete fix: Pact contract testing demo that detects an API break (torso → stomach) before deployment.

AI-written summary · about

" chapters (17)

1. 0:00Intro
2. 1:34Things you need to do well in 2022
3. 4:16Tracing & observability
4. 6:38Performance requirements
5. 7:29Quarkus
6. 8:44Performance optimization
7. 13:24Takeaway
8. 14:31Management
9. 17:18FinOps
10. 19:50Releasing
11. 20:28Microservices
12. 22:55Modularity
13. 24:52Distributed monolith
14. 27:57Test pyramid
15. 31:04Demo
16. 39:48Demo recap
17. 40:32Outro

" related talks

• 28mCloud Chaos and Microservices MayhemHolly Cummins · jLove 2020
• 34mCloud Chaos and Microservices MayhemHolly Cummins · Jfokus 2021
• 38mCloud chaos and microservices mayhemHolly Cummins · J-Fall Virtual 2020
• 34mLets be Real Quarkus in the WildMarkus Eisele · Devnexus 2021
• 23mLightning Talk: Rethinking MicroservicesRich Hagarty · Emerging OS Forum @ Open Source Summit North America 2023
• 02h 51mReactive Microservices with QuarkusClement Escoffier, Stéphane Épardaud · Devoxx France 2021
• 54mQuarkus - make microservices "micro" again. Maksim Govorishchev. JavaFest 2020 OnlineMaksym Hovoryshchev · Java Fest 2020
• 23mMicroservices and containersVazha Pirtskhalaishvili · DevOps Inspire 2018