Go vs Rust for backend services at scale: what real teams chose
Published 2026-10-19 · Built only from first-party engineering write-ups in our database. Every number below comes from the linked source.
The best-known direct comparison is Discord's 2020 post: it rewrote its Read States service from Go to Rust to get rid of garbage-collection latency spikes in a large in-memory cache. Elsewhere in our database the two languages coexist: Dropbox lists both Rust and Go for Magic Pocket, Datadog built Husky in Go and redid timeseries indexing in Rust, and Cloudflare uses Go for Quicksilver and its HTTP analytics pipeline and Rust for Pingora.
Go vs Rust: side by side
| Go | Rust | |
|---|---|---|
| Stories in our database | 7 | 11 |
| Companies | Cloudflare, Datadog, Discord, Dropbox and Slack | Axiom, Cloudflare, Datadog, Discord, Dropbox, Figma and OpenAI |
| Published | 2017–2023 (1 undated) | 2018–2026 (2 undated) |
| Techniques alongside it | columnar storage (2), multi-tenancy (2), aggregation (1), caching (1) | rewrite (6), indexing (2), caching (1), CDC cache invalidation (1) |
| Scale numbers stated in sources | 14 million HTTP requests/sec (network peak) (Cloudflare); 6M requests/sec (Cloudflare); 500 PB (Dropbox) | 1B+ users across 40 regions (OpenAI); 70 million+ requests/sec (OpenAI); dozens of clusters, hundreds of database nodes (Discord) |
| Direct comparison story | Discord: Why Discord is switching from Go to Rust | (same story) |
Verdict
In these stories, Rust shows up where teams hit GC pauses or wanted lower latency and memory (Discord, Figma, Cloudflare's Pingora). Go shows up in plenty of systems that scaled fine. Neither is a default winner.
Counts are stories in How They Scaled tagged with each side, see the Go and Rust pages. They describe what these teams wrote about, not market share or benchmark results.