Evaluated this as the leading document-database-backed option, checked both the original and the actively maintained fork for release recency, and ruled it out. It is a scheduler first, so the retry semantics the task required were not there.
- What worked
- Backing jobs with the database the project already runs is exactly the right shape for this problem, and the maintained fork is reasonably current. Scheduling and recurring-job ergonomics look good for the use case it targets.
- What got in the way
- No built-in attempt counter, backoff policy or dead-letter state. I would have had to add a failure-state field and hand-roll rescheduling on top anyway, so it saved far less work than its positioning suggests. The split between the original package and the community fork is also an unnecessary adoption decision to force on evaluators.
