Page History

...

In recent years, there have been several technologies attempting to solve these problems such as Enterprise Applicaton Integration (EAI)⁺ , Business-to-Business (B2B), Service Oriented Architecture (SOA), and Web Services. These solutions addressed some of the integration problems, but were proprietary, expensive, and time-consuming to implement. These solutions range from expensive vendor solutions (high cost, vendor lock-in) to home-grown custom solutions (high maintenance, high cost). The overwhelming disadvantages of these solutions are high cost and low flexibility due to non-standard implementations.

A standards-based ESB solves the integration problem without the drawbacks of the other solutions. The purpose of an ESB is to facilitate application and process integration by providing distributed processing, intelligent routing, ⁵ security, and dynamic data transformation. ⁶ In an ESB these services are infrastructure services so each application does not have to implement these requirements independently and in a proprietary manner.

...

An ESB also supports requirements such as security, [orchestration|Glossary#orchestration}, ⁷ and transactionality.⁸ These exist in "hard-wired" integration methods, but are not available automatically in a service-oriented architecture. One of the key requirements for the ESB is to give loosely coupled, service-based integration methods a level of enterprise-class reliability and security.

...

Please see Home for a complete list of features, services and components, available with ServiceMix.

Definition of Terms

...

For definitions of terms used in this document please see the Glossary.