Delayed Job vs Hangfire
Delayed Job
github.comHangfire
hangfire.ioSide by side
| Figure | Delayed Job | Hangfire |
|---|---|---|
| Price from | Free | $41.67/mo |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | Yes |
| Web | — | Yes |
| Windows | — | Yes |
| Linux | — | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 4 |
| Spec score · Task Queue Software | 7.6 (#26) | 9.1 (#2) |
| Purpose | Delayed::Job is a database-backed priority queue for running longer tasks asynchronously in the background. | Hangfire performs background processing in .NET and .NET Core applications without requiring a Windows Service or separate process. |
Plans
In their own words
Delayed Job
Delayed Job has no write-up on Specifiction yet; its figures are above.
Hangfire
Hangfire runs background jobs in.NET and.NET Core applications without requiring a Windows Service or a separate process. It supports fire-and-forget, delayed and recurring jobs, as well as continuations, and stores jobs persistently. SQL Server and Redis are officially supported storage options, with other community-driven implementations also available. A built-in web dashboard shows processing activity and each job's state. Hangfire describes its processing as at-least-once, with automatic retries after unhandled exceptions or application termination. It can run across multiple machines and coordinates their work automatically. Listed integrations include ASP.NET, ASP.NET Core, console applications, Windows Services, WCF, Nancy and ServiceStack. Hangfire Core is open source under LGPLv3 and free for commercial use. The Open plan is free. Startup costs $500 a year, Business $1,500 a year, and Enterprise $4,500 a year, all billed per organization annually. Pro adds batches and batch continuations; Ace adds throttling features for concurrency and rate limits. Dashboard access is local by default, so remote access needs authorization configuration.