IBM MQ Series vs MSMQ?
Enzo Maini
a leg up on MSMQ when it comes to load balancing and auto failover as well
as other features that MSMQ on Windows NT 4.0 does not have.
Even under W2K v5.1 seems to have more enterprise type features. To boot
the NT Install of MQ comes with VB and C++ code that I was able to drop
right in without digging through tons of documentation.
Other than the fact that MSMQ is free, are there any other compelling
reasons?
NOTE: I am not bashing MS I just think their feature list for MSMQ is not on
par with IBM right now.
Doron Juster
First, MSMQ has better performance then MQSeries.
It's better integrated with all other Windows features. It has better
administration tools.
MSMQ Security is built-in, out of the box, no need to buy third party
software.
MTS and COM+ support are built-in too, no need to install support pack.
etc... etc...
Doron
"Enzo Maini" <ma...@earthlink.net> wrote in message
news:uRFUAaYkAHA.1920@tkmsftngp02...
German
More extentions...
"Doron Juster" <doro...@hotmail.com> wrote in message
news:ekZkVPYlAHA.1720@tkmsftngp02...
Andy
I have also been looking at MSMQ and MQSeries. I have to agree that MQSeries
really does seem to be a much better product.
Doron - I would start by looking here
http://www-4.ibm.com/software/ts/mqseries/
and here
http://www2.software.ibm.com/casestudies/swcs.nsf/swgsearch?SearchView&Query
=MQSeries
there are loads of case studies not just a single article comissioned by
microsoft for micrsoft.
and on this public news group "ibmpub.win2k.mqseries"
There is a very large MQSeries user base already and there are many experts
to help you out.
Doron - What do you mean by best performance the link is a microsoft link.
What do you expect them to say about their own products? There is an attack
on this article by a group at the ibm web site basically stating that the
tests were implemented to suit a very specific scenario and don't represent
real world useage.I would look at this document
http://www-4.ibm.com/software/ts/mqseries/library/articles/MQperf.pdf and
specifically at the conclusions section. It states quite explicitly that
MSMQ doesn't scale well and is not that suited to ecommerce.
I would also say that the documentation with MQSeries is Excellent and that
it is a much more cross platform product.
I was originally going to use MSMQ on a project that I'm currently working
on but I have to connect to a machine that can only run an MQSeries client.
I was going to install the bridge between the two products using the
MQSeries to MSMQ bridge that MS have developed as part of the SNA server
product. Unfortunately it is incredibly complex for what it does and it is
actually easier to just use MQSeries on both sides.
The only real advantage to MSMQ is that it is like all other MS products,
its designed to work only with MS products and if it does work on other
platforms its ported normally by third parties. In the case of MSMQ that's
level8 software. So if you intend to use it only with MS products and
platforms, I'd probably say that MSMQ would be a choice worth considering.
Having compared both I would still tend towards MQSeries as its very slick,
in particular ver5.2 which, incidentally uses the MMC snap in. So how do you
conclude that it has "better administrative tools" when they use the same
framework for administration. In addition have you tried to get MSMQ1.0 to
work with MSMQ2.0 (ie NT4 with W2K) and soon to be MSMQ3.0? (It works
sometimes). MQSeries provides an excellent API across all platforms and is
backwardly compatible with all previous versions. As a programmer it is
supported across many languages VB, C\C++, Java an COBOL to name a few, all
of which are supported by plently of code examples.
The built in security is only built in if its running on the windows
platform! You don't need third party software with MQSeries either as it has
security built in also. Even if it didn't, the API is so easy to use that
implementing your own security would be very straight forward.
MQSERIES Version 5.2 has built in support for MTS/COM+, along with many code
examples - no need to install a support pack either!
What's the etc etc ?????
Enzo - I agree that the clustering of MQ servers and therefore queues is a
BIG advantage.
MSMQ is free (perhaps they are taking a leaf out of the Linux World) only if
you ignore the cost of all the other products you need in order to use it
well. E.G. Visual Studio etc etc etc..... I don't think there are any
compeling reasons at all yet.
NOTE: I am not bashing MS I also think there feature list and cross platform
integration for MSMQ is not on par with IBM either
"Doron Juster" <doro...@hotmail.com> wrote in message
news:ekZkVPYlAHA.1720@tkmsftngp02...
Doron Juster
1) Security- Unless I missed it while searching the MQSeries information
center, I didn't find a simple method of sending an authenticated and/or
encrypted message. MQSeries Documentation eventually lead you to the exit
function and 3rd party products. With msmq, it's as simple as adding a
property or two to the message, before sending it. Everything is out of the
box.
2) Interoperability- I do employ everything from msmq1.0 on Win95 to msmq2.0
on Win2k datacenter cluster and couldn't find any compatibility problem. It
just works.
3) Performance- obviously each company publish the numbers that favor its
own products. We don't expect anything else... But it's also obvious that
performance depend on strength of platforms, environment, exact scenario,
etc. In most of my tests, msmq performed better.
4) Bridge installation- I agree with you that it's complex. But you need
only few bridges in a real deployment, and whenever I followed all
instructions in the bridge documentation I was able to install it
successfully.
5) MQSeries 5.2- I'm still unable to install it. It seems that I need to be
domain administrator in order to do it, and my helpdesk stuff really do not
like the idea of granting me so much permissions. But I keep trying.
What's etc .. etc ... ??
Just a shortcut to saying that a lot can be said on this subject, much more
than I can write without spending too many hours...
Best regards
Doron
"Andy" <Mad...@mail.com> wrote in message
news:ORkw$H1rAHA.1284@tkmsftngp05...
Andy
On your points
1) Check out the information center in 5.2. ( I'll look again as I may have
misinterpretted what I read). If you want to use across different PEC and/or
platforms ( not just MS ) then MSMQ also requires the same third party
products for security e.g verisign digital certificates.
2) I say again that if you just use a MS Platform then yes it does just work
but most enterprise solutions don't just use MS.
3) I am pleased that you have elaborated on your original response as it
makes it much clearer as to where and how you qualify performance. If the
performance works for you then fine - but why tell people that it fits all
cases when it clearly doesn't.
4) The bridge doesn't provide complete interoperability in any case, not all
messages work across the bridge. Much better to write a service of your own
to do this stuff. It seems that MS yet again are not that keen to get things
to work with anything not MS.
5) Installs in no time at all (5mins) and it just works, including a cluster
with another machine and yes, you do need to be an Administrator, but what
else is new on NT.
I agree this subject is large but it is dangerous to over simplfy a response
to a request for comment on the pros and cons of two simular but different
products. MS constantly do this, it is annoying.
I think I'll leave this thread alone now and give some of the MS people the
chance to explain why their product is or isn't better than MQSeries - I
would be very interested indeed in that.
Best Regards,
Andy
"Doron Juster" <doro...@hotmail.com> wrote in message
news:#krGJZ5rAHA.1552@tkmsftngp04...
Mike Storey
makes a great deal of sense, (it's hard to cost justify MQS when MSMQ is
free). If you are multi-platform MQS makes things a lot eaiser. I'm a BIG
FAN of the eBP product from Candle Corp. This tool abstracts the underlying
transport (MSMQ, MQS, Tibco etc.) and gives your developers a simplified
API. Using eBP I have successfully built and tested applications under MSMQ,
and then migrated the application to multiple platforms including NT, Unix,
and MVS using both MSMQ and MQ Series. Changing a service to use MQS from
MSMQ is as simple as changing a few entries in a Services Directory, no code
chages are required. If your not sure where tommorow will take you this is a
great way to mitigate the risks inhearant in choosing a single vendors
solution to MOM.
Mike
><>