dotnet distributed apps: MSMQ vs async sockets -- dotnet distributed apps

MSMQ vs async sockets

vijragv NO[at]SPAM hotmail.com
12/17/2003 5:38:49 PM

dotnet distributed apps:

Hi all

I am trying to weigh in the pro and cons of using msmq or async
sockets for the design below.

Essentially,
We have three executables; one is a nativeapplication.exe,
SingleMachineController.exe and MultiMachineController.exe
• We have a number of nativeapplications(that is written in c++) that
are each in its own processes running on a single machine. Each
nativeapplication needs to send/receive messages from/to its
SingleMachineController(.net application) running on the same machine.
• Each SingleMachineController in turn needs to send/receive messages
from/to the MultiMachineController(.net application running on a
different machine) and to the nativeapplication.
• MultiMachineController needs to send/receive messages from/to its
singleMachineControllers

I am trying to figure out whether to use async sockets or msmq for
inter process communication. Any pointers to information that relate

Re: MSMQ vs async sockets

Paul Glavich
12/20/2003 9:00:48 PM

Depends. Sockets would be faster. MSMQ would be easier (IMHO) and you would
also have the ability to have one process offline or not runnnig (MSMQ would
still process and queue up msgs) until the other app was ready to read them.
Also, MSMQ is transactional, if you need that functionality. Async sockets I
see as more "raw" in terms of development (hence the speed increase) but its
functionality is dependent on how much work you want to do. MSMQ does a hell
of a lot "for free".

--
- Paul Glavich

[quoted text, click to view]