This book begins by describing the basic installation process, then mentions some ActiveMQ usage patterns and ends by considering other useful issues for proofs of concept and unit testing with ActiveMQ. The author has taken great care in drafting and each chapter describes the topic shows the code and explains something additional concerning the topic.
My recommendation to the author is:
- Consider using GitHub to post the source code for the examples, the code version control are very useful for referencing code and to receive feedback from readers.
- Give use cases for the patterns, throughout the book are mentioned different patterns and at least should be mentioned a use case for each.
The latter is something I would like to extend, for example mentions a request/response pattern, and, I personally have never heard of this with a message broker, here is a simple example of how to develop it but the best way to explain this would be a use case. It is clearly understood that doing this is not scalable in a single process to wait for the answer “in one thread”, but, what concerns should lead someone to do this?, In fact, always think this (in my opinion) we helps to make everything asynchronously and is what message brokers are made.
I must admit that the author also considered to mention two ActiveMQ aspects that stand out compared to the features of other brokers, I mean Failover transport and Virtual destinations, these are two issues that never would have expected to be included in a book, and however I must congratulate the author for having an excellent idea.
In short, the book is good enough to be an “Instant” edition, just little things to improve.
The author has kindly uploaded the code examples to GitHub: