Integration core principles

While this is a simple example, it does serve to illustrate some basic fundamentals of any integration initiative. Applying our five core integration principles, namely:

Orchestration Composing new services by chaining multiple services together.
Transformation Data transformation.
Transportation Transport protocol negotiation.
Mediation Supporting multiple interfaces to a single service for backwards compatibility or alternate data formats & transports.
Non-functional consistency Security requirements, monitoring, management, high availability, etc.

An ESB implementation use case typically involves the following:

Orchestration Composing several existing fine grained components into a single higher order composite service. This can be done to achieve appropriate "granularity" of services and promote reuse and manageability of the underlying components. In our loan processing example this includes leveraging existing credit check, interest rate and data warehouse applications to create a new composite service.
Data transformation Transformation between canonical data formats and specific data formats required by each ESB connector. An example of this would be transforming between CSV, Cobol copybook or EDI formats to either SOAP/XML or JSON. Canoncial data formats can greatly simplify the transformation requirements associated with a large ESB implementation where there are many consumers and providers, each with their own data formats and definitions.
Transport protocol negotiation Transport protocol negotiation between multiple formats (such as HTTP, JMS, JDBC). Note: Mule treats databases like another "service" by making JDBC just another transport (or endpoint) where data can be accessed.
Mediation Providing support for multiple interfaces for the purpose of a) supporting multiple versions of a service for backwards compatibility or alternatively, b) to allow for multiple channels to the same underlying component implementation. This second requirement may involve providing multiple interfaces to the same component, one legacy interface (Flat file) and one standards compliant (SOAP/XML) interface.
Non-functional consistency For a typical ESB initiative, this can include consistency around the way security and monitoring policies are applied and implemented. Additionally the goals of scalability and availability can be achieved by using multiple instances of an ESB to provide increased throughput (scalability) and eliminate single-points-of-failure (SPOFs), which is the key objective for highly available systems.
+

Esta página está disponible en español

Ver en español