Learn more Shop now Learn more Shop now Shop now Shop now Shop now Shop now Learn More Shop now Learn more Click Here Shop now Learn More Shop now Shop Women's Shop Men's

Customer reviews

2.5 out of 5 stars
2.5 out of 5 stars
HornetQ Messaging Developer's Guide
Format: Paperback|Change
Price:£27.99+ Free shipping with Amazon Prime

on 12 March 2013
When i read the table of contents, I thought it might be a good book. but to give an idea on of how bad it is, it does not even go to describe acceptors and connectors, not even in the config chapter. The text and example in chapter 7 ( diverts and filters) is just ridiculously simple, its of no use. Chapter on using hornetq with JBoss AS just repeats the contents in the earlier chapters, does not indicate how to configure the server outside of jboss and still get JBoss AS to work with hornetq. The text has no flow to it and the author keeps repeating instructions on how to download and install eclipse! Lots of typos. What I would recommend is to just read through the online documentation of hornetq, which is very thorough.
0Comment| One person found this helpful. Was this review helpful to you?YesNoReport abuse
on 3 December 2012
For readers who were programming since the 90s in java, this book evokes familiar ideas. HornetQ implements the Java Messaging Service [JMS], which was released to great publicity by Sun Microsystems in 1999. JMS was generalised to Messaging Oriented Middleware [MOM] and HornetQ can also be considered if somewhat liberally as implementation of that. Asynchrony is a key basic idea for why HornetQ exists, and this is quickly apparent from the book's early discussion. The use cases would involve the need for a message framework that can accept many incoming messages and store them in a temporary holding area and then forward these to one or more consumers, where the latter might be databases or end user applications.

The book also positions itself as a user friendly alternative to the official HornetQ documentation. I am sure the latter is comprehensive about all the HornetQ features, but it is likely turgid reading.

One nifty aspect of the book is how it chooses to save [=commit] its messages into not a relational database like MySql but MongoDB. The latter uses the NoSql approach. If you are trained in relational databases, it may be worthwhile professionally to try this book out as a use case for learning MongoDB or more generally NoSql. The programming steps are slightly different. However, you can learn what is a quite different approach to storing and accessing data, that is generating some buzz right now on the tech street.

While I have just said that the book is useful for trying out MongoDB, it is deficient in not explaining why this was done. Perhaps the advantages are obvious to the author. Probably not to a reader likely to be trained in RDBS. The text could have been improved by going more into these benefits to educate a possibly wary reader. I mean, What the heck is this NoSql stuff?? An excellent pedagogic lesson was passed up here.

It is this, rather than the fine grained details about how to use HornetQ, where these details take up most of the book, that to me is the salient top level aspect.
0Comment|Was this review helpful to you?YesNoReport abuse

Need customer service? Click here