History, Fundamentals and Future of Cloud Native
summary
Timeline traces the term from academic papers (2011) to industry definitions (2012, 2017) and gives a working definition: a distributed, elastic, horizontally scalable app made of microservices that isolate state. Concrete practices include Kubernetes and OpenShift for orchestration, OpenTelemetry for observability, event storming + DDD for decomposition, consumer‑driven contracts and context maps for integrations, CI pipelines that spin test environments on GCE, and a migration roadmap; one cited scale example is 170,000 instances and millions of users, with team velocity moving from quarterly releases to ~50 releases per sprint.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:37History of Cloud Native
- 9:41How did Cloud Native emerge
- 16:00Digitalization and digitization
- 17:45Organization shift
- 21:29Principles of Cloud Native
- 36:31Verticals
- 37:47Context Map Patterns
- 40:43Custom Supplier
- 42:20Consumers
- 43:05Models
- 44:13Shared Partner
- 45:28Two Services
- 47:40Deployment Pipeline
- 49:50Cloud Native Computing Foundation
- 50:50Cloud Native Roadmap
- 52:18Cognitive Landscape Map
- 53:23Conclusion
related talks
14mCloud Native vs. Platform Native vs...
23mKeynote: A Brief History of the Cloud from Servers to VMs to Buildpacks to Cloud Native Containers
43m(Mis)Understanding Cloud-Native
23mMaking Cloud Native Computing Universal and Sustainable
03mGoing (cloud) Native
51mWhat Is This Cloud Native Thing Anyway?
50mFlying through Cloud Native (CNCF)
27mCloud Native: why, oh why?