Technology
Go
Go is for jobs, gateways, and the quiet services that sit beside a Next.js app. We use it when a script has become a product.
What it is
Go is the language Google designed for networked services: simple, compiled, garbage-collected, with concurrency as a primitive (goroutines). It is the language of Docker, Kubernetes, and a large share of the cloud plumbing people never see.
Teams pick it for APIs, CLIs, and workers that have to be small, fast to deploy, and easy to read six months later. It is not a UI language. It is a service language with an opinion about what should not be in the language.
What it does
Companies use Go for gateways, proxies, orchestration, and back ends that sit behind a TypeScript or mobile client. Cloudflare, Uber, and Twitch have all talked about Go in production. If the product is a container platform, Go is probably already in the repo.
We use it for services that need to be boring and fast. The interface can still be Next.js. Go does not have to own the pixels.
Why we use it
Small services for work the page should not wait on.
When a script has become a product, Go is a fit. The interface stays on the web stack your team can publish from. The service is boring on purpose.
If it has to start fast and stay boring, it probably does not belong in the request.
Built on it
Docker
The original engine and CLI are Go, which is why containers feel like Go culture.
Kubernetes
Google's orchestrator, written in Go, now the default cluster API.
Uber
Has published extensively on Go services at marketplace scale.
Cloudflare
A large share of edge and control-plane work is Go.
Twitch
Has used Go for chat, video plumbing, and high-throughput services.
Tell us what needs to ship.
You use a working prototype before the production build goes ahead.