The boring architecture that ships
There's a certain kind of conference talk that goes: we had a monolith, we broke it into microservices,
Memory models and why they matter for concurrent code
Concurrent code fails in ways that are hard to reproduce and hard to reason about. A lot of those failures
When to build vs buy: a framework I actually use
Engineering teams relitigate this question constantly: should we build it ourselves or use an existing solution? The debate usually goes
Distributed consensus without the PhD
Distributed consensus gets treated like graduate-level material. The Paxos paper is famously hard to read. Raft was explicitly designed to
Self-hosting everything: what I learned running my own stack
About a year ago I stopped paying for most of the SaaS tools I'd accumulated and started running
Write-ahead logs: the idea behind most durable systems
If you've worked with Postgres, SQLite, or pretty much any serious storage system, you've encountered the
Latency vs throughput: they're not the same thing
These two get conflated constantly, including by people who should know better. They're related but they measure fundamentally
Using Aeron Cluster as a source of truth
Most teams reaching for a consensus system are looking for coordination, leader election, distributed locks, configuration management. Aeron Cluster handles
Consistent hashing: how distributed systems route without a coordinator
When you need to distribute data across multiple nodes, the first instinct is to use a hash function: take a
Why performance isn't always the north star
I spend a lot of time thinking about performance. I use Cap'n Proto over Protobuf because parsing overhead