SOA Architecture Patterns
Asanka Abeysinghe,
Architect, WSO2, Inc.
asankaa@wso2.com

Introduction
This session provides an in-depth on how to implement a SOA
solution using basic elements of such an infrastructure.
We will demonstrate mapping several enterprise SOA patterns,
to a few real world and a few hypothetical business requirements.
SOA implementation details will be discussed using products from
the WSO2 SOA platform.

Agenda

Introduction
 Patterns

SOA Infrastructure

Solution building roadmap

Use-Case 1

Use-Case 2
 Use-Case 3

Enhancements

Summary

Q&A

Patterns
A generic solution for a common recurring problem.

Used it before
 Error proof
 Catalog to pick one
 Feel comfortable

SOA Patterns
SA Patterns
OO Patterns
EAA Patterns
EAI Patterns Other
OO - Object-Oriented
SA – Software Architecture
EAI – Ent. Application Integration
EAA – Ent. Application Architecture

SOA Infrastructure

Solution Building Roadmap
Requirements Business Patterns Integration Patterns
Application Patterns
Runtime Patterns
Product Mappings

USE-Case-1 (Business Scenario)
A system has connected a service client and a service in P2P.
System is running on production.
Backend Service development team decided to bring bunch of
changes to the backend service(s).

Secure the backend service.

Change the service contract.

Bring multiple services instead of the single service.
Change
Again ?
Service Client/Frontend developers
PMs, Financial dept, HR Dept

USE-Case-1 (Pattern Mapping)

Service Broker Pattern with ESB
 Pipes and Filters
 Transform
 Route

Trusted Subsystems

Functional Decomposition
 Service Encapsulation

USE-Case-1 (Implementation)
Pipes and filters
Route
Trusted subsystems

USE-Case-1 (Implementation) cont..
Pipes and filters Mediation
Route DBLookup
Transform

USE-Case-1 (Implementation) cont..
Pipes and filters
Route

USE-Case-1 (Implementation) cont..
Pipes and filters
Route
Functional decomposition
Service encapsulation

USE-Case-2 (Business Scenario)
A service that hosted in a local network required to accept
requests from outside and need to validate the content outside
LAN before accepting.
Validations , virus scan and validate the content
Expose the service to
outside
NO you can't

USE-Case-2 (Pattern Mapping)

Service Firewall Pattern
 Protocol Bridging

USE-Case-2 (Implementation)
Service Firewall
Protocol bridging

USE-Case-3 (Business Scenario)
SOA infrastructure going to implement in an environment that
contains legacy systems and legacy databases that running for
a long time. Existing systems are error proof and the data is
valuable to make decisions.
Throw the old systems
away.....
Data ?
NO SOA $$$$

USE-Case-3 (Pattern Mapping)
 MDM (Master Data Management) Pattern

EDA (Event Driven Architecture)

USE-Case-3 (Implementation)
MDM

USE-Case-3 (Implementation) cont..
MDM

USE-Case-3 (Implementation) cont..
MDM
EDA

Enhancements

Shared repository/ registry
 Clustering

HA / LB

Governance

Monitoring

Management
 Create your own patterns for your needs

Summary

Identify the business requirements.
 Map them to patterns.

Avoid P2P.

Think about the ROI.

Keep all stakeholders happy.

Optimize the usage of the application.
 Apply SOA correctly, use it in a practical
manner.

Q&A