0
i'm using from several time Hangfire with SQL and i don't have any problem.
Classic use cases that i will have are:
From a web app, user enqueue an operation and can check all pending operations. Where operation ends he has a notification via SignalR and can check output of a job. An example is the same Azure Portal, where every operation is enqueued and status is visible in the bell on top right.
Recurring job that runs every few seconds to perform scheduled operations indipendent from user's interaction. Jobs must have a lock concept, so until one is running, nothing else of the same type should start for that user.
Recently i'm moving to Azure, using k8s for some microservices. I think that i will use a microservice with Hangfire, do you thiks that Hangfire and microservices can coexist?
If i don't use Hangfire i have to replicate something similar using Azure Function (high cost), manage a storage for job's state, so will worth it using something different?
How do you manage these scenario in microservice architecture? Bye
I'm working on running Hangfire in a dockerized microservice.
Top comments (0)