Closed mookid8000 closed 10 years ago
+1 :)
Who needs this? I don't.
If you need it, you could use RabbitMQ instead of MSMQ - then you get to scale by having competing consumers, which is simpler to set up.
Could still be fun to implement :)
I'd make it more like a load balancer though, so no req/rep between distributor and worker, just distributor forwarding messages to an array of workers
I'd pull in Topshelf and just use MsmqMessageQueue
In order to avoid spending time serializing/deserializing
Simple load balancer POC has been made: LoadBalancerService
- is just a simple lightweight Rebus endpoint that distributes messages between a number of workers, round robin-style.
You can read more in my blog post
Implement a distributor process. This most likely involves doing the following:
Worker
be able to be inworkerMode
\ Must request work from a distributor when it starts and after finishing processing each messageworkerQueue.Send
that message to the workerWas that it?