Evolving the Cloud Native Maturity Model
summary
Cartografos publishes a five-phase maturity model that maps concrete expectations: Build (pre-production), Operate (one app in production), Scale (many apps, multi‑cloud), Improve (policy/code refinement) and Optimize (lean toolset, contributions back). It prescribes people/process/policy/tech/business KPIs, recommends CI/CD and GitOps patterns, enforces policy-as-code via admission controllers like Gatekeeper and operators (example: Strimzi for Kafka), and keeps artifacts in a GitHub repo with community scoring and contribution paths.
AI-written summary · about
chapters (11)
- 0:00Cloud Native Maturity Model intro
- 1:07Cartographer working group origins
- 2:32Need for maturity model
- 3:56Key themes and levels
- 6:50Level 1: Pre-production builds
- 12:04Level 2: Production operations
- 18:24Level 3: Scaling complexity
- 24:04Level 4: Policies and processes
- 27:18Level 5: Technical debt
- 30:32Model evolution and plans
- 32:17Q&A
related talks
34mIntro to the Cloud Native Maturity Model
35mTowards Cloud Native Platforms
21mGrowing up in a cloud native org
40mClosing Keynote: 4 Quadrants of DevOps Maturity Model
27mMaturity: Understanding Where You Are Today, to Get Where You Want to Be Tomorrow
54mCloud Native Culture
44mNine Ways To Fail at Cloud Native
30mCloud & DevOPS culture