Apache Formalizes Distribution of an MQ Series Equivalent - Open Source Software Up the Stack

« Sunday Morning Reading Goes Open Source | Main | Talking with the Open Solutions Alliance »

February 20, 2007
Apache Formalizes Distribution of an MQ Series Equivalent

Apache says its ActiveMQ effort has graduated from the Incubator to become a top level project (TLP). The Apache ActiveMQ, termed a so-called enterprise service bus (ESB) in some press articles, is a distributed messaging system that will support clients in Java (JMS), C++, Ruby, Python and other languages. Apache ActiveMQ is said to fully support JMS 1.1 and J2EE 1.4.

(I say so-called ESB for two reasons:
-- There is some question among those purists such as me whether Apache ActiveMQ is really an ESB
-- An ESB is just a type of MOM (message-oriented middleware) to me anyways)

Still, moving up the stack is an important step for Apache, which cut its teeth and claimed its fame on the web server of the same name. Now, it is working at additional levels of modern middleware (most notably with the IBM Gluecode application server development team as part of the Geronimo project). ESB and/or MQ-level activity can be thought of as even "higher level" than a web server or an application server. I don't want to characterize it in a way that implies that technical success might be harder to accomplish but I would say corporate acceptance might be harder. The heritage MQ brand's longheld meaning is one of "bullet proofness" in enterprises. And with any level of ESB-like functionality (whatever us purists say), we are beginning to see OSS supporting applications that enterprises really consider mission critical. The involvement of a key Amazon developer might help allay any CIO fears.

In terms of commercial backing (see my February 16 post on the taxonomy of OSS and the importance of commerical backing), Logic Blaze and its Fuse project are the only one mentioned on the Apache.org site at this time. Optaros also say it supports ActiveMQ via its SOA practice (and Optaros is a purist like me, making a distinction between an MQ-like message broker and a true ESB). If you know of any sources of ActiveMQ support, let me know via the comments link below.

In terms of OSS development efforts, the ActiveMQ project competes with the Celtix ESB effort out of CORBA-expert Iona (which, to further illustrate the intertwining of the OSS culture, sprung out of Apache "competitor" ObjectWeb). There is also a Mule effort.

In terms of competing closed source products, almost all the leading software suppliers have this covered both ways. Progress' SONIC ESB is the most well known of the commerical suppliers because its Dave Chappell literally wrote the book (and I would say Progress' SonicMQ is acually more the direct competitor). But IBM, Oracle, SAP, Microsoft, BEA, TIBCO, Software AG and many more (including small pure-play providers such as Fiorano) provide ESBs and older generation MQ-like products as separately priced products or embedded elsewhere int their middleware offering--or most likely both. Progress' execs made the point to me in researching this subject that the big win for the commerical suppliers is the way in which they use OSS as components (Axis was cited as an example) and give back to the community with quality control on those components. Progress also participates by providing dedicated development resources; they have a guy on the Apache Synapse project for example.

Apache ActiveMQ is released under the Apache License, Version 2.0.

I opine that although the free download is as simple as any other OSS action, users are really getting into areas where documentation, training, and most important, previous experience are critical. Neither an ESB nor an old fashioned MOM is something you play around with in the sandbox for an afternoon even if it's free.

Tags:

Posted by dennisb in OSS Development |Digg This|Add to del.icio.us

Trackback Pings

TrackBack URL for this entry:
http://www.ebizq.net/mt/mt-tb.cgi/1397

Comments

Dennis, you are correct, ActiveMQ is a messaging infrastructure, not an ESB. ActiveMQ is included in Apache ServiceMix (in incubator status) which is an ESB. ActiveMQ and ServiceMix are from the same core group of developers, and both are professionally supported by LogicBlaze (packaged as FUSE).

While ServiceMix and Celtix do compete, Celtix actually ships with ActiveMQ for messaging. One of the most interesting things about open source (IMO) is the environment of "co-opetition".

Posted by: brenda michelson at February 21, 2007 05:56 PM | Permalink

Actually Apache ActiveMQ is a JMS 1.1 compliant message broker (with many advanced features). Apache ServiceMix is a Java Business Integration (JBI) compliant ESB that is built on top of ActiveMQ. The distinction between the two is the same distinction between standard messaging vs. intelligent routing and transformation of messages - ActiveMQ is the message broker and ServiceMix is the ESB. Please see the respective web sites for more information:

http://activemq.org/
http://servicemix.org/

Posted by: Bruce Snyder at February 22, 2007 06:29 PM | Permalink

Note that the Apache ActiveMQ project never claims to be an ESB, its a Message Broker.

Though Apache ServiceMix does claim to be an ESB :)

Posted by: James Strachan at February 23, 2007 02:07 AM | Permalink

Thanks, James.

From my post, I think you can see that I agree that ActiveMQ is more of an old fashioned MOM than an ESB. It must have been some of the press coverage of it that caused me to say otherwise. But either way, the "moving on up" comment is the key one.

Thanks again

Posted by: Dennis Byron at February 23, 2007 03:59 PM | Permalink

I am trying to understand what I can do with ESB that I cannot do with MQ. If my needs are reliable, scalable, controlled msg flow between applications of my Company ActiveMQ seems to just fit the bill. Why would I want to use ESB ?

I have an even more fundamental question. Why do I need SOAP ? AppX can simply perform an HTTP ping with name value pairs and AppB can send the response. What value does SOAP bring here ?

Of course the above is tight coupling, so I would put in ActiveMQ in the middle. Why do I need ServiceMix ?

It would be great if someone gave me some pointers regarding the above.

Regards,

Response:

Sanjiv, our site is about trends and business issues rather than providing technical advice so I would advise posting your question to the Apache MQ site directly. There are guys there who also worked on the Apache Synapse ESB so they will be very specific about the differences.

I think you are right that "If my needs are reliable, scalable, controlled msg flow between applications of my company, ActiveMQ seems to just fit the bill." ESBs and SOAP come into the picture when there are services involved.

Posted by: sanjiv at September 7, 2007 07:28 AM | Permalink