Threadmill vs db-scheduler
db-scheduler is a small, dependable scheduler that keeps everything in one database table. Threadmill is a larger engine with queues, concurrency control and a dashboard. Both are Apache 2.0.
Checked on . Sources: db-scheduler README.
Short version
- Choose db-scheduler if you want the smallest possible dependency, you run a database Threadmill does not support, or you need Java 17 or 21.
- Choose Threadmill if you need named queues with their own capacity, per-key concurrency, workflows, deduplication, a dashboard, Redis, or commercial support.
Checked on . Sources: db-scheduler README.
Comparison
| db-scheduler | Threadmill | |
|---|---|---|
| License | Apache 2.0 | Apache 2.0 |
| Footprint | One table, one dependency | Several tables, modular jars |
| One-time and recurring tasks | Yes | Yes |
| Queues with separate capacity | No | Yes |
| Priorities | Optional | Yes |
| Per-key concurrency and mutexes | No | Yes |
| Workflows and deduplication | No | Yes |
| New-job pickup | Polling, 10 seconds by default | Wake signal, 500 ms poll fallback |
| Dashboard | Community project | Included |
| Stores | Eight SQL databases | PostgreSQL, Oracle, Redis |
| Commercial support | No | Available |
Source: db-scheduler README, checked on .