A durable job queue in your database
Why a job table in the database you already run beats a message broker for most products, and the delivery guarantee that constrains every handler.
Written from our own codebase rather than from memory. Mostly PostgreSQL, background work and the decisions we would defend in a code review.
Why a job table in the database you already run beats a message broker for most products, and the delivery guarantee that constrains every handler.
A tenant filter you have to remember is a bug with a delay on it. Here is an isolation model that fails closed, and the detail that decides it.
Why a fee module can ship without a payment gateway, and what matters far more to a school office than a pay-now button on the parent app.
A description of the problem is enough to start. You will get a reply from one of the people who would do the work.