In Chapter 1, we introduced ESB and also looked into what JBI has got to offer here. If you are familiar with SOA principles, one subtle fact, which is evident now is that ESB or JBI are not an end by themselves, but a means towards an end (which is SOA). An ESB is not required to build an SOA, nor is JBI required for ESB or SOA. However, all of them have something in common using JBI—we can build standard components to be deployed into ESB architectures. Thus, JBI by itself is one of the ways by which we can attain SOA. There is also a caveat to this—just following JBI or ESB will not guarantee that you attain SOA. Increasingly, you will hear requests from your project stakeholders to implement an ESB without considering SOA as a whole, such that they want immediate solutions. It is technically feasible to build ESB, which act as pipes interconnecting systems, but the success of such ESB architectures without considering the SOA landscape, which it...