Multi-tenant application

question
1

Any suggestions how to handle multi-tenant applications? We have a SaaS type of application (ASP.NET MVC) where one code base handles many clients. Each client has a separate database though. Having separate Hangfire database for each client (or include Hangfire tables in the client database) sounds like an overkill because same Hangfire server will need to monitor hundreds of data sources. Thus I’m inclining towards single Hangfire database, but in that case I need some support from Hangfire API to distinguish jobs for different clients (forgot to mention that I need to display running/successful jobs within app).

Thanks!

2

We have multitenancy and I simply append recurring jobs with a “location” for identificaiton and then an implementation that holds which connection that will be used and pass that in which then in turn passes it to our data layer inside the job.