Engineering
Engineered for planet scale.
01Principles
Eight rules we don’t bend.
They decide what we build, how we build it and what we refuse to ship.
- 01
Correctness first
A fast wrong answer is a slow disaster. Contracts are typed, invariants are tested, and a result is official only when the server has computed it.
- 02
Tail latency is a feature
Averages hide the players who feel the lag. We design for the 99th percentile, keep hot paths allocation-light, and measure them in microseconds.
- 03
Fairness is engineered
In a real-time sport, consistent latency for everyone, everywhere, is part of the product. Fairness is a requirement we build to, not a promise we make.
- 04
Designed for partial failure
Every dependency fails eventually. Services degrade gracefully, isolate faults, and recover without taking their neighbors down with them.
- 05
Observable by default
Metrics, traces and structured logs ship with the first line of a service, not after the first incident. What we cannot see, we do not ship.
- 06
Interfaces are products
Service contracts and event streams are versioned, owned and reviewed like public APIs, so every service can deploy on its own schedule.
- 07
Security in depth
Every new surface is threat-modeled before it ships. Least privilege, secrets outside code, and integrity enforced on the server — never trusted to the client.
- 08
Cost is architecture
A choice that is cheap for one user and ruinous for millions is the wrong choice. We weigh every design against its unit economics at scale.
02By the numbers
Measured in microseconds.
The engineering targets behind TYPEMUSE, as published — engineered-for figures, never a claim about live traffic.
- real-time race netcode
- 60 Hz
- keystroke engine hot path
- 59 µs
- domains, one polyglot fleet
- 9
- of players, by design
- Millions
03The stack
A polyglot fleet, one build graph.
Every language chosen for what only it does best — the TYPEMUSE monorepo on one hermetic build graph, every surface observed end to end. This is a glimpse, not the blueprint.
11 programming languages 3 codebases
Measured
- Dart
- Elixir
- Go
- Java
- JavaScript
- PL/pgSQL
- Python
- Rust
- Shell
- Starlark
- TypeScript
Every programming language with substantial code across Syrosin’s codebases — the TYPEMUSE monorepo and the company’s websites — classified the way GitHub does. Build-tool output, third-party libraries, and markup and data formats are not counted. Dart is included ahead of its arrival in the codebase.
Language names and logos are trademarks of their respective owners, shown only to identify the languages we build with; no endorsement is implied. Postgres, PostgreSQL and the Slonik logo are trademarks of the PostgreSQL Community Association of Canada. Rust logo © Rust Foundation, CC BY 4.0, recolored. Duke, the Java mascot, is used under the BSD license.
Bazel monorepo
One hermetic build graph for every language.
gRPC + Protobuf
Typed, versioned contracts between services.
Apache Kafka
Durable event streams between domains.
Kubernetes
Declarative, independently deployable services.
Global edge network
Traffic served and protected close to players.
OpenTelemetry
One standard for metrics, traces and logs.
04In practice
How the principles show up day to day.
Hermetic builds
One build graph compiles, tests and packages every language the same way on every machine, so a green build means the same thing everywhere.
Contracts before code
Service boundaries start as typed, versioned contracts. Breaking changes are caught at review, not in production.
Benchmarks in the loop
Hot paths carry benchmarks, and a change that slows them is a change that has to explain itself.
Every surface threat-modeled
Before an endpoint, webhook or form ships, we write down who can call it, what it can reach and what it costs if abused.