Threads versus instances, handling MSMQ

[jwhite68]

I am building an application in C# that will manage many thousands of incomming messages. This will be managed with MSMQ - message queues.

I would like to know whether its better to create a new instance of the main process (component) for every message received or whether to have just one instance that will spawn new threads as soon as messages are recieved to process a particular message.

Assuming that hundreds of thousands of messages could ce received and processed, just trying to understand whether single instance, multiple threads is a better route than multiple instances.

Thoughts?

 

[jmeckley]

check out NServiceBus. This project solves the problem you are describing. I believe there is also MassTransit which solves the same problem, but it's still in it's infancy.

Jason Meckley
Programmer
Specialty Bakers, Inc.

 

[chiph]

Are you talking about multi-threading the writing to the MSMQ, or the reading from it?

Because when reading from it, you can use the standard asynchronous programming model that the framework gives you, and you'll be in good shape, performance-wise.

Be aware that multi-threading means that some of your messages will be processed out of order.

Chip H.


____________________________________________________________________
www.chipholland.com