If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Pros/Cons of using DB2 connect Vs MQ architecture.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 12-15-09, 07:44
siddz84 siddz84 is offline
Registered User
 
Join Date: Dec 2009
Posts: 5
Pros/Cons of using DB2 connect Vs MQ architecture.

Hi,

I would like to know the advantages & disadvantages of migrating my application to DB2 connect from the MQ architecture.

Our application accesses over 50 different tables for generating over 12 different XML layouts for almost every "account view" request. I am thinking over the possibility of separating out each layout into distinct stored procedures so that they can be accessed via DB2 connect.

Our application receives around 300,000 "account view" requests/day.

Before even getting into the research of how suitable it would be for our application, I wanted to hear from the experts in this forum what they think would be upside & downside of making this shift.

Basic thoughts :
Upside :
Cutting down on expense on CICS.
Cutting down on MQ processing.
Faster response time.

Downside :
Limitation on the amount of data transfer/message using DB2 connect.
Limitation on the number of parallel threads that can be processed.
A possible increase in the DB2 expense.

All possible thoughts, advise, suggestions are most welcome.

Thanks,
Siddharth.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On