Use Hanfire with multiple applications in one server

[mdmoura]

Hello,

I have 4 ASP.NET MVC 5 applications on a server where I want to use Hangfire.

Do I need to have the Hangfire tables in each application SQL database?

Or can I have a Hangfire database and all application use that one?

Thank You,
Miguel

[odinserj]

My recommendation: use separate databases for different code bases. Otherwise workers of one application may encounter background job that is intended for other application, and this will result to a failed job.

Hangfire itself is responsible for maintain its tables. It automatically deletes old jobs, purges outdated statistics and maintains its schema. So this recommendation will not result in additional maintenance problems.

[CrazyPyro]

Even if you use separate databases (which I agree you should) you still need to be careful with the configuration of these multiple applications, or else you might run into this problem: https://github.com/HangfireIO/Hangfire/issues/223

[AndersRisager]

I have the same issue and I have posted a possible solution here:

Different versions of Application against same

I am implementing Hangfire in our solution and we are using a build and application server. That gives us a lot of versions for the same application, that all run against one DB. So all the jobservers will race to fetch the job when it is created, without knowing if they have the correct code to execute the job. I would like the servers to only fetch jobs for that version. Possible solution: Add a column “Version” to the Job and Server table to identify a specific version of the application.…

Also, the ServerName limit in version 1.43 is 50, but the last five chars. is added by Hangfire as an application id eg. “:9018” so you can only assign 45 characters. It fails silently so take extra care here ; )