Need advice about which tool to choose?Ask the StackShare community!

Hangfire

Stacks27

Followers11

+ 1

Votes0

NServiceBus

Stacks20

Followers8

+ 1

Votes0

Add tool

Hangfire vs NServiceBus: What are the differences?

Hangfire: Perform background processing in .NET and .NET Core applications. 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; NServiceBus: *Enterprise-grade scalability and reliability for your workflows and integrations *. Performance, scalability, pub/sub, reliable integration, workflow orchestration, and everything else you could possibly want in a service bus.

Hangfire belongs to "Background Processing" category of the tech stack, while NServiceBus can be primarily classified under "Message Queue".

Hangfire is an open source tool with 4.93K GitHub stars and 1.12K GitHub forks. Here's a link to Hangfire's open source repository on GitHub.

According to the StackShare community, Hangfire has a broader approval, being mentioned in 9 company stacks & 9 developers stacks; compared to NServiceBus, which is listed in 9 company stacks and 6 developer stacks.

- No public GitHub repository available -

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.

What is NServiceBus?

Performance, scalability, pub/sub, reliable integration, workflow orchestration, and everything else you could possibly want in a service bus.

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Hangfire?

Why do developers choose NServiceBus?

Be the first to leave a pro

Add a pro

Be the first to leave a pro

Add a pro

Be the first to leave a con

Add a con

Be the first to leave a con

Add a con

What companies use Hangfire?

What companies use NServiceBus?

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Hangfire?

What tools integrate with NServiceBus?

No integrations found

What are some alternatives to Hangfire and NServiceBus?

RabbitMQ

RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.

Azure Functions

Azure Functions is an event driven, compute-on-demand experience that extends the existing Azure application platform with capabilities to implement code triggered by events occurring in virtually any Azure or 3rd party service as well as on-premises systems.

Sidekiq

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.

Resque

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.

Beanstalkd

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.

See all alternatives

Decisions about Hangfire and NServiceBus

No stack decisions found

Related Comparisons