Kubernetes Is No Longer Number One — The REAL 2025 Cloud Native Report (CNCF x SlashData)
By Tatiana Mikhaleva · Founder & Senior Developer Advocate
Hey my cloud-native queens, kings, and everyone shipping to production in between.
In this article, we’re going to walk through the key facts from the 2025 “State of Cloud Native” report by CNCF and SlashData.
Here’s the main spoiler: Kubernetes is NO LONGER the most interesting number.
While everyone’s chasing K8s, the real action is somewhere else.
This data is based on over 12,000 developers from 128 countries, collected between June and July 2025, with a breakdown by role: backend, DevOps, ML/AI, IoT, and games.
Let’s get straight to the facts.
Finding Number One: Backend won
56% of backend developers are now cloud native.
In absolute numbers, that’s 15.6 million cloud-native developers, and 9.3 million of them are backend.
Why does this matter? Because backend teams carry the weight for APIs, observability, microservices, CI/CD, and service ownership.
If you’re building a platform, build it for backend and DevOps — not for “everyone in general”.
Backend + DevOps is the new core of the cloud-native community.
Finding Number Two: AI is not that cloud native
You might expect AI/ML to be all-in on the cloud and GPUs — but only 41% of ML/AI professionals are cloud native.
One big reason, according to the report, is the heavy use of MLaaS — managed services that abstract away the underlying infrastructure.
AI models keep scaling, but the classic DevOps discipline — logs, versioning, deployments — often lags behind.
For DevOps, SREs, and Platform Engineers, that’s a huge window of opportunity: bring proper engineering hygiene into MLOps — real pipelines, versioned environments, logs, and managed clusters.
Finding Number Three: What’s really being used
The most widely used cloud-native technologies are not exotic at all. They’re very down-to-earth:
- API gateways — 50%
- Microservices — 46%
- Kubernetes — 28%
- Observability — 28%
Observability (28%) has now caught up to Kubernetes (28%). “Just running it” is no longer enough — everyone understands you have to see what’s going on, too.
And then there’s service mesh: 8%. Eight percent. The hype made it sound like 80.
So the world isn’t living in “service mesh everywhere”. It’s living in:
just give me a solid gateway, logs, and orchestration.
If you’re building a product for DevOps, aim for this reality — not for super-exotic architectures almost nobody runs.
What to do with this data
If you’re an architect, a DevOps team lead, or building a platform, here’s what this report is really telling you:
-
Go backend- and DevOps-first. These two groups are the most cloud-native in the report. This is where you bring IDPs, artifact repositories, and policy-as-code.
-
Support hybrid. 30% of all developers are on hybrid cloud, 23% are multi-cloud. Your networking, secrets, and observability need to span everything, not just a single provider.
-
Bring ML teams up to code. If you have ML folks in-house, give them the same level of engineering hygiene as your production teams: versioned environments, pipelines, logs, clusters, and proper deployments.
-
Don’t over-engineer. The mainstream stack is this combo: API gateways, microservices, Kubernetes, plus observability — not some universal service mesh everywhere. This is a mature, understandable stack where you can actually ship and make money.
Final verdict
Cloud native is now mainstream for backend and DevOps — and AI is just playing catch-up.
How does this look in your company or team? Do these numbers match your reality, or is your stack going in a different direction?
Share your experience in the comments — I’m genuinely curious to see how this data maps to real life.
Related Posts
- 1AI SRE Joined My On-Call — A Beginner-Friendly Walkthrough of RootlyDevOps & Cloud · What an AI SRE actually does on call. A hands-on walkthrough of Rootly — how it observes, advises, and (when you let it) acts. With a real look at the four-level trust model.
- 2Stop Lying About Your Backups — Zero-Trust Recovery with PlakarDevOps & Cloud · Learn how to master Terraform tags for cloud resource management, automation, and cost tracking. Discover best practices, default tags, and merging strategies!
- 3Escaping the Command Line Cartel: Why I Mandate Visual Git in Enterprise DXDevOps & Cloud · Relying purely on the terminal is a toxic DX dependency. Discover how architecting visual version control with GitKraken eliminates cognitive load, enforces psychological safety, and scales enterprise DevOps.
- 4Inside Helm - How Charts, Releases, and State Work in KubernetesDevOps & Cloud · Learn how Helm really works under the hood — charts, releases, and Kubernetes state management explained in plain DevOps language.
Random Posts
- 1Amazon Q - The AI DevOps Tool That Fixes AWS HeadachesAI & MLOps · Amazon Q is AWS's AI assistant that helps DevOps engineers fix cloud issues faster with smart, context-aware insights and automation.
- 2Best CI/CD Tool in 2025? GitHub Actions vs GitLab CI vs Argo WorkflowsDevOps & Cloud · Compare GitHub Actions, GitLab CI, and Argo Workflows in 2025 — and find out which CI/CD tool best fits your team and pipeline.
- 3Linux for Beginners - Essential Commands Every IT Girl Must KnowDevOps & Cloud · Master Linux commands & boost your IT skills! Learn essential commands for navigating, managing files & running processes like a pro.
- 4Docker Compose Explained - Imagine Running Your Own CafeDevOps & Cloud · Docker Compose explained with a fun cafe analogy! Learn how to run and deploy apps easily with containers—perfect for beginners and IT pros alike.