What audience is this book targeted at ?
ie . beginners ,people that have some experience with other integration frameworks ,etc...
I'm asking because, so far, most of my integration work has been via web services rather than direct interaction with different applications .
I'm trying to think about what sort of use cases would benefit from Spring integration.
Joined: Nov 01, 2012
Two questions here:
1. What audience
2. When to use SI
Any technical person that is considering to use Spring Integration would benefit from the book. Also if you're using it already there are some pointers in there that might save you some time, or open your eyes to something. We've really tried to make it worth the read, so I hope you enjoy it.
This is a more tricky question. I would say that if you're processing a fair bit of information and you're doing several different things with it functionally you should consider using Spring Integration for its runtime decoupling of services. This will help if you want to distribute the application over multiple functionally distinct nodes later. If you have a straightforward web-app or a straight forward batch job or a straight forward map-reduce job you might want to look at something else. If it's a little bit of two or more of those, Spring Integration might help you.
Another reason to use Spring Integration might be if you want your application to react to events (other than http requests). Coding that yourself is error prone and the abstractions that Spring Integration has for that are rather nice (in my biased opinion).