architecture - MSMQ vs Temporary Table Dump -

I know that this question has been asked a little earlier. But I see that I still do not think which path I should go down. This is my scenario, hopefully you can help:

We will have a series of web services which will be hundreds The mobile app will hit at the scheduled time. These services go to both devices with data on the device, and are coming back from them. Data from the devices will need to update a single central SQL Server database, which also feeds many desktop applications and a website.

In order to reduce the amount of time for requests / feedback of these services, we have decided to process the data coming from the devices after this fact, either by pasting it in an MSMQ instance or using serial items By collecting them in a temporary data store and later they are being processed in a windows service

So my choice is there, but here are some other things that you People can give me advice:

• Returns the returned data from the device will not return small message packets that need to be ordered by server side
• Nothing about MSMQ I know but I've written Windows services first. Although I have no problem in choosing MSMQ, if it is necessary.
• I want to keep a response from those devices where in some cases the processing fails, which is due to the data. In this way I can query the data and see whether there is a problem or not, although the device allows the user to add comments which increases the length of the related side in the server side database.

With this information, do you think it is looking for MSWA to learn or should I live with a simple solution?

Chris

MSMQ is not a bad choice and it is not hard to learn But keep in mind that

Cons:

• Every line can only be 2 GB.
• Each message can be fixed using 4 MB (maximum 4 MB limit can be used with MSMQ WCF).
• For Windows only, so that you can limit it to COM-enabled with .NET, C / C ++ or COM library.

Pros:

• Supports Windows Network Load Balancer.
• Microsoft supports the cluster service
• Integrated with Active Directory.
• Ship with Windows.
• Supports transactions.
• MSMQ messages can be tracked by audit messages Windows Event Logs.
• Messages can be automatically authenticated or encrypted, and can be verified and decrypted at reception.

Writing your data on a staging table can be a good idea because you want to log back a message.

When I do not know the other architecture of the system, it is difficult to give advice, but I hope this answer will help a little bit.

Useful Links