I am looking use case where you will use Hangfire on a Net Core Web.API App, which already spawns a new thread for every connection. We have a API for creating PDF (People make Rest request and we return a PDF). Each request takes about 3 to 30 seconds depending on how busy the server is. Thanyou
I’m sorry, but your question doesn’t make any sense to me: asp.net always was multi-threaded but this has nothing to do with why one would want to use hangfire. Could you rephrase and specify exactly what you mean?