This document discusses lightweight orchestration using the WSO2 Enterprise Service Bus (ESB). It provides an overview of WSO2 and its products for service orchestration. It then describes how the ESB can be used to orchestrate blocking and non-blocking backend services, including examples of invoking multiple services to retrieve product price and tax information, or price and description.
2. About WSO2
• Providing the only complete open source componentized cloud
platform
–
–
Dedicated to removing all the stumbling blocks to enterprise agility
Enabling you to focus on business logic and business value
• Recognized by leading analyst firms as visionaries and leaders
–
–
Gartner cites WSO2 as visionaries in all 3 categories of application
infrastructure
Forrester places WSO2 in top 2 for API Management
• Global corporation with offices in USA, UK & Sri Lanka
–
200+ employees and growing
• Business model of selling comprehensive support &
maintenance for our products
5. Service Orchestration in SOA
• Coordinating and accessing multiple fine grained
services from a single coarse-grained service.
• Client only has visible to a single coarse-grained
service.
• Multiple other fine grained services are invoked
from the coarse-grained service which are not
directly visible to the client.
10. WSO2 ESB is…
• A lightweight, high performance ESB
• Feature rich and standards compliant
• SOAP and WS-* standards
• REST support
• Domain specific protocol support (eg: FIX)
• User friendly and highly extensible
• 100% free and open source with commercial support
12. Mediators
Rich mediator library, wherein most cases a single
mediator can be directly mapped to an EIP.
http://docs.wso2.org/wiki/display/ESB470/Mediators
13. WSO2 Developer Studio
How WSO2 Developer Studio can be used for
Service Orchestration
• Message Mediation
Sequences, Proxy Services, Endpoints, Local Entries
Data Transformations
Custom Mediators
• Create deployable artifacts that can be bundled and
deployed to WSO2 ESB.
16. Blocking backend services with the WSO2 ESB
Scenario
• Client invokes a proxy service that would access two backend
services to get the
• Price based on the Product Code
• Tax based on the State and the Price
• Client invocation would contain the Product Code and the State
code.
• Client Receives the Tax applicable for the product.
19. Non blocking backend services
Scenario
• Client invoking a proxy service that would access two backend
services to get the
• Price based on the Product Code
• Product description based on the Product Code
• Client invocation would contain the Product Code
• Client Receives the Product Price and the Product Description.
21. Engage with WSO2
• Helping you get the most out of your deployments
• From project evaluation and inception to development
and going into production, WSO2 is your partner in
ensuring 100% project success