| Author |
Message
|
| skytorch |
 Posted: Thu Sep 26, 2002 12:25 pm Post subject: Design issue: using Unix IPC Msg vs MQseries |
 |
|
Apprentice
Joined: 10 Jun 2002
Posts: 47
Location: New York City
|
Hi,
How do you compare cons and pros of Unix IPC messaging implementation and MQ impl ? The performance of Unix IPC Messaging is a lot faster than MQ's (e.g. in-queue or de-queue rate). So what are the downside using Unix IPC Messaging ? (we're using C, Solaris 8 and MQ 5.2).
Thanks in advance.
Sky |
|
| Back to top |
|
 |
| dgolding |
| Posted: Tue Oct 01, 2002 2:17 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
Using the IPC mechanism is great for fast, synchronous applications, but is not fault tolerant. If the receiving side is not there than nobody can play 
MQ gives you the robustness, and is an asynchronous or"psuedo-synchronous" method - if you can fire off your data and forget about it ("fire-and-forget"), use MQ.
My $0.02 |
|
| Back to top |
|
|
| mrlinux |
| Posted: Tue Oct 01, 2002 3:29 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Well the big con is that you are confined to the box you are running the application. no being able to send messages to another box.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| dgolding |
| Posted: Tue Oct 01, 2002 5:08 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
| Unless you doing a socket read/write application - were the seperate ends can be anywhere. I included the use of IPC with those. |
|
| Back to top |
|
|
| mrlinux |
| Posted: Tue Oct 01, 2002 5:59 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Well then that adds another con, both applications have to be up and running for the sending side to work. also now you have to handle network errors and retries in the code
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| dgolding |
| Posted: Tue Oct 01, 2002 6:55 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
That's what I meant about not being fault tolerant - if the receiving side is not there, then no show.
If the application HAS to be synchronous/real-time (sub-millisecond response, that sort of thing) then MQ isn't necessarily the best or only way to go.
Another downside for the socket mechanism is personally I find the connect, open, put API from MQ easier to code then the bind, listen&accept of socket I/O....  |
|
| Back to top |
|
|
|
|
