Lightweight orchestration with WSO2Enterprise Service Bus

Nadeesha Gamage

© WSO2 2013. Not for redistribution. Commercial in Confidence.

About WSO2

•  Providing the only complete open source componentized cloudplatform

– – 

Dedicated to removing all the stumbling blocks to enterprise agilityEnabling 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

infrastructureForrester 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

150+ globally positioned support customers

WSO2 Product Map

Service Orchestration in SOA

•  Coordinating and accessing multiple fine grainedservices 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.

• 

• 

Service orchestration in SOA

Service orchestration in SOA for

•  Blocking backend services – Service dependencyexist. Response of one service is required for the next service.

Service orchestration in SOA for

•  Non Blocking backend services – Services are notdepended on each other and can be invoked simultaneously.

Service orchestration in SOA with the WSO2 ESB

WSO2 Enterprise Service Bus

• • 

A lightweight, high performance ESBFeature rich and standards compliant• • • 

SOAP and WS-* standardsREST supportDomain specific protocol support (eg: FIX)

• • 

User friendly and highly extensible100% free and open source with commercial

support

WSO2 ESB - Some Functional Components

• • • • • • • • • • 

MediatorsSequences Endpoints Proxy Services Event SourcesPriority Executors Message Stores TasksLocal EntriesRegistry

Mediators

Rich mediator library, wherein most cases a singlemediator can be directly mapped to an EIP.

http://docs.wso2.org/wiki/display/ESB470/Mediators

WSO2 Developer Studio

How WSO2 Developer Studio can beService Orchestration

used for

•  Message MediationSequences, Proxy Services,

Data Transformations

Custom Mediators

Endpoints, Local Entries

•  Create deployable artifacts that can be bundled anddeployed to WSO2 ESB.

WSO2 Carbon artifact deployment

Blocking backend services with the WSO2 ESB

Blocking backend services with the WSO2 ESB

Scenario

•  Client invokes a proxy service that would access two backendservices to get the• • 

Price based on the Product CodeTax based on the State and the Price

•  Clientcode. Client

invocation would contain the Product Code and the State

•  Receives the Tax applicable for the product.

Blocking backend services with the WSO2 ESB

Non blocking backend services

Non blocking backend services

Scenario

•  Client invoking a proxy service that wouldservices to get the

access two backend

• • 

Price based on the Product CodeProduct description based on the Product Code

• • 

Client invocation would contain the Product CodeClient Receives the Product Price and the Product Description.

Non blocking backend services

Engage with WSO2

• • 

Helping you get the most out of your deploymentsFrom project evaluation and inception to development and going into production, WSO2 is your partner in ensuring 100% project success