Backend scalability engineering · est. 2019 · three engineers
An eight- to sixteen-week embed. A hardened core, in your repo, under your review process. A runbook, a load-test suite, and a benchmark harness your on-call engineer can actually run at 2 a.m. We do not do greenfield. We do not do "digital transformation." We migrate hot paths off burning platforms and we write the postmortems so your engineers don't have to.
Below: selected engagements since 2022. Client names are withheld by default; architectural detail is not. The status strip at the foot of this page is current as of the last tending.
A double-entry ledger written in Ruby was capping at 340 postings/sec under payroll-day contention. We re-implemented the posting engine in Go with per-account serial queues and a Raft-backed journal, gated behind a differential tester that replayed a year of production journal entries. Sustained throughput now sits above 11,000 postings/sec with p99 under 40ms.
Go 1.22 · PostgreSQL 15 · NATS JetStream · etcd/raft · OpenTelemetry
Forty-three Node services with unbounded in-memory queues had been producing correlated tenant outages for two years. We collapsed the path into three Go binaries — edge receiver, normalizer, sink writer — with bounded channels, explicit shed policies, and a Kafka offset-replay tool that turned incident recovery from a war room into a command.
Go 1.21 · Kafka · ClickHouse · Kubernetes · OpenTelemetry
A freight-matching platform had accumulated microservices faster than domain boundaries. We mapped the real call graph from four weeks of OpenTelemetry traces, identified aggregate roots, and merged the shipment and pricing contexts into single Go services. The remaining four were left as a boundary proposal the client's platform team executed on its own cadence.
Go 1.21 · gRPC · CockroachDB · Temporal · OpenTelemetry
Premium encoding jobs were missing SLAs because the scheduler was a priority queue with wishful thinking. We replaced it with a deadline-aware EDF variant with bounded preemption, under 900 lines including comments, gated by a simulator that replays a year of historical submissions. Miss rate fell from 4.2% to under 0.1%.
Go 1.20 · Redis Streams · FFmpeg orchestration · Prometheus
A healthcare-adjacent SaaS needed session handling decoupled from its monolith for compliance, without a forced flag day. We built a thin Go auth service in front, lazily re-hashed bcrypt credentials on successful login, and moved sessions to PASETO v4. Zero observed forced logouts during the three-week cutover.
Go 1.21 · PASETO v4 · PostgreSQL · Envoy · Redis
"Good Go code is mostly the code you chose not to write. We spend the first two weeks deleting things and the next six making what remains impossible to misuse."
— From our engagement handbook, §2.1 "The First Fortnight"
Calendar
Q1 & Q2 booked. Q3 has one slot under consideration; the ledger engagement rolls off 14 March.
Reading
See Method for our assessment template and benchmark discipline.
Commit log
Portfolio prose was last edited the week of 10 Feb 2025. The measurements underneath are re-verifiable from the SHAs in each case file.