Nine Ways To Fail at Cloud Native

on YouTube ↗44m

" summary

Argues that common failures are concrete: microservices become a distributed monolith when teams copy‑paste domain models instead of sharing libraries; CI/CD sits idle in Tekton or Jenkins so releases still happen twice a year (a bank’s release board example); provisioning that should take 10 minutes stretches to three months behind an 84‑step pre‑approval; the Mars probe crash shows unit mismatch. Recommends fixes like consumer-driven contract tests, automation-first CI, feature flags, canary deploys, and paired co‑creation to make cloud native actually deliver.

AI-written summary · about

" chapters (7)

1. 0:00Introduction
2. 3:11What cloud native means
3. 12:30Microservices project failures
4. 21:55Cost of manual testing
5. 27:09Old governance blocks cloud
6. 28:12Culture and ops for cloud native
7. 31:01Q&A

" related talks

• 54mCloud Native CultureNathaniel Schutta · Devnexus 2020
• 42mCloud Native ApplicationsKarsten Samaschke · ContainerDays Hamburg 2018
• 59mCloud Native CultureNathaniel Schutta · Developer Summit 2020
• 46mThe Cloud Native Diabolical DeveloperMartijn Verburg · Devoxx Belgium 2019
• 06mAccelerate Application Delivery with a Cloud-Native MindsetAndrew Hately · O'Reilly Software Architecture Conference New York 2018
• 06mCloud-Native Application Testing ApproachesSumit Mundhada · TestFlix 2022
• 29m5 ways to screw up your DevOps TransformationDave van Herpen · devopsdays Amsterdam 2020
• 30mThis is Not a Technology Problem: Leveraging Culture and Process to Make the Most...Colin Simmons · Cloud Foundry Summit North America 2019