Book Image

HornetQ Messaging Developer's Guide

By : Piero Giacomelli
Book Image

HornetQ Messaging Developer's Guide

By: Piero Giacomelli

Overview of this book

<p>Messages and information can be exchanged at exponential speed with JBoss HornetQ asynchronous messaging middleware. Learn how to use the JAVA open source Message Oriented Framework, to build a high-performance, multi-protocol, embeddable, clustered system and manage millions of messages per second.<br /><br />In the HornetQ Messaging Developer’s Guide you will find the most common applications of a message exchanger with example code, as part of real-world scenarios. This practical and applicable guide increases reader knowledge chapter by chapter, covering basics to the most advanced features.<br /><br />You will start from a clean installation of a HornetQ sever and, having progressively become a HornetQ master, will finish by being able to use the framework embedded in your software and sharing information in a cluster environment.<br /><br />Starting from writing and reading a single message, we will discover more advanced features like managing queues, clustering the server, and controlling the undelivered messages. The book deals with a real-world advanced medical scenario as the main example that will lead you from learning the basics to the advanced features of HornetQ.</p>
Table of Contents (18 chapters)
HornetQ Messaging Developer's Guide
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

First cluster with two different nodes


Our first example is one of the simplest, yet one of the most needed ones when we need to create a cluster. Till now we have seen a single queue deployed on a single node. So we basically interacted with only one instance of HornetQ, both from the consumer, rather than from the consumer and producer layer.

In this case we change our scenario. We create two nodes for running different HornetQ server instances. Then we will use JMS to interact both at a producer level and at a consumer level to demonstrate that the cluster will share information between the two nodes.

JMS topics are part of the JMS specification and are basically a distribution mechanism for publishing messages that are delivered to multiple subscribers. From our point of view, you could think of a topic as a distributed queue where we can produce consumer messages.

From the code point of view, this will not affect anything except for the fact that we will use a topic instead of a queue...