Open Source Message Queuing System
psicode writes "John Davies has announced AMQ, an effort at JPMorgan Chase & Co. to create an open-source message queuing system that can compete with proprietary message systems like IBM MQSeries and Tibco/RV. The announcement was made at the
annual conference Web
Services on Wall Street during Davies' presentation on February 1. eWeek has an article today with more details and some funny statements about Red Hat, SuSE and Sun possibly integrating AMQ into their "kernel". If JPMorgan Chase & Co. follows through with their announcement and they come up with a suitable open-source license, AMQ could become the Apache of messaging systems."
The trick is in Web Services, I was lead developer on a LARGE project during the DotCom Era (2000 ish) that used Vitria, a great system and its interop capablities blew my mind at first but if we could have utilized web services we would have halved developemnt time, not to mentio forgoing a 1 Million $ Vitria Liscence.
It was cool though, we took about 6 different Apps on TOTALLY Different Platforms, 1 only HP UX, 1 , Two on Solaris ( on on 7 one on 2.51) One on DOS (Yes DOS it only ran there) and a couple on Windows, tied them all together through Vitria then hooked it up to a Web Front end, It was sooo slick the first VC that came to see our Proof of Concept (which was totally functional )gave us 15 Mil in VC
But alas another DotCom fatality, we went from 12 employees to 165 in a year......can you say BAM
How about Joram which is supposed to be pretty good.
--Stupidity is Self Curing!
They should check out tipc for message queueing. TIPC is a reliable messaging protocol designed for clusters. TIPC is fairly transparent whether a task is local or somewhere else on the network.
-Aaron
This post is encrypted twice with ROT-13. Documenting or attempting to crack this encryption is illegal.
AMQ is not to be confused with ActiveMQ. ActiveMQ is an open-source Java JMS implementation. Sun's JMS API defines a unified interface to a messaging system. The problem with JMS is that it is Java centric and Sun did not specify a wire protocol or the binary message format. AMQ is an implementation of a messaging system that is cross language/platform, something that is, from what I know, currently only povided by commercial messaging implementations which are quite pricey.
Amen! I have been crying. Sometimes I even run into people who are ignornat of the history and think EJBs invented the whole idea of distributed objects. It drives me crazy. We had a project at work built with C++/CORBA. It was pretty mature and worked really well. There was another project built on EJBs and we were suppose to get the two products talking. At the first meeting, they had a whole slideshow showing why we should rewrite our stuff with EJBs, showing all the advantages and how you could have remote objects and other things "not possible in C++". We were laughing until we realized there are MANY people who believe that. After we explained to them that their EJBs are more or less CORBA, they looked at us funny and I don't think they really believed us. They figured since they had just discovered distributed objects, it must be new and we were some crazy people who did not understand the power of EJBs...
It's a shame. CORBA is really useful and I think very easy to work with. Granted, there are a few things to learn if you're using the C++ mapping, but if you take the time, it's actually pretty straightforward and consistent.
It seems whenever something is at the point where it is mature and works well, it is thrown out and some new thing is invented to replace it - and they end up re-inventing the wheel many times - usually with less then spectacular results.