What is Hangfire?
It is an open-source framework that helps you to create, process and manage your background jobs, i.e. operations you don't want to put in your request processing pipeline. It supports all kind of background tasks – short-running and long-running, CPU intensive and I/O intensive, one shot and recurrent.
Hangfire is a tool in the Background Processing category of a tech stack.
Hangfire is an open source tool with 4.9K GitHub stars and 1.1K GitHub forks. Here’s a link to Hangfire's open source repository on GitHub
Who uses Hangfire?
9 companies reportedly use Hangfire in their tech stacks, including Gbase, TrackJS, and PagueVeloz.
7 developers on StackShare have stated that they use Hangfire.
Why developers like Hangfire?
Here’s a list of reasons why companies and developers use Hangfire
Be the first to leave a pro
Hangfire Alternatives & Comparisons
What are some alternatives to Hangfire?
See all alternatives
RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
Performance, scalability, pub/sub, reliable integration, workflow orchestration, and everything else you could possibly want in a service bus.
Sidekiq uses threads to handle many jobs at the same time in the same process. It does not require Rails but will integrate tightly with Rails 3/4 to make background processing dead simple.
Background jobs can be any Ruby class or module that responds to perform. Your existing classes can easily be converted to background jobs or you can create new classes specifically to do work. Or, you can do both.
Beanstalks's interface is generic, but was originally designed for reducing the latency of page views in high-volume web applications by running time-consuming tasks asynchronously.