AK
Available for Hire/Consulting · 2 slots / month

Scalable backend systems,engineered for 0 → 100x.

I'm Anup Kumar — Architect / Principal Engineer with 13+ years designing APIs, distributed systems, and infrastructure that served 200M+ users at Bolt (Berlin) and Delivery Hero. Now helping founders and teams scale without breaking.

Portrait of Anup Kumar
Trusted track record across
Bolt
Delivery Hero
HERE Technologies
JetSynthesys (GREE)
Tata Consultancy Services
200M+
MAU served in production
10K
RPS handled at peak
35%
Latency reduction at Bolt
13+
Years of engineering
What I do

Backend, architecture, and the hard parts.

I focus on the systems most teams don't have the time — or the scars — to build properly.

01
Backend Architecture & System Design
02
Distributed Systems & Event-Driven Architecture
03
API Design (REST / GraphQL / gRPC)
04
Performance & Cost Optimization
05
Cloud Infrastructure (AWS, GCP, Kubernetes)
06
Blockchain & Smart Contracts (Rust, Solidity, CosmWasm)
Featured work

Case studies, not a GitHub dump.

All case studies
Architecture notes

I think in diagrams. Here are two.

Full gallery
architecture / distributed-rate-limiter.svg
Clientsmobile · web · 3rd partyAbusive actorbot / retry stormAPI Gatewayrate-limit middlewaretenant · route · userRedisZADD + ZREMRANGEBYSCOREsliding window (sorted set)Local shadow cachefallback if Redis downOrders serviceprotectedPayments serviceprotectedSearch serviceprotectedHTTP 429Retry-After headerallowed paththrottled (429)
Distributed Rate Limiter
architecture / idempotent-payment-system.svg
ClientIdempotency-KeyPayments APIdedupe + validatecheck-and-set on keyIdempotency storeRedis + Postgreskey → response hashLedger (Postgres)double-entrytx: DEBIT + CREDITunique(idempotency_key)Outbox tablesettlement.requestedFraud / risk checkssynchronousAcquirer / PSPexponential backoffRetry workerreads outbox → PSPdead-letter on cap1. POST /charge + key2. check dedupe3. write tx atomically4. call PSP5. outbox event6. async retry
Idempotent Payment System
Writing

Field notes from production.

All writing
Let's build

Have a system that needs to scale — or stop breaking?

I work with a small number of teams each month on architecture reviews, scaling, and hands-on backend engineering. If that sounds like you, let's talk.