Hornetq - Enterprise messaging

  •        2386

HornetQ is the new ultra high performance enterprise grade messaging system from JBoss community. It is a multi-protocol, embeddable, very high performance, clustered, asynchronous messaging system. It offers server replication and automatic client failover to eliminate lost or duplicated messages in case of server failure. It also provides a comprehensive management API to manage & monitor servers.

HornetQ supports STOMP (simple text oriented messaging protocol), JMS bridge, Client side load balancing, Duplicate message detection, Message expiration, Scheduled messages and lot more.




Related Projects


Apache ActiveMQ is the most popular and powerful open source messaging and Integration Patterns provider. Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4.

RocketMQ - Distributed messaging and streaming data platform

Apache RocketMQ is a distributed messaging and streaming platform with low latency, high performance and reliability, trillion-level capacity and flexible scalability.

Apache Apollo - ActiveMQ's next generation of messaging

ActiveMQ Apollo is a faster, more reliable, easier to maintain messaging broker built from the foundations of the original ActiveMQ. It accomplishes this using a radically different threading and message dispatching architecture. Like ActiveMQ, Apollo is a multi-protocol broker and supports STOMP, AMQP, MQTT, Openwire, SSL, and WebSockets.

RabbitMQ - Robust messaging for applications

RabbitMQ is a messaging broker - an intermediary for messaging. It gives your applications a common platform to send and receive messages, and your messages a safe place to live until received. It features include reliability, high availability, Clustering and Federation. RabbitMQ ships with an easy-to use management UI that allows you to monitor and control every aspect of your message broker. There are RabbitMQ clients for almost any language you can think of.

ZeroMQ - Messaging Library

The 0MQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products. 0MQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more.

Apache Qpid - AMQP Enterprise Messaging Implementation.

Apache Qpid implements the latest AMQP specification, the first open standard for enterprise messaging, and provides transaction management, queuing, distribution, security, management, clustering, federation and heterogeneous multi-platform support and a lot more.

vespa-crabro - simple message queue layer on top of HornetQ

simple message queue layer on top of HornetQ

hornetq-stomp - HornetQ Server with Stomp Connect

HornetQ Server with Stomp Connect

SAFMQ: Store and Forward Message Queue

SAFMQ: Store and Forward Message Queue, message oriented middleware. Uses include Assured Async Messaging, SOA, Delayed/Batch, and Cluster/Grid Computing. The SAFMQ server provides cross platform communication among C++, PHP, Java, and .NET clients.

hornetq-jms-python - Sample HornetQ JMS Python Integration

Sample HornetQ JMS Python Integration

NSQ - A realtime distributed messaging platform in Go

NSQ is a realtime distributed messaging platform designed to operate at scale, handling billions of messages per day. It promotes distributed and decentralized topologies without single points of failure, enabling fault tolerance and high availability coupled with a reliable message delivery guarantee. It scales horizontally, without any centralized brokers. Built-in discovery simplifies the addition of nodes to the cluster.

OpenMAMA - Open Middleware Agnostic Messaging API

OpenMAMA Project provides a vendor neutral integration layer for a variety of message oriented middleware systems and messaging protocols. It enables an application to employ a range or middleware systems simultaneously or switch between them at will while developing with a single open source API. Adding or changing the messaging stack does not require lengthy and expensive code changes.

hornetq-poc - Repository created to store proofs of concept about JMS and HornetQ.

Repository created to store proofs of concept about JMS and HornetQ.

couchdb-lager - Mirror of Apache CouchDB

for the backend:```erlang{lager, [ {handlers, [ {lager_console_backend, [info, {lager_default_formatter, [time," [",severity,"] ", message, "\n"]}]}, {lager_file_backend, [{file, "error.log"}, {level, error}, {formatter, lager_default_formatter}, {formatter_config, [date, " ", time," [",severity,"] ",pid, " ", message, "\n"]}]}, {lager_file_backend, [{file, "console.log"}, {level, info}]} ]}]}.```Included is lager_default_formatter. This provides a generic, default formatting fo


Embedded JBoss HornetQ broker with STOMP over Websockets connector

Pulsar - Distributed pub-sub Messaging System from Yahoo

Pulsar is a distributed pub-sub messaging platform with a very flexible messaging model and an intuitive client API. It is horizontally scalable (Millions of independent topics and millions of messages published per second), Strong ordering and consistency guarantees, Low latency , REST API, Geo Replication and lot more.

Celery - Distributed Task Queue

Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well. The execution units, called tasks, are executed concurrently on a single or more worker servers using multiprocessing, Eventlet, or gevent. Tasks can execute asynchronously (in the background) or synchronously (wait until ready).

message-api - Use simple, technology neutral method calls for messaging (JMS, ESB, etc.)

Use simple, technology neutral method calls for messaging (JMS, ESB, etc.)

HornetQ_Spring - Simple HornetQ/JMS Spring integration example

Simple HornetQ/JMS Spring integration example


Spring Integration JMS message-driven-channel-adapter has a good MBean support through DefaultMessageListenerContainer where we can control the flow of messages to the subscribers. In this project I will demonstrate some of these capabilities.