MQSeries.net :: View topic - MGET Node v Asych Request/Reply Handlers

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MGET Node v Asych Request/Reply Handlers

MGET Node v Asych Request/Reply Handlers

« View previous topic :: View next topic »

Author

Message

wilsonjohn24

Posted: Tue Jun 16, 2009 5:07 am Post subject: MGET Node v Asych Request/Reply Handlers

Voyager

Joined: 02 Feb 2007
Posts: 93
Location: Scotland

Hi,

Scenario/Context:

RR service on broker to an end point system - which will turn around replies in real time

MQ Get ( with itâ€™s thread lock ) to handle a RR scenario v Instantiation of Request + Reply handler flows to process the RR scenario

Does anyone have a valuable insight into this in terms of the Non-Functional or a decision tree?

In my view if the end point system is quick â€“ MQ Get node must be more performant as it does not have to reload flow instance?
But happy to learn

Cheers

John

mqjeff

Posted: Tue Jun 16, 2009 5:25 am Post subject:

Grand Master

Joined: 25 Jun 2008
Posts: 17447

One big consideration is how much state you need to maintain between Request and Reply that is not contained in the Reply Message.

It's a lot easier to store big state in Environment than it is to stick it on a queue and re-read it in your async reply flow.

For example, suppose you have an order that you need to get updated part numbers for... you might have a small request/reply message (give me the new part number for this old one...) but a big order message that needs to be augmented.

wilsonjohn24

Posted: Tue Jun 16, 2009 5:47 am Post subject:

Voyager

Joined: 02 Feb 2007
Posts: 93
Location: Scotland

Fair Point - 1UP for MQ Get in that Scenario ( in terms of it copes with that requirement more simplistically) . I would agree that the MQ Get is a much cleaner pattern of implementation for RR for almost all scenarios involving real time RR.

Purely on the Non Functional how would you see them sizing up to one another?

In terms of Thread locking of two asych process for shorter periods + associated loading of the flow instances V the longer thread lock on the MQGet + lack of swapping( for want of a better term)?

Vitor

Posted: Tue Jun 16, 2009 6:03 am Post subject:

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

wilsonjohn24 wrote:

In terms of Thread locking of two asych process for shorter periods + associated loading of the flow instances V the longer thread lock on the MQGet + lack of swapping( for want of a better term)?

If you had 2 processes you'd have a better chance of breaking the process across different threads, and (presumably) better error recovery as if the application is waiting for an asych response it can wait for 30 seconds or 30 mins.

My 2 cents, other views welcomed.
_________________
Honesty is the best policy.
Insanity is the best defence.

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MGET Node v Asych Request/Reply Handlers

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Protected by Anti-Spam ACP