Orbital Ledger
An event-sourced double-entry ledger powering card and wallet payments. Idempotent write API, outbox-based event publishing and nightly reconciliation against bank statements.
I build the gravity that holds products together — APIs, data pipelines and distributed services that stay in stable orbit under load.
Begin descentI'm Matthew, a backend developer who designs and operates the systems users never see but always rely on: payment ledgers, event streams, APIs and the infrastructure that keeps them running.
For more than seven years I've been building server-side software across fintech, logistics and SaaS. My work starts where the interface ends — modelling data so it stays consistent, designing APIs that are pleasant to integrate with, and shaping services so they scale horizontally without surprises.
I care about systems that are boring in production: observable, well-tested, and documented well enough that the next engineer can land safely. I'm most at home with Go and Python, PostgreSQL and Kafka, and I'm comfortable owning a service from schema design to on-call.
Four payload bays, each calibrated over years of production flights. Readings show working proficiency.
Primary thrust for services and tooling.
Storage, streams and caching at scale.
Launch pads, containers and cloud.
Navigation systems that keep it all stable.
Selected systems I've designed and flown into production, with the telemetry that matters.
An event-sourced double-entry ledger powering card and wallet payments. Idempotent write API, outbox-based event publishing and nightly reconciliation against bank statements.
A multi-tenant API gateway with token-bucket rate limiting, JWT auth and per-tenant quotas. Replaced three legacy proxies and gave every team a single, observable front door.
A streaming ingestion pipeline for fleet telemetry — GPS pings, scan events and ETAs — deduplicated, enriched and landed in an analytical store for real-time shipment tracking.
An internal observability toolkit: a drop-in Go library for tracing, structured logs and RED metrics, plus generated Grafana dashboards and SLO alerts for every new service.
Every stage added altitude. Here's the ascent so far, latest burn first.
Have a system that needs a stable orbit? The channel is open — transmissions are answered within one Earth day.