Soa 14 service integration with esb
- 1. Service Oriented Architecture: 14 Service Integration with ESB Prof Neeraj Bhargava Vaibhav Khanna Department of Computer Science School of Engineering and Systems Sciences Maharshi Dayanand Saraswati University Ajmer
- 2. Enterprise Service Bus (ESB) âą An Enterprise Service Bus (ESB) is fundamentally an architecture. It is a set of rules and principles for integrating numerous applications together over a bus-like infrastructure. âą The core concept of the ESB Architecture is that you integrate different applications by putting a communication bus between them and then enable each application to talk to the bus. âą This decouples systems from each other, allowing them to communicate without dependency on or knowledge of other systems on the bus.
- 3. ESB Vs Point to point Integration âą The concept of ESB was born out of the need to move away from point-to-point integration, which becomes brittle and hard to manage over time. âą Point-to-point integration results in custom integration code being spread among applications with no central way to monitor or troubleshoot. âą This is often referred to as "spaghetti code" and does not scale because it creates tight dependencies between applications.
- 4. What is ESB âą Enterprise Service Bus (ESB) is a standardized integration platform that combines messaging, web services, data transformation, and intelligent routing, to reliably connect and coordinate the interaction of a significant number of heterogeneous applications with transactional integrity. âą It can also be defined as a software architecture model used for designing and implementing communication between mutually interacting software applications in a Service Oriented Architecture (SOA).
- 6. ESB Implementation âą The ESB architecture has some key principles that allow for business agility and scale. âą The key focus is to decouple systems from each other while allowing them to communicate in a consistent and manageable way. âą The "bus" concept decouples applications from each other. This is usually achieved using a messaging server like JMS or AMQP. âą The data that travels on the bus is a canonical format and is almost always XML. âą There is an "adapter" between the application and the bus that marshals data between the two parties.
- 7. ESB Implementation âą The adapter is responsible for talking to the backend application and transforming data from the application format to the bus format. âą The adapter can also perform a host of other activities such as message routing transaction management, Security, monitoring, error handling, etc. âą ESBs are generally stateless; the state is embedded in the messages passing through the bus. âą The canonical message format is the contract between systems. âą The canonical format means that there is one consistent message format traveling on the bus and that every application on the bus can communicate with each other
- 8. ESB Core functionalities âą Decoupling One of the most important things that can be done via ESB is to decouple clients from service providers. âą Transport Protocol Conversion ESB gives the ability to accept one input protocol and communicate with another service provider on a different protocol. âą Message Enhancement ESB allows to isolate the client and make some basic changes to the message. âą For example, changing date format of incoming message or appending informational data to messages. âą Message Transformation ESB facilitates transformation of an incoming message into several outgoing formats and structure. âą For example, XML to JSON, XML to Java objects.
- 9. ESB Core functionalities âą Routing ESB has the ability to redirect a client request to a particular service provider based on deterministic or variable routing criteria. âą Security ESB protects services from unauthorized access. âą Process Choreography and Service Orchestration ESB manages process flow and complex business services to perform a business operation. âą Process choreography is about business services while service orchestration is the ability to manage the coordination of their actual implementations. It is also capable of abstracting business services from actual implemented services. âą Transaction Management ESB provides the ability to provide a single unit of work for a business request, providing framework for coordination of multiple disparate systems.
- 10. Integration core principles âą 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. âą Transformation: Data transformation between canonical data formats and specific data formats required by each ESB connector. âą Canonical 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.
- 11. Integration core principles âą Transportation: Transport protocol negotiation between multiple formats (such as HTTP, JMS, JDBC). âą Mediation: Providing 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. âą 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.
- 12. Assignment âą Explain the concept of ESB and Key concerns in ESB Implementation âą Explain the ESB Core functionalities, and core principles of ESB Integration âą Thank You