Understanding Enterprise Application Integration
In today's enterprise infrastructure, system and application integration is more and more frequently a mission critical concern. The wide variety of approaches and ideologies aimed at achieving this goal are proof of this fact. When you're just getting started researching application and data integration solutions, it's easy to get lost in a sea of acronyms, opinions, and confusing marketing language.
Rapid advancements in EAI technology to meet the increasing demand for integration in the enterprise often results in arguments about what EAI is or isn't, or how the small differences between one proprietary approach or another make it the only viable solution.
In this article, we'll clear up the confusion, with an easy to understand, clearly organized look at the evolution of EAI. Starting with a brief history of the origins of EAI, we'll walk through all the major developments in EAI architecture, and learn how traditional "hub and spoke" broker-based EAI systems are now being replaced by agile, distributed, standards-based Enterprise Service Bus architectures.
Enterprise architectures, by their nature, tend to consist of many systems and applications, which provide the various services the company relies upon to conduct their day to day business. A single organization might use separate systems, either developed in-house or licensed from a third party vendor, to manage their supply chain, customer relationships, employee information, and business logic. This modularization is often desirable. In theory, breaking the task of running a business into multiple smaller functionalities allows for easy implementation of the best and newest technological advancements in each area, and quick adaptation to changing business needs.