After being distracted a lot with RESTEasy releases over the past few months, I finally have something usable (and more importantly, documented) for the HornetQ REST Interface I’ve been working on. The interface allows you to leverage the reliability and scalability features of HornetQ over a simple REST/HTTP interface. Messages are produced and consumed by sending and receiving simple HTTP messages containing the XML or JSON (really any media type) document you want to exchange.
Other than being buzzword compliant here are some of the reasons you might want to use the HornetQ REST Interface:
- Usable by any programming language that has an HTTP client library.
- Zero client footprint. We want HornetQ to be usable by any client/programming language that has an adequate HTTP client library. You shouldn’t have to download, install, and configure a special library to interact with HornetQ.
- No envelope (i.e. SOAP) or feed (i.e. Atom) format requirements. You shouldn’t have to learn, use, or parse a specific XML document format in order to send and receive messages through HornetQ’s REST interface.
- Lightweight interoperability. Since interactions are RESTful the HTTP uniform interface provides all the interoperability you need to communicate between different languages, platforms, and even messaging implementations that choose to implement the same RESTful interface as HornetQ (i.e. the REST-* effort.)
- Leverage the reliability, scalability, and clustering features of HornetQ on the back end without sacrificing the simplicity of a REST interface.
HornetQ REST Features
- Duplicate detection when producing messages
- Pull and Push consumers
- Acknowledgement and Auto-acknowledgement protocols
- Create new queues and topics
- Mix and match JMS and REST producers and consumers
- Simple transformations
Visit the HornetQ REST Interface web page to find links for downloading and browsing docs, source code, and examples.