Posts
All the articles I've posted.
I built Uber's backend. Then one driver got 59 riders
Part 2 of a ride-hailing backend on kind: 10,000 drivers and 6,000 riders in an Istanbul-sized city push three Go pods to their CPU limit, a Redis geo index (GEOADD, GEOSEARCH) halves the work and fills the map again, and a check-then-set race hands one driver 59 riders until SET NX fixes it. Every manifest, command and number.
I built Uber's backend. It crashed at 5,000 drivers, and these three fixes held it up
A Go location service on a local kind cluster behind HAProxy, load-tested with k6. One pod gets OOMKilled at about 5,000 WebSocket drivers, three pods lose two thirds of the drivers, Redis pub/sub brings them back and a Horizontal Pod Autoscaler grows it to four pods at 10,000 drivers, with every manifest, command and number.
Microservices communication patterns on a real shop: retries, Kafka, the outbox and a saga
Four Spring Boot 4.1 services, Kafka 4.3, Postgres 17 and Debezium 3.7 in Docker Compose. A retry that charges a card three times, an idempotency key that stops it, a circuit breaker, an event lost to a dual write, the outbox that fixes it and a saga that refunds the money, with every command and output.
Nginx in front of two Node.js apps: proxy headers, failover, 429 and a cache HIT
One Nginx 1.31.6 container and two Node.js app instances in Docker Compose. Every config file, the headers the app receives, a stopped backend costing exactly one slow request, rate limiting with 429, gzip at 8x, a cache HIT in under a millisecond and TLS 1.3 with HTTP/2, with every command to repeat it.
Spring Boot logging, from log levels to Grafana Loki
A Spring Boot 4.1 service that logs at every level, writes JSON with one property, changes its log level at runtime through Actuator and ships everything to Loki with Grafana Alloy. Every config file, command and output, plus the LogQL that finds a failed payment and its stack trace.
Watching Kafka work: batches, log segments and an idle fourth consumer
Kafka 4.3.1 in one container, 3,000 keyed messages and three partitions. The segment files on disk, 900 messages stored in two batches, keys that always land in the same partition, a consumer that gets nothing, and every command to repeat it.
One index, 467x faster: reading a PostgreSQL B-tree from the inside
Five million rows, one customer, 54 ms with a sequential scan and 0.116 ms with a B-tree index. The EXPLAIN output line by line, the tree's real depth from pageinspect, what the index costs, and every command to repeat it.
HTTPS from the terminal: eleven checks with curl and openssl
Look at a real TLS 1.3 connection to Google, read its certificate chain, build a tiny certificate authority, break certificates on badssl.com and time every step of one request, using only curl, openssl and dig.