Bulkhead Pattern

ELI5 — The Vibe Check

The bulkhead pattern isolates different parts of your system so one failure doesn't sink everything. Named after ship bulkheads that contain flooding. If your recommendation engine crashes, it shouldn't take down checkout. Separate thread pools, connection pools, and resources per component.

Real Talk

The bulkhead pattern isolates system components into independent pools of resources (threads, connections, memory) so that a failure in one component doesn't cascade to others. Like watertight compartments in a ship, each bulkhead contains failures locally. Implemented via separate thread pools, connection pools, process isolation, or container resource limits.

When You'll Hear This

"The bulkhead pattern kept checkout running even when the recommendation service OOM'd." / "Give each downstream service its own connection pool so one slow service can't exhaust all connections."