// a blog about systems that stagger but don't fall

lurch.dev

Notes on resilience engineering, fault tolerance, and the endearing wobbliness of distributed systems that stagger under load and somehow keep walking forward.

v1.4 // unstable build: passing* uptime: 99.2%
WARN  [render]  section_alignment: off by 4px  -- continuing
+4px field_note // 042

The day our queue forgot how to count

2026-03-18 · 7 min read · distributed-systems

A monotonically-increasing counter is one of those things you take for granted -- until a kernel-level clock skew shoves your sequence numbers sideways and the queue starts handing out duplicate IDs to anyone who'll listen. Here's how we discovered it, why our retry logic actually helped, and what we wrote down so it never happens again.

read the whole thing →
-2px field_note // 041

Backpressure is a love language

2026-03-04 · 11 min read · streaming

Every consumer that says "slow down please" is doing the rest of the pipeline a favour. We swapped a fire-and-forget producer for one that actually listens, and watched p99 latency drop by half. Pictures included, because backpressure deserves a comic strip.

read the whole thing →
INFO  [stack]   recovering gracefully... lurching ahead
+6px pattern // resilience

Bulkheads, but make them friendly

pattern catalogue · updated weekly

A bulkhead in a real ship looks intimidating: thick steel, heavy bolts, a vibe of do not approach. In code, it can be a twelve-line wrapper around a thread pool. We collect friendly versions of intimidating patterns -- circuit breakers that say sorry, retries with manners, timeouts with a sense of humour.

  • Circuit-breaker (apologetic variant)
  • Retry with jittered patience
  • Bulkhead, narrative form
  • Hedge requests & learn forgiveness
browse the catalogue →
OK    [hero]    still standing -- proceed to next section
+0px post-mortem // 17

The 4-byte typo that ate Tuesday

2026-02-22 · incident write-up

We deployed a config change. The config change had a typo. The typo looked like a flag. The flag was real. Reader, the flag was real.

full timeline →
+3px post-mortem // 16

When DNS went on holiday

2026-01-30 · incident write-up

DNS didn't break. DNS just got slow. Slow enough that everything that depended on DNS got slow. We learned a lot about our own timeouts that day.

full timeline →
-4px post-mortem // 15

A leap second walks into a bar

2025-12-31 · incident write-up

The bartender says, "we don't serve your kind here." Then he serves it anyway, because the bar is a Linux box and Linux boxes have to serve everyone, even the leap seconds.

full timeline →
WARN  [grid]    column_alignment drift +6px -- aesthetic intent
+2px about

Why "lurch"?

Because real systems don't glide. They lurch. They lean too far one way, catch themselves, lean back. The good ones make it look intentional. The great ones turn the lurch into a walking gait.

This blog is written by a small team of engineers who think the interesting part of distributed systems isn't the diagrams -- it's the moment the diagram gets it wrong and the system has to figure something out anyway. We collect those moments.

--- the lurch.dev crew _
-3px subscribe

Get new posts in your inbox

One letter, every other week. No tracking pixels. Frequently typo'd. Always free.

OK    [footer]  end-of-stack reached -- system stable