Two Workers Both Held the 'Only One' Lock. The Clock Was Never Synced.

<p>A worker acquires a distributed lock, starts updating a document, and freezes for 12 seconds.</p> <p>Its 10-second lock expires. Another worker acquires the same lock, finishes

<p>A ghost lock blocked every cron trigger for 6 hours after a Korean ad-network API took 45 seconds to respond — 15 seconds past the Workers wall clock limit.</p> <p>The Workers

<p>I was brushing my teeth on a Tuesday morning, phone propped on the cistern, when the idea dropped: a better title for Sunday's sermon. I opened the app, started a note on

<p>Session affinity is a simple idea: route a client to the same backend node it used<br /> last time, so state that lives on that node (a cache, a connection, an in-memory<br />

<p>If your third-party OAuth integration works for days and then dies with <code>{"error":"invalid_grant"}</code>, the cause is usually not clock skew, a wrong client secret, or

<p>Another one from the same one-person-AI-company setup I've written about before: Claude Code builds and maintains the code, several agents run unattended on a schedule,

<h2> The Problem We Were Actually Solving </h2> <p>I still remember the day our server count hit 50 nodes - it was the point at which our distributed lock management started to