Blog

Essays on the problems behind durable background work and the patterns that solve them.

Longer reads on the problems that background work runs into once it has to survive crashes, retries and two systems disagreeing — and the patterns that solve them. They explain ideas rather than an API; the guides cover how to use them in Queuert.

  1. One body, sync and async

    Why a library that runs inside synchronous SQLite transactions and asynchronous Postgres ones writes each function once as a generator, and why it then compiles the generators away.

  2. Side effects after commit

    Where to put work that should follow a commit, and a small per-transaction buffer that runs it only when the transaction lands.

  3. Finishing a job

    The other half of the dual-write problem — why a handler's writes and the record that its job is done drift apart, and how to commit them together.

  4. Typing a job chain

    How to keep a job's input and output types connected across the queue boundary, from the call that starts a chain to the job that ends it.

  5. The dual-write problem

    Why a business write and the job it triggers drift apart when they live in two systems, and what it takes to make them commit together.

esc

Search guides, integrations and every exported symbol.

↑ ↓ to navigate↵ to open