On Thu, Jul 19, 2012 at 11:14 AM, Gordon Sim <[email protected]> wrote:
> On 07/19/2012 03:48 PM, Hiram Chirino wrote: > >> I'm interested in using Proton in the ActiveMQ's Apollo message broker. >> > > Great! > > I don't know how closely you are following this thread, but I've been following it since the Proton bits interest me very much. > what would your view be of the feasibility of evolving to a single AMQP > based broker at Apache? We have two brokers already at Qpid and are very > concious of duplicated effort. I don't think I'm qualified to comment on the pros and cons of your the vs C++ based AMQP broker. So I'm not sure if those 2 could be consolidated in some way. > The nature of AMQP 1.0 makes it less restrictive in terms of broker > 'model'. > A very good thing. > I certainly don't have anything like a concrete proposal. I'm just > thinking aloud, noting that combining efforts if possible would be ideal, > and wondering how far that view may be shared. Well, from a ASF point of view there is some duplication of effort in maintaing a Qpid Java broker and a ActiveMQ java broker. They both target similar users (folks who like running apps on the JVM) and use cases. This situation will be even more intese once ActiveMQ implements the AMQP 1.0 spec. >From my point of view, and it's a VERY biased and insensitive point of view (sorry if I offend anyone): <dream> The ideal split of *Java* tech bits across the projects would be to have QPID implement all the non-broker specific libs like Proton, clients, bridges and perhaps even proxies/intermediaries. (Here's where the very biased bit comes in...) Then QPID folks then implement/maintain an AMQP java broker on using ActiveMQ's Apollo project and Qpid's non-broker specific bits. In Apollo the protocols are implemented a plugins on top of the core. You could take the Apollo distro, strip out the STOMP protocol it ships, and then slap on your AMQP implementation. So you could end up with a broker which focused on just AMQP hopefully keeping your current QPID java broker users happy. The current plan is for Apollo to eventually become AcitveMQ 6. ActiveMQ 6 could then continue to be the ASF's multi-protocol Java messaging broker. It would repackage Apollo + QPID's Apollo AMQP impl + Apollo's STOMP impl + ActiveMQ's current protocol impl + other bits like an MQTT protocol impl. That means Qpid's AMQP broker impl would also tag along and make it upstream into lots of other projects like ServiceMix and Apache Geronimo. The nice thing all the projects would have a nice common broker base we could collaborate on (the Apollo core). Each project could release broker distos which are focused on 1 protocol, and the ActiveMQ distro could repackage everything into one monstrous distribution where all the protocols are integrated. Naturally if something like this was to occur, the Qpid broker devs would quickly get commit rights to ActiveMQ since they will probably need to stretch and pull Apollo's broker core in new directions. </dream> -- ** *Hiram Chirino* *Software Fellow | FuseSource Corp.* *[email protected] | fusesource.com* *skype: hiramchirino | twitter: @hiramchirino<http://twitter.com/hiramchirino> * *blog: Hiram Chirino's Bit Mojo <http://hiramchirino.com/blog/>* * * * *
