I've read a reply you made in another post: spring integration vs ESB and you say:
Thus, you can use Spring Integration easily as a library within (existing) applications. This means Spring Integration is also very suitable for intra-application integration and not just for business-to-business (B2B) or application-to-application integration (EAI).
Is it thus the intention to make integration patterns more accessible from within applications?
Does the book discuss the trade offs involved in using integration patterns in this manner, e.g. overheads involved in any transformations?
And what are your thoughts on the use of spring integration vs spring dependency injection vs OSGi in making applications more modular?
I mean, with Spring we have a great way to decouple components of an application. With OSGi we have a way to formalise this decoupling at a physical level. So why do we need to complicate matters further by using integration patterns within the application?
I'm just trying to understand the bigger picture