Bit Mojo | My Ramblings on Hawt Tech

Feb/12

3

Apache Apollo 1.0 Released!

4 Comments Other

I’m pleased to announce the availability of Apache Apollo 1.0.  Apollo is a faster, more reliable, easier to maintain messaging broker built from the foundations of the Apache ActiveMQ project but with a radically different threading architecture which lets it scale to large number of concurrent connections and destinations while using a constant number of threads.

Apollo features:

  • Stomp 1.0 Protocol Support
  • Stomp 1.1 Protocol Support
  • Topics and Queues
  • Queue Browsers
  • Durable Subscriptions on Topics
  • Persistent/Reliable Messaging
  • Message Expiration
  • Message Swapping
  • Message Selectors
  • JAAS Authentication
  • ACL based Authorization
  • SSL/TLS Support and Certificate based Authentication
  • REST Management API

Yes, it supports JMS!  Just download Apollo, start it up using the getting started guide and then check out the distribution’s examples directory.  Oh yeah, Apollo has great documentation!

I’ve re-run the STOMP benchmarks I covered in a previous post against the 1.0 release.  The benchmark uses the STOMP protocol to build an apples to apples performance comparison between all the major STOMP servers.  I’ve also built a new JMS benchmark which uses the JMS API build the same kind of performance comparisons.  Both benchmarks are open source and available to be tried out on your choice of hardware.  Or better yet, follow the simple instructions found in each project’s readme to run the benchmarks on EC2:

  • https://github.com/chirino/stomp-benchmark
  • https://github.com/chirino/jms-benchmark

For those of you wondering why the ActiveMQ project create new message broker as a subproject, it’s because we wanted to address the shift in the processor market to multi core for the next major release.  ActiveMQ currently employs complex thread locking which starts to become bottleneck as you increase the core count and you don’t end up fully exploiting the potential on large core count machines.  By developing the solution as a subproject, it’s easier to explore the best options without impacting current main line development of ActiveMQ 5.x.

Now that the Apollo sub project has proven itself, I think it’s time to start integrating it into ActiveMQ.  Ideally, ActiveMQ 6 switches Apollo’s messaging engine and adds/ports all the existing features we’ve come to expect out of ActiveMQ like networks of brokers and priority queues.  But we should really be talking about this on the Apache mailing lists.. join me there!

No tags

spacer

4 Comments for Apache Apollo 1.0 Released!

Apollo 1.0 released | Habari! Blog | February 4, 2012 at 2:19 am

[...] high-speed message broker ActiveMQ Apollo 1.0 has been released. A Delphi client library for Apollo is available from Habarisoft – currently in beta, but a [...]

spacer

Lars-Erik Helander | February 5, 2012 at 5:06 am

Having browsed the Apollo website and studied the benchmarks, I got very interested in exploring more about Apollo.

I had one particular question and I tried to find some place to put it, but I was not able to use the “Community” links provided by the Apollo website.

The question I had was:
Does Apollo provide support for some scenario(s) of broker failover (now or in some near future)?

/Lars

spacer

Pierre Crokaert | February 13, 2012 at 4:10 pm

Have you made improvements on the reliabilty? Because we are migrating a production site to RabbitMQ because of Null content messages received on ActiveMQ, an old bug, but no follow up and no fix? Stability of ActiveMQ is often criticized in message queue comparisons.

spacer

Hiram Chirino | February 13, 2012 at 4:27 pm

Even though 1.0 is Apollo’s initial public release, it previously had 6 open beta releases to where early adopters picked it up and many times used it in anger. Due to it’s simplified thread model it’s proven to be much more robust. Most of the Known Issues in Apollo 1.0 are cosmetic.

« STOMP Messaging Benchmarks: ActiveMQ vs Apollo vs HornetQ vs RabbitMQ

-->
To top
gipoco.com is neither affiliated with the authors of this page nor responsible for its contents. This is a safe-cache copy of the original web site.