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-schedulerThreadmill
LicenseApache 2.0Apache 2.0
FootprintOne table, one dependencySeveral tables, modular jars
One-time and recurring tasksYesYes
Queues with separate capacityNoYes
PrioritiesOptionalYes
Per-key concurrency and mutexesNoYes
Workflows and deduplicationNoYes
New-job pickupPolling, 10 seconds by defaultWake signal, 500 ms poll fallback
DashboardCommunity projectIncluded
StoresEight SQL databasesPostgreSQL, Oracle, Redis
Commercial supportNoAvailable

Source: db-scheduler README, checked on .