Building Reactive Systems with Akka
Bonér on what 'reactive' actually means once you take it past the buzzword: responsive, resilient, elastic, message-driven systems built on actors.

The World Is Asynchronous
Vogels makes the case that loose coupling and event-driven architecture aren't a style choice — they're how the world actually works.

When To Use Microservices (And When Not To!)
Newman and Fowler talk through the cases where microservices earn their keep — and the much larger set where they don't.

The Soul of Erlang and Elixir
Sasa Juric on what actually makes the BEAM special — isolated processes, message passing, supervision — and how those primitives produce systems that stay up while the world burns around them.

Distributed Systems Are a UX Problem
Treat reframes consistency, latency, and partial failure as user-facing concerns — and shows what good distributed-system UX looks like.

Building a Distributed Message Log from Scratch
What you learn when you implement a Kafka-style log yourself: replication, leader election, fsync semantics, and the limits of 'just use a queue.'

The Language of the System
Hickey on the fact that the language inside your process is rarely the language between your processes — and what that should imply for system design.