(Mis)Understanding Cloud-Native
summary
Defines cloud native by CNCF keywords then gives pragmatic rules: choose public, private or hybrid based on workload predictability; prefer open-standards managed services (eg Postgres) to reduce migration pain rather than fetishizing DIY clusters; use tools like Kubernetes, Knative, OpenShift, Terraform/Pulumi and OpenTelemetry for deployment, serverless and observability; treat lift‑and‑shift as minimal modernization, not a rewrite, assess code, data and integrations before moving, and expect CI/CD and infra automation to evolve — doing too much DIY operations costs time more than it saves.
AI-written summary · about
chapters (8)
- 0:00Start
- 2:29The CNCF Cloud Native Definition v1.0
- 12:59Lift-And-Shift
- 14:44Further Development
- 20:08There is always a way to evolve your implementation
- 24:55DIY Kubernetes Story (In Short)
- 33:23Resilient CI/CD pipelines
- 37:42Make a System Observable
related talks
53m(Mis)Understanding Cloud Native
03mGoing (cloud) Native
51mWhat Is This Cloud Native Thing Anyway?
56mHistory, Fundamentals and Future of Cloud Native
34mGoing cloud-native: Why? How? & What?
55mWhat Does Cloud-native Mean Anyway?
14mCloud Native vs. Platform Native vs...
20mComplexity of the cloud native ecosystem