Cilantrobyte.

Tech Stacks · Backend

Go

For services with hard latency budgets.

Category

Backend

At the studio

Since 2021

Projects shipped

1 case study

Status

Active

(01) Our take

We write Go when latency is the product. For rate limiters, auth proxies, realtime aggregation services, and anything that has to stay under 10ms p99, Go's concurrency model and predictable runtime behaviour are hard to beat.

We don't pick Go for CRUD. The type system's strictness is a cost when you're writing boring database-backed endpoints, and the ecosystem's lack of a dominant web framework means you make more small decisions than you'd like. But for specialised infrastructure, it's our first choice.

(02) What we build with it

Typical work

  • Realtime services with strict latency requirements
  • Proxy and gateway services
  • Command-line tools and operational utilities
  • High-throughput data ingestion

(03) How we engage

Engagement shape

Go is usually one service among many in a larger engagement — we rarely build entire products in Go, but we frequently build specific services in it.

(04) In production

Where we've shipped it

All case studies →

(05) Pairs with

Works well with

Technologies we reach for alongside Go in most engagements.

Data

PostgreSQL

The default database. For almost everything.

Data

Redis

The cache, the queue, the session store, the rate limiter.

Infra

Docker

The container standard, still.

Infra

AWS

The default cloud when compliance, scale, or sovereignty demand it.

Thinking about a Go project?

Start a project →back to all stacks