Scaling Hangfire can be done in two ways: Increase the number of worker threads per server, or increase the number of servers. You also need to be aware of the constrains of the underlying host. That could be a Docker, VM, or a Physical Host. Regardless, there are constraints of CPU and memory that you will likley need to look at to determine the right number of worker threads per hangfire server. You can scale out further by deploying many hangfire servers on different underlying hosts. Tip: Be aware of moving the bottleneck and be sure that downstream services can handle the extra load.

🔔 Subscribe: https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw?sub_confirmation=1

💥 Join this channel to get access to source code, demos, and slides!
https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw/join

📝 Blog: https://codeopinion.com

📚 Book Recommendations

Domain-Driven Design
https://amzn.to/2QwG8sb

Patterns of Enterprise Application Architecture
https://amzn.to/3d8kMJj

Refactoring: Improving the Design of Existing Code
https://amzn.to/2NVdP5Q

Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith
https://amzn.to/3srUuZ6

RESTful Web Clients: Enabling Reuse Through Hypermedia
https://amzn.to/3d8Q96B

0:00 Intro to Producers & Consumers
1:39 Worker Threads
3:35 Multiple Hangfire Servers
5:05 Downstream Services

CodeOpinon: https://codeopinion.com
Twitter: https://twitter.com/codeopinion

#hangfire #dotnet #backgroundjobs

#hangfire #dotnet #backgroundjobs #scaling hangfire