Spoilt for Choice: How to Choose the Right Enterprise Service Bus (ESB)?
I had a very interesting talk at OOP 2013 in Germany. OOP is a great conference for software architects and decision makers. The topic of my talk was “Spoilt for Choice: How to Choose the Right Enterprise Service Bus (ESB)”. Hereby, I want to share the slides with you…
Data exchanges in and between companies increase a lot. The number of applications which must be integrated increases, too. As solution, an Enterprise Service Bus (ESB) can be used in almost every integration project – no matter which technologies, transport protocols, data formats, or environments such as Java or .NET are used. All integration projects can be realized in a consistent way without redundant boilerplate code. However, an ESB offers many further features, such as business process management (BPM), master data management, business activity monitoring, or big data. Plenty of ESB products are on the market which differ a lot regarding concepts, programming models, tooling, and open source vs. proprietary. Really one is spoilt for choice.
This session shows and compares ESB alternatives and discusses their pros and cons. Besides, a recommendation will be given when to use just a lightweight framework for a specific problem such as systems integration or BPM instead of a (too) powerful ESB. You will also learn what an integration suite is, how it differs from an ESB, and when to use which alternative.
Here are the slides of my session:
Feel free to tell me your opinions in the comments. I appreciate every feedback!
Kai Wähner (Twitter: @KaiWaehner)
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)