| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JMS, MQ and overall messaging solution architecture |
« View previous topic :: View next topic » |
| Author |
Message
|
| adamopolis |
 Posted: Thu Mar 01, 2007 3:13 am Post subject: JMS, MQ and overall messaging solution architecture |
 |
|
Newbie
Joined: 01 Mar 2007
Posts: 2
|
Hello,
I understand that the JMS API and the MQ API expose about the same amount of functionality, if that is the case, I am wondering why I should a spend lot of money on MQ products.... doesn't it make much more sense to develop a messaging infrastructure directly using JMS? can someone explain to me what are the reasons for investing in MQ? (or indeed other vendors MOM solutions) rather than a raw java implementation?
Would be interested to hear peoples thoughts/opinions on this issue... |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Mar 01, 2007 3:23 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Using WMQ as a JMS provider gives you access to the reliability, scaleability, throughput and all the other good things listed in the IBM sales material.
If your business doesn't require these things, or access to support like this board or indeed IBM itself then a native implementation does indeed provide the same functionality. JMS is a standard after all. 
You might also want to evaluate some of the open source JMS solutions. Might save you reinventing too many wheels.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Mar 01, 2007 3:47 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
MQ's strength is also cross-platform compatibility. You won't be able to use JMS to connect non-JMS applications without something like MQ.
MQ clients are free, so generally a JMS over MQ infrastructure is not expensive, you may only need one queue manager (ideally clustered). |
|
| Back to top |
|
|
| EddieA |
| Posted: Thu Mar 01, 2007 11:59 am Post subject: Re: JMS, MQ and overall messaging solution architecture |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| adamopolis wrote: |
| rather than a raw java implementation? |
There is no "raw Java" implementation.
If you download the MQ Java files from Sun, they are just prototypes. There is NO code. You get the code by installing a Messaging provider that supports JMS, be that IBM, or anyone else.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| jsware |
| Posted: Fri Mar 02, 2007 12:30 am Post subject: Re: JMS, MQ and overall messaging solution architecture |
|
|
Chevalier
Joined: 17 May 2001
Posts: 455
|
| adamopolis wrote: |
| I understand that the JMS API and the MQ API expose about the same amount of functionality, if that is the case, I am wondering why I should a spend lot of money on MQ products.... |
This isn't quite correct. The MQ API provides an implementation, where-as the JMS API only provides an interface specification.
Its abit like saying if I can use JDBC or ODBC to access databases, why would I want to buy DB2? You have to have a database that implements JDBC/ODBC aswell as the JDBC/ODBC API itself.
I believe Sun do provide a reference implementation of the JMS API. I'm not going to comment on any comparison between this and WMQ 
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
