ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Java / JMS » MQ API vs JMS API

Post new topic  Reply to topic
 MQ API vs JMS API « View previous topic :: View next topic » 
Author Message
rparti
PostPosted: Tue May 22, 2007 7:40 am    Post subject: MQ API vs JMS API Reply with quote

Voyager

Joined: 05 Oct 2005
Posts: 86
Location: U.S.A.

I was just thinking about the pros and cons of MQ API vs JMS API. Why would one consider one vs the other? I compiled a list, and was wondering if anyone could add to it.

Advantages of using MQ API
1. More control over the MQGET's and MQPUT's and SYNCPOINTS
2. More control over the MQ objects like reading MQ properties (but that would be useful if we are building MQ Administration software.
3. Good option if you don have a JNDI server installed

Advantages of using JMS
1. Vendor independence hence applications are more portable

Thanks.
Back to top
View user's profile Send private message
marcin.kasinski
PostPosted: Tue May 22, 2007 11:45 am    Post subject: Re: MQ API vs JMS API Reply with quote

Sentinel

Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw

I could add...

Advantages of using MQ API
- better performance little bit
-general more control

Advantages of using JMS
- pool managing

Disadvantages of using JMS
- not implemented all native functionality (eg: segmentation)


There are also non technical things which you should consider.

I personally use MQ native API because... I like it.
I used to it. For me it easier.

I use JMS only with MDB.
_________________
Marcin
Back to top
View user's profile Send private message Visit poster's website
rparti
PostPosted: Tue May 22, 2007 2:14 pm    Post subject: Reply with quote

Voyager

Joined: 05 Oct 2005
Posts: 86
Location: U.S.A.

Thanks for your reply Marcin

marcin.kasinski wrote:


Advantages of using MQ API
- better performance little bit


I thought that too, until I found the following link

http://www.sun.com/software/products/message_queue/wp_JMSperformance.pdf
This compares performance of Sun JMS with Websphere MQ Java
According to this document, the performance of JMS is better than Websphere MQ Java. Don't know what to say here.

However, Page 18 of the following link shows a comparison of MQI calls, WMQ Java and JMS and - This document was compiled by IBM

ftp://ftp.software.ibm.com/software/integration/support/supportpacs/individual/mp7g.pdf

It says in the page that the two Java-based APIs are very similar, with the WMQ Java peaking 3.0% above the JMS API. The MQI interface provided better overall performance peaking 13.7%
higher than JMS, which is what u mentioned as well

I also agree that WMQ java offers more control.

What about SYNCPOINTS? I dont think JMS offers SYNCPOINTS although it does offer Transacted Messaging
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Tue May 22, 2007 2:23 pm    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Syncpoints are the same thing as transacted messaging.

Comparing performance of the Sun JMS Provider with the WebSphere MQ JMS Provider is comparing contact admin to apples. It's entirely likely that the Sun JMS Provider may run faster than WebSphere MQ when Sun is doing unreliable messaging and MQ is doing persistent messaging. But unless you really understand the testing that was done, and the conditions that are being compared, you should take any such statements as pure marketing. Your own experience will be completely different.

Use JMS when you're running code in a J2EE container.

Use WMQ Java API when you're writing things that need fine grained control of WMQ.

Use your own best judgement when deciding for things that are somewhere in between.

Do not make any decisions based on performance without clear performance requirements, test plans, monitoring and analysis, and target metrics.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
rparti
PostPosted: Tue May 22, 2007 2:58 pm    Post subject: Reply with quote

Voyager

Joined: 05 Oct 2005
Posts: 86
Location: U.S.A.

Thanks for the insight Jeff.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Java / JMS » MQ API vs JMS API
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
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.