MSMQ vs Temporary Table Dump

Question

I know this question has been asked a bit before. But looking around I still cant make my mind up which route I should go down. Here\'s my scenario, hopefully you can help out:<

Answer 1

MSMQ isn't a bad choice and is definitely not difficult to learn, but keep in mind that there are some constraints that you should be aware of.

Cons:

• Each queue can only be 2GB.
• Each message 4MB (altough the 4MB limit can be fixed by using MSMQ with WCF).
• Only for Windows so you're limited to use it with .NET, C/C++ or COM library for COM-enabled environments.

Pros:

• Supports Windows Network Load Balancer.
• Supports Microsoft Cluster Service.
• Integrated with Active Directory.
• Ships with Windows.
• Supports transactions.
• MSMQ messages can be tracked by audit messages in the Windows Event log.
• Messages can be automatically authenticated (signed) or encrypted upon sending, and verified and decrypted upon reception.

Another approach you might want to consider is writing your data to a staging table. This might be a good idea since you want to have a message back log.

It's difficult giving advice when I don't know the rest of the system's architecture, but I hope this answer will help a little.

Useful links

Programming MSMQ in .NET - Part 1
Using MSMQ with WCF