Decisions
Decisions
0005 - Elixir for Twitch ingress
Architecture decision: Elixir for Twitch ingress
On this page
Date: 2026-05-23
Status: Accepted; supersedes ADR 0001 in part.
Context
The original Twitch connection lifecycle was difficult to supervise. ADR 0002 chose Go as the primary service language.
Decision
We chose Elixir and OTP for Twitch ingress. Supervision gives long-lived connections an explicit place to recover from failures. This refines the ingress portion of ADR 0001.
Consequences
The project maintains a second runtime and toolchain. The decision to use services remains in force.