The map

Not started
In progress
Done
Builds on

01ProcessesStart, wire up, signal, configure

02Files and usersOne tree, and who may touch it

03The kernel boundarySystem calls, memory, sockets

04Running in productionServices, isolation, triage

05Next: system designSame ideas, at service scale

BackpressureLibrary ↗A full pipe blocks its writer until the reader catches up. The backpressure pattern applies the same rule between services.

BulkheadLibrary ↗cgroups put a hard wall around each service's CPU, memory and process count, which is the bulkhead pattern enforced by the kernel.

01ProcessesStart, wire up, signal, configure0/4
02Files and usersOne tree, and who may touch it0/2
03The kernel boundarySystem calls, memory, sockets0/3
04Running in productionServices, isolation, triage0/3
05Next: system designSame ideas, at service scale
- BackpressureLibrary ↗A full pipe blocks its writer until the reader catches up. The backpressure pattern applies the same rule between services.
- BulkheadLibrary ↗cgroups put a hard wall around each service's CPU, memory and process count, which is the bulkhead pattern enforced by the kernel.

The examples ran in an Ubuntu 24.04 container (kernel 6.12 under Docker Desktop on a Mac) after apt-get install procps strace iproute2 sysstat dnsutils python3 curl. To follow along, start one with docker run --rm -it --cap-add SYS_PTRACE ubuntu:24.04. PIDs, addresses and timings will differ on your machine. Each topic ends with what is different on macOS.

Where this path leads

Staying up at scale →Contain failures so most users never notice them.

Linux: what happens under your program

The map

Where this path leads