mekhi//node

Mekhi Thomas-El

Software Engineer, Distributed Systems

Philadelphia, PA · resume · linkedin

What I build

Systems that stay correct under failure, and that can prove they did. Most of my work sits in two places: the low-level storage and filesystem layer, where correctness is enforced by the code itself, and the distributed decisioning layer, where a request has a hard latency budget and a decision that must be reproducible months later.

Those are the same problem at different scales. A filesystem that can migrate an on-disk format without going down is solving an exactly-once problem. A payment eligibility decision that must be re-explainable a year later is solving the same one again.

Selected work

This server, right now

Every number below is scraped from this process. No mock data, no screenshots.

p99 latency
—
budget 20ms
p50 latency
—
median handler time
requests served
0
since start
in flight
0
concurrent

Raw text exposition: /metrics · JSON: /api/stats

How this is built

A single Go binary using nothing but the standard library. No web framework, no client library, no markdown parser, no charting library. The Prometheus exposition format, the histogram quantiles, the markdown renderer, and the chart are all implemented here, because depending on them would defeat the point of the page.