search

HangfireIO / Hangfire

An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required
https://www.hangfire.io
Other
9.4k stars 1.7k forks source link

About Hangfire #1548

Open jt4000 opened 5 years ago

jt4000 commented 5 years ago

Hello,

What is special to use Hangfire compare to use the async or similar that is part of dotnet framework?

Is there a differences?

Thank you!

joro550 commented 4 years ago

You could probably break it down like this, Async: You want to go retrieve some information from somewhere and you know it's going to take some time i.e. from disk, but you want to be notified as soon as it's done so you can use that information with the rest of the execution, normally this would result in telling the user that the operation has been completed via some visual prompt.

Hangfire is much like a background service, you can tell it to run and you want the process to go away and do a thing and you don't necessarily want/need to tell the user when the operation has been completed.

You can use Hangfire in multiple different ways though, in-process - where jobs are run in the background of the executing application, or out of process- where you can tell another process to execute the jobs.

Hope this helps separate the two in your mind