HornetQ and ActiveMQ: Messaging – the next generation
The dev teams behind free messaging broker HornetQ and ActiveMQ appear to be considering closer collaboration.
The development powers that be behind free messaging broker HornetQ and ActiveMQ appear to be pondering closer cooperation, if a proposal submitted to the Project Manager of HornetQ, Clubert Suconic, to the ActiveMQ team in the mailing list is anything to go on.
In the missive, Suconic offers to deliver his project code base to the ActiveMQ community, highlighting the extensive number of interactions between the brokers as an excellent foundation for the initiative. There’s also the highly complementary natures of the two technologies, meaning that the within the ActiveMQ subproject Apollo can easily be at least partially implemented in HornetQ.
With the broker protocol STOMP already fully supported by Hornet, it’ll be simple to tack on support for Open Wire too. Moreover, with version 2.0 of the standard Java Message Service (JMS), which appeared after more than ten years of development, HornetQ is also good to go. Thus, the the Red Hat broker also stands to be an asset for involvement in the Apache ActiveMQ project, which has not yet implemented the standard.
So far, Suconic’s offer appears to have gone down with ActiveMQ committers like pizza at a hackathon. Red Hat’s Hiram Chirino, for example, writes:
“Bringing the HornetQ community into [the] ActiveMQ would be exciting for me. We could collaborate and bring together the best features of ActiveMQ, Apollo and HornetQ to create an amazing next generation messaging system AND grow our developer community at the same time.”
Suconic’s suggestion appears to have come at the perfect time, as Chirino has recently been bemoaning the lack of involvement in the Apollo project. The developer attributes this to the fact that the sub-project is implemented in Scala, prompting him to ponder a Java port.
An ActiveMQ – HornetQ union also makes a lot of sense in white-collar corporate terms: HornetQ is a JBoss-So Red Hat projective, and a number of the ActiveMQ committers (11, according to the current list on the site) also come from the House of Hat. A spontaneous, pragmatic merger also saves a lot of time reinventing wheels for the communities on either side. There’s no point in fighting it, this was all clearly meant to be.