Today we are going to start a new tutorial series on Enterprise Service Bus from the very basics. People like me who learned ESB from web application development background when first time engage into solving integration problem which requires ESB could not visualize the problem domain and deployment infrastructure. In normal web application development though it follows multi tier architecture, however it is always about one application or one flow or one bundle (i.e one archive file ear or war). So even though its multi threaded its only one application archive file which needs to be deployed. We only have one web application context.
However when we involve in developing solution in integration or SOA domain we often deal multiple domain bundle or archive file. And each of there bundle or flow has their own context. The major difference between normal web application bundle and ESB bundle are as follows:
1. ESB bundle are generally B2B
2. ESB bundles or services are generally stateless (though we have separate domain like BPM which facilitates stateful bundle or flow or service) where as web application bundle are stateful in nature).
The above diagram is just novice view of ESB in comparison with an web application container. However an enterprise service bus is much more and complex.
We will continue this series and elaborate ESB in next article.