Backend

MCP and 40 Years of Distributed Systems: When AI Agents Repeat the RPC Mistakes

MCP and 40 Years of Distributed Systems: When AI Agents Repeat the RPC Mistakes

In late July 2025, Julien Simon published an argument nobody in the AI tooling bubble wanted to hear: the Model Context Protocol ignores forty years of hard-won distributed systems lessons. The Hacker News thread pulled 409 points and 227 comments. Most people agreed, a few pushed back, and nearly everyone missed the detail that actually matters: MCP is not a new protocol. It is JSON-RPC 2.0, which makes it a grandchild of Sun RPC from 1984.

Read More
Hyrum's Law in Go: When an Error String Becomes an Immutable API Contract

Hyrum's Law in Go: When an Error String Becomes an Immutable API Contract

Some comments in the Go standard library make you close the laptop for a minute. Not because they are hard to understand, but because they are brutally honest about something most of us prefer to ignore.

Read More
From KISS and SOLID to Idempotency: Demystifying Classic Software Engineering Terms for Go Backend

From KISS and SOLID to Idempotency: Demystifying Classic Software Engineering Terms for Go Backend

If you have ever sat through a backend interview or a technical design session for a new service, you know the feeling: the room quickly descends into buzzword bingo. Acronyms fly from every direction: KISS, DRY, YAGNI, the five letters of SOLID, quickly followed by Idempotency, Backpressure, and Circuit Breaker.

Read More
Systems Design for Advanced Beginners: Anatomy of Infrastructure from Simple Monolith to Production Scale

Systems Design for Advanced Beginners: Anatomy of Infrastructure from Simple Monolith to Production Scale

You have shipped a few small websites. You can stand up a CRUD app in Django, Laravel, or Gin in an afternoon. But then you look at the architecture behind a real platform - Stripe, GitHub, or a mid-sized marketplace - and wonder: what is actually behind the curtain, and how does it survive tens of millions of users?

Read More
Lore: Epic Games Open-Sources a VCS Built for Massive Binaries

Lore: Epic Games Open-Sources a VCS Built for Massive Binaries

Game repositories are not web repositories. In an engine the size of Unreal, most of the weight is binary assets, textures, meshes, world partitions, hundreds of MB to several GB each, churned by thousands of artists and developers. Git handles that badly: LFS is a bolt-on dragging whole 2 GB files, dedup is capped by pack deltas, partial clone plus sparse checkout is experimental, and offline means fail.

Read More
Practical System Design: The Quiet Elegance of Boring Architecture

Practical System Design: The Quiet Elegance of Boring Architecture

Junior engineers often assume that impressive system design requires a complex web of microservices, event streaming through Apache Kafka, CQRS patterns, and distributed consensus mechanisms running across every cluster.

Read More
Lies We Tell Ourselves to Keep Using Golang

Lies We Tell Ourselves to Keep Using Golang

In the backend engineering community, Golang (Go) is frequently praised for its radical simplicity. From microservices at Google, Uber, and Grab to core infrastructure projects like Docker, Kubernetes, and Terraform, Go seems to be everywhere. Engineers routinely swap familiar praises: “Go is dead simple to learn,” “Concurrency in Go is practically free thanks to Goroutines,” and “The Go toolchain compiles instantly into a single self-contained binary.”

Read More
Golang disables Nagle's Algorithm by default: A performance trick on unstable networks

Golang disables Nagle's Algorithm by default: A performance trick on unstable networks

Hello everyone, today I want to share with you a funny and sad story that I and many of my fellow system engineers have experienced.

Read More
API Filtering: retrieving data like a coffee connoisseur

API Filtering: retrieving data like a coffee connoisseur

In my first year of working, I once wrote an endpoint GET /api/menus that returned… the entire menu. 200 items every time it was called. The JSON was 1.2MB heavy. The frontend only needed the name and price of 10 active dishes. I remember the first thing my lead said: “You’re sending the entire warehouse to someone who just needs to view the menu, aren’t you?”

Read More