[tonyhb]

Inngest's Durable Endpoints aim to solve the durable API problem without messy DB txns, all within some tolerance: https://www.inngest.com/docs/learn/durable-endpoints.

Other than that, yes, durable execution does all of this for you.

TLDR on Durable Endpoints: you can automatically use steps in API endpoints which checkpoint state in the BG, and then retry on failure. This means you can run jobs in the background _somewhat_ transactionally (somewhat because there's delay between checkpointing) to minimize any tradeoffs here. And, if you want full transactionality, don't buffer checkpoints in the BG and instead do it synchronously.

Also, Redis is good for medium scale load. We're hitting millions of RPS (aggregated) on our services (I work at Inngest) and it doesn't scale so well at this load, at all. We had to invest in other infra.