Just Spring Integration written by Madhusudhan Konda provides a concise overview of the Spring Integration framework in 100 pages. The author covers many topics in regards to Spring Integration in only 100 pages and I was able to learn many things and can see the value of the framework. On the other hand, since there was only 100 pages there were a couple of times I felt that topics were covered too lightly and could have been covered in more depth. There were some topics towards the ends of the chapters that seemed to just have a definition and the author didn’t go into enough detail on these topics. I fell that there is a good opportunity to provide more detailed examples of all the sections that are covered in the book and some of the corner cases that you need to think about when using an messaging framework.
If you are looking for a introduction to Spring Integration and no nothing about it, like myself, then this is a good book to get but not at the full price. If you have the opportunity to get the book at 50% off, which they do if it is the book of the day, then it would be worth the money. Otherwise, I think there are other books out there that provide more in depth coverage of the Spring Integration framework that is not covered in this book.
Some of the corner cases that I mentioned about above you will need to think about when creating a production application. For example, if you are persisting the messages to a data store in cases where the system might crash it never talks about if those messages are purged if they don’t get processed. In addition, when you have multiple messages that need to be all processed to complete the group of tasks the system will store the messages until all of them are collected, if you select that option. What happens if one of the messages never comes around, do those messages stay around in the data store? The author does explain all the options that you have for process the collection of messages, but never talks about these corner cases. Another corner case is dealing with the ability to use a file locks so that other processes cannot read the same file, but what happens to the file lock if the system crashes? This use case is never covered and is very important to think about, otherwise you could have a case where files are getting locked by the framework and never get processed.
Therefore, if you are looking for a quick introduction to Spring Integration with the understanding that you will need to research some of these use case when creating a production system, then this book will help you out. Again, I knew nothing about Spring Integration before I read this book and after reading it I have a good understanding of what it provides and can see how it would benefit current and future applications. I just feel that I will need to research on my own to learn even more about the topic and feel that for the price of the book I should not have to be doing that right out of the gate. Therefore, if you are looking for a book that provides in depth coverage of all the topics within Spring Integration, then this is not the book for you.