Guides

Short, factual pieces on the mechanics of background jobs on Postgres, written from the code Sturdle runs today. No benchmarks, no competitor names.

  1. Postgres as a job queue

    A job queue needs three things from its store: a claim that two workers cannot both win, a way to notice a worker that died, and a place to keep what happened. Postgres provides all three with features it has had for years.

    Read the guide

  2. Durable steps in TypeScript

    A background job that calls three external services will, some day, fail after the second call. Durable steps are how a job survives that: each step's result is stored as it completes, so a retry replays what was done and runs only what was not.

    Read the guide