What Does Cloud-native Mean Anyway?
summary
Cloud-native means an application is designed to work well in a cloud environment, not that it must be microservices; vendors differ and CNCF lists containers, service meshes and microservices as exemplars but not requirements. Industry surveys show monolith interest rising from 12% to 25%, large wins at Spotify and Netflix coexist with many failed microservice projects producing distributed monoliths. Practical stack examples mapped to the 12-factor app include Git, Tekton/Jenkins, Docker registries, Kubernetes, MicroShed testing, ELK and Open Liberty.
AI-written summary · about
chapters (14)
- 0:00Introduction to cloud native
- 1:27Vendor definitions of cloud native
- 6:29CNCF definition and microservices debate
- 8:36Architectural styles spectrum
- 13:10Industry shift away from microservices
- 16:46Distributed monolith pitfalls
- 18:53Choosing the right architecture
- 21:21Reasons for investing in cloud
- 23:09Essence of cloud native
- 25:1312 Factor methodology explained
- 31:07Tools for cloud native development
- 34:19Architecture doesn't limit cloud native
- 36:23Summary and key takeaways
- 40:15Q&A session
