Skip to content

Decisions

0002 - Go for services

Architecture decision: Go for services

On this page

Date: 2026-01-04

Status: Accepted; refined by ADR 0005.

Context

The rewrite needed a service language suited to concurrent work and a modest runtime footprint.

Decision

We chose Go as the primary service language for its concurrency model, runtime footprint and deployment characteristics.

Consequences

The project must maintain Go alongside other language ecosystems. Twitch ingress later adopted Elixir for supervision (ADR 0005).

References

Go module, Twitch ingress.