AB
ALOK BUILDS← FIELD NOTEBOOK
●SECTION 03 / TECHNICAL JOURNAL
03 / FIELD ARCHIVE

Writing & Technical Notes

Dispatches on distributed systems, failure boundaries, database internals, and production engineering from the notebook.

12 ARTICLES RECORDED20 TOPIC CLUSTERSDISTRIBUTED ARCHITECTUREPRODUCTION RESILIENCE
Pagination Is Not a Detail You Take LightlyBACKEND

Pagination Is Not a Detail You Take Lightly

#backend#system-design#databases
Aug 2026 · 6 min read→
Diagram showing a database and message queue connected through an outbox tableDISTRIBUTED SYSTEMS

Designing a Timeline API: The Simplicity of Fan-out-on-Read

Designing a Timeline API: The Simplicity of Fan-out-on-Read.

#Distributed Systems#System Design#Node.js
Aug 2026 · 8 min read→
Open book with technical diagrams and notes scattered aroundSYSTEM-DESIGN

From CRUD to Distributed Systems: Why I'm Building a Twitter Timeline Service (and Documenting Every Phase)

A breakdown of Twitter's fan-out architecture - and why optimizing for reads over writes was one of the most elegant tradeoffs in social media engineering.

#system-design#distributed-systems#learning
Jul 2026 · 4 min read→
Diagram showing producer, queue, consumer, retries and dead letter queueDISTRIBUTED SYSTEMS

Dead Letter Queues: Building Reliable Distributed Systems That Don't Lose Messages

Retries alone aren't enough. Learn how Dead Letter Queues isolate poison messages, preserve failures for debugging, and keep distributed systems reliable.

#Distributed Systems#System Design#Messaging
Jul 2026 · 25 min read→
Diagram showing a database and message queue connected through an outbox tableDISTRIBUTED SYSTEMS

The Outbox Pattern: How I Stopped Losing Messages Between My Database and My Queue

A payment succeeds, the customer gets charged, but the confirmation email never arrives - because your process crashed between two lines of code. Here's the pattern that closes that gap, and why every production system eventually needs it.

#Distributed Systems#System Design#Node.js
Jul 2026 · 11 min read→
Open book with technical diagrams and notes scattered aroundKAFKA

Building a Real-Time Analytics System with Apache Kafka: Lessons from My Mini Uber Project

I wanted to understand how companies like Uber process millions of location updates every day. Instead of watching more tutorials, I decided to build a small event-driven backend from scratch using Apache Kafka, Socket.IO, and TypeScript.

#Kafka#distributed-systems#learning
Jun 2026 · 6 min read→
How Netflix Stopped One Slow Microservice From Taking Down the Whole CompanyBACKEND

How Netflix Stopped One Slow Microservice From Taking Down the Whole Company

The real story behind Hystrix, Netflix's circuit breaker library - why cascading failures kept taking down their platform, and the pattern they built to stop it.

#backend#system-design#reliability
Jun 2026 · 6 min read→
Open book with technical diagrams and notes scattered aroundSYSTEM-DESIGN

How X (Formerly Twitter) Adopted Fan-out So Beautifully

A breakdown of Twitter's fan-out architecture - and why optimizing for reads over writes was one of the most elegant tradeoffs in social media engineering.

#system-design#distributed-systems#learning
Jun 2026 · 6 min read→
Network of connected systems with glowing nodes representing distributed architectureDISTRIBUTED-SYSTEMS

You Can't console.log Your Way Out of a Distributed System

What DDIA Chapter 1 taught me about partial failure - and why tracing tools like Zipkin and OpenTelemetry aren't over-engineering.

#distributed-systems#system-design#observability
Jun 2026 · 4 min read→
Server room with network cables connecting multiple systemsDISTRIBUTED-SYSTEMS

Designing a Scalable Distributed Notification System

A deep dive into building a production-ready notification system with RabbitMQ, Redis, and proper observability.

#distributed-systems#backend#architecture
Mar 2024 · 2 min read→