Go is becoming important in cloud and DevOps because it is already used to build foundational infrastructure projects—including Docker and Kubernetes—and because many Go developers work on cloud infrastructure tooling. In the Go project’s 2025 survey, more than one-third of respondents said they build that kind of tooling. Those findings point to Go’s practical place in the ecosystem, not a claim that every cloud team uses it or that it is the best language for every job.
Why Go is prominent in cloud infrastructure
The clearest evidence is in the software itself. The Go project’s FAQ identifies Docker and Kubernetes as major cloud infrastructure projects written in Go. It also describes Go as a key language in Google site reliability engineering (SRE), large-scale data processing, and Google Cloud software.
That footprint gives developers practical reasons to encounter Go: they may operate, extend, or integrate with infrastructure software built in the language. In the Go project’s 2025 developer survey, more than one-third of respondents said they specifically build cloud infrastructure tooling. The figure describes survey respondents, not all Go developers or all software teams.
What Go developers report about cloud deployments
The 2025 Go survey found that respondents reported deploying Go software to several kinds of environments. AWS was reported by 46%, company-owned servers by 44%, and Google Cloud Platform by 26%. These categories may overlap, so they should not be read as shares that add up to 100% or as exclusive choices.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
The spread suggests that Go development is not confined to a single public-cloud provider. Survey respondents also described cases where they were unsure about provider-specific experience or did not directly interact with public-cloud platforms. Some said containerization helped abstract deployment from provider details. That is respondent experience, not a guarantee that every Go application is portable without adaptation.
How Kubernetes fits—and what its adoption figure means
Kubernetes is important context for cloud and DevOps work, but Kubernetes adoption is not a measure of Go adoption. The Cloud Native Computing Foundation’s 2025 Annual Cloud Native Survey announcement, published January 20, 2026, says 82% of container users ran Kubernetes in production. That statistic describes container users covered by the CNCF survey; it does not say what percentage of their software was written in Go.
Go’s connection to Kubernetes is concrete because Kubernetes itself is written in Go. The broader adoption figure explains why cloud-native infrastructure is relevant to developers, without establishing that Kubernetes use caused Go’s popularity.
Tools commonly found alongside Go
The Go project’s 2023 H2 survey gives a snapshot of technologies respondents used with their Go software. These are neighboring tools in reported workflows, not requirements for Go development.
| Tool or category | Survey finding | What it is used for |
|---|---|---|
| Prometheus | 43% of respondents reported using it as an observability system with their Go software | Monitoring and metrics |
| Grafana | 43% of respondents reported using it as an observability system with their Go software | Observability and dashboards |
| gRPC | The survey names it among technologies used alongside Go; no percentage is stated here | Service communication |
| Terraform | About one-quarter of respondents reported using it for infrastructure-as-code needs | Infrastructure as code |
All figures in this table come from the Go project’s 2023 H2 survey, not its 2025 survey. They should be read as a dated view of respondents’ stacks, rather than current adoption rates across the industry. Using Prometheus, Grafana, gRPC, or Terraform does not require a team to write its software in Go.
What the evidence does—and does not—say about Go’s importance
Together, the project footprint and the surveys show why Go matters in cloud and DevOps: it is used in major infrastructure projects, and a substantial portion of surveyed Go developers work directly on cloud infrastructure tooling. The deployment responses also show that respondents work across public cloud and company-owned environments.
Rank #4
These facts do not establish that Go is universally dominant, or that it is faster, safer, simpler, or cheaper than another language. Nor do they prove that using Kubernetes or another cloud-native tool leads a team to choose Go. The surveys are respondent-based, and CNCF’s adoption figures describe the organizations or users included in its survey, not the entire global market.
A separate historical statistic needs similar care: a Google Cloud post published in 2022 said that more than 75% of CNCF projects, including Kubernetes, were written in Go, based on public repositories as of May 2021. That is useful historical context, not a current estimate of Go’s share of CNCF projects.
Best Value
When Go may be a practical choice
The evidence is most relevant if you are evaluating a language for infrastructure tooling or cloud software that needs to work with systems already built in Go. For a real project, the decision still depends on the work and the organization, not on popularity figures alone.
Quick Recap
- Workload: Decide whether you are building infrastructure tooling or application services; the survey findings do not establish that the same language choice suits both equally.
- Operational needs: Check the runtime, packaging, and distribution requirements for your deployment environment rather than assuming a language will automatically make deployment portable.
- Team and codebase: Account for existing skills, maintainers, and integration with the organization’s current software.
- Required ecosystem: Confirm that the libraries and APIs your system needs are available and suitable.
- Deployment environment: Evaluate the target platform and its constraints; survey respondents reported using a mix of cloud providers and company-owned servers.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
