HornetQ: Difference between revisions
mNo edit summary |
Updated Infobox with release 2.4.0 |
||
| Line 8: | Line 8: | ||
| developer = [[JBoss_(company)|JBoss]] |
| developer = [[JBoss_(company)|JBoss]] |
||
| status = Active |
| status = Active |
||
| latest release version = 2. |
| latest release version = 2.4.0 |
||
| latest release date = {{release date|2013| |
| latest release date = {{release date|2013|12|16}} |
||
| operating system = [[Cross-platform]] |
| operating system = [[Cross-platform]] |
||
| programming language = [[Java (programming language)|Java]] |
| programming language = [[Java (programming language)|Java]] |
||
Revision as of 14:38, 13 February 2014
 | This article needs additional citations for verification. (June 2012) |
| Developer(s) | JBoss |
|---|---|
| Stable release | 2.4.0
/ December 16, 2013 |
| Written in | Java |
| Operating system | Cross-platform |
| Type | asynchronous messaging |
| License | Apache License 2.0 |
| Website | http://hornetq.org |
HornetQ is an open source asynchronous messaging project from JBoss. It is an example of Message Oriented Middleware. HornetQ is an open source project to build a multi-protocol, embeddable, very high performance, clustered, asynchronous messaging system. During much of its development, the HornetQ code base was developed under the name JBoss Messaging 2.0.
The HornetQ project was started with Tim Fox as the project lead, and was launched on 24 August 2009. Fox led the project until 8 October 2010, when he stepped down as project lead to pursue other projects. It is currently led by Clebert Suconic with core engineers Andy Taylor, Francisco Borges, Howard Gao and Jeff Mesnil.
The HornetQ project is licensed using the Apache Software License v 2.0. As of 4-2-2010 HornetQ is the SPECjms2007[1] record breaker.[2]
It has the following relevant features:
- Supports STOMP protocol for cross language clients
- 100% JMS compliant
- 8.2 Million Messages per second with SpecJMS
- AIO (over Linux)/NIO (over any OS) based high performance journal.
- Clustering for scalability and reliability
- Supports Master/Slave architecture for fault tolerance
- Supports discovery groups for dynamic node clusters
- Core Bridges to connect to other HornetQ servers (over unreliable WAN links)
- JMS Bridges to connect to other JMS compatible servers
- Diverts to reroute traffic without modifying application code
- Paging to support messages which size exceeds the available RAM
- Large message support to enable file messaging
- XA and JTA transaction support
- Application Server integration using the JCA standard (allows MDBs too)
- High performance Netty NIO connector over TCP, SSL and Servlet modes (for messaging between firewalls)
- JMX based management
- Last Value Queues
- Filters and wildcard support
- Security features integrated with JAAS
- Simple XML configuration
References
- ^
SPECjms2007 "Frequently Asked Questions". Retrieved 2012-06-22.
SPECjms2007 is an industry-standard benchmark designed to measure the performance and scalability of JMS-based Message-Oriented Middleware (MOM) platforms.
{{cite web}}: Check|url=value (help) - ^ Spring+JBoss, So Happy Together! from Red Hat