~/ratelimit-svc
Distributed rate limiter for high-throughput APIs
A sharded token-bucket service backed by Redis with sub-ms p99 latency. Pluggable strategies (fixed, sliding, leaky-bucket) and a Go SDK with circuit-breaker fallback.
// hello, world
I design and ship reliable services — APIs, event pipelines, and data infrastructure. Currently focused on distributed systems and developer experience.
A short paragraph about who you are. Replace this with your story — what you care about, what kinds of problems you like solving, and what you're looking for next.
I'm a backend engineer with X years of experience building services that handle real traffic. I care about correctness, observability, and code that other engineers can pick up six months later without cursing.
Lately I've been working on <a domain or problem> — ingest pipelines, search infra, low-latency APIs, whatever fits. Outside of work, I write about systems on my blog and contribute to a couple of OSS projects.
When I'm not in front of a terminal: coffee, mechanical keyboards, and reading distributed-systems papers I only half understand.
Selected work — replace these placeholders with your own projects. Each card highlights the problem, stack, and a couple of impact metrics.
Distributed rate limiter for high-throughput APIs
A sharded token-bucket service backed by Redis with sub-ms p99 latency. Pluggable strategies (fixed, sliding, leaky-bucket) and a Go SDK with circuit-breaker fallback.
Multi-tenant event ingest pipeline
Ingest, validate, and route billions of analytics events daily. Kafka-based fan-out, Avro schemas, and exactly-once consumers writing to ClickHouse for sub-second queries.
Zero-downtime PostgreSQL migration tool
A small CLI that runs safe schema changes against live Postgres — adds locks-with-timeouts, NOT VALID constraints, and chunked backfills. Used by a dozen teams internally.
Read-through cache layer with stale-while-revalidate
A thin Go library + sidecar that caches expensive read queries at the edge. SWR semantics, request coalescing, and per-tenant TTLs configurable at runtime.
A short timeline of where I've been. Replace these entries with your roles, dates, and the impact you owned.
The fastest way to reach me is email. I read every message and reply within a couple of days.
$ echo "let's build something"
I'm open to backend / platform roles, freelance work, and interesting OSS collaborations.
you@example.com →