Its been a while but we have finally released 2.3.0.Final.
This includes new features such as replication, multiple backups, multiple failover, failback and stomp 1.2 support as well as many other enhancements, fixes and performance tweaks.
Thanks to all the team, Clebert Suconic, Andy Taylor, Francisco Borges, Howard Gao and Justin Bertram as well as Jeff Mesnil for his integration work and all the other contributors.
Onwards and upwards to 2.4.
HornetQ was already faster, and we have made it even faster.
We have once again improved our performance, and we have made a post here explaining the results obtained with SpecJMS.
Look at the blog entry for information:
HornetQ- the new ultra high performance enterprise grade messaging system from JBoss, sets a record breaking score in the SPECjms2007 industry standard benchmark for JMS messaging system performance.
HornetQ 2.0.GA obtained scores up to 307% higher than previously published SPECjms2007 benchmark results, on the same server hardware and operating system set-up.
The peer-reviewed results are available on the spec.org web-site: www.spec.org/jms2007/results/jms2007.html
The results were obtained by Kai Sachs and Stefan Appel from an independent research group at the TU Darmstadt, Germany.
Their release announcement can be found here:
SPEC® and the benchmark name SPECjms2007® are registered trademarks of the Standard Performance Evaluation Corporation. The results used in the above comparison refer to submissions made on the 17 Sep 2009 and 20 Jan 2010 by TU University Darmstadt
What is HornetQ?
HornetQ is an open source project to build a multi-protocol, embeddable, very high performance, clustered, asynchronous messaging system.
HornetQ is an example of Message Oriented Middleware (MoM) .
Please see the General FAQ wiki page for more information.
Why should I use HornetQ?
Here are a selection of the reasons:
Open Source Software - HornetQ is released under the Apache v 2.0 Licence.
Written in Java - HornetQ runs on any platform with a Java 5 or later runtime.
JMS and above - HornetQ supports the JMS 1.1 API and also defines its own messaging API for maximum performance and flexibility. Other protocols are planned for upcoming releases.
Superb performance - HornetQ class-beating high performance journal provides persistent messaging performance at rates normally seen for non-persistent messaging. Non-persistent messaging performance rocks the boat too.
POJO-based design - HornetQ has been designed using POJO and minimal third-party dependencies. You choose how you want to use HornetQ: run it stand-alone, integrate it with JBoss Application Server or another Java server/container or embed it directly inside your own product.
Solid high availability - HornetQ offers server replication and automatic client failover to eliminate lost or duplicated messages in case of server failure.
Flexible clustering - Create clusters of HornetQ servers that know how to load balance messages. Link geographically distributed clusters over unreliable connections to form a global network. Configure routing of messages in a highly flexible way. Adapt HornetQ to your network topology, not the other way round.
Management - HornetQ provides a comprehensive management API to manage & monitor servers. It is integrated seamlessly to the servers to work in a HA environment.
Documentation & Examples - All HornetQ features are documented and examples are provided. Read the documentation, run the examples and leverage HornetQ features to make your messaging code more robust and performant.
Check out the
HornetQ Messaging Developer's Guide
Want to be a HornetQ committer?
Come and join the sexiest messaging project around.
We need you! We want you!
Just follow these easy steps