WSO2 SOA Solution Patterns

25
Santa Clara SOA Solution Patterns Afkham Azeez, Architect & Product Manager WSO2 WSAS, WSO2, Inc. [email protected]

description

 

Transcript of WSO2 SOA Solution Patterns

Page 1: WSO2 SOA Solution Patterns

Santa Clara

SOA Solution PatternsAfkham Azeez,

Architect & Product Manager WSO2 WSAS, WSO2, [email protected]

Page 2: WSO2 SOA Solution Patterns

Santa Clara

We will...see how to implement an SOA solution using basic elements of an SOA infrastructure.

...demonstrate how to map enterprise SOA patterns, to a few real world and a few hypothetical business requirements.

...discuss SOA implementation details using products from the WSO2 SOA Platform.

Page 3: WSO2 SOA Solution Patterns

Santa Clara

Overview

Patterns SOA Infrastructure Solution building roadmap 3 usecases

Scenario, pattern mapping & implementation Enhancements

Page 4: WSO2 SOA Solution Patterns

Santa Clara

What is a pattern?

A generic reusable solution for a common recurring problem.

Tried & tested Robust (stood the test of time) Maintained in a catalog Feel comfortable using

Page 5: WSO2 SOA Solution Patterns

Santa Clara

SOA Solution Patterns

OO Patterns

EAI Patterns

EAA Patterns

SA Patterns

Other

OO - Object-OrientedSA – Software ArchitectureEAI – Enterprise Application IntegrationEAA – Enterprise Application Architecture

Page 6: WSO2 SOA Solution Patterns

Santa ClaraSOA Infrastructure – The Building Blocks

Page 7: WSO2 SOA Solution Patterns

Santa Clara

Solution Building Roadmap

Requirements Business Patterns Integration Patterns

Application Patterns

Runtime Patterns

Product Mappings

Page 8: WSO2 SOA Solution Patterns

Santa Clara

Usecase-1 (Business Scenario)

Client/frontend developersPMs, Finance, HR etc.

Change Again ?

● Service client and service connected in P2P fashion in a production System.

● Backend service development team has decided to change the backend services.

● Secure the backend services.● Change the service contracts.● Introduce multiple services in place of a single service.

Page 9: WSO2 SOA Solution Patterns

Santa Clara

Usecase-1 (Pattern Mapping)

Service Broker Pattern Pipes and Filters

Transform Route

Trusted Subsystems Functional Decomposition Service Encapsulation

Page 10: WSO2 SOA Solution Patterns

Santa Clara

Usecase-1 (Implementation)

Pipes and filtersRoute Trusted subsystems

Page 11: WSO2 SOA Solution Patterns

Santa Clara

Usecase-1 (Implementation) cont..

MediationDBLookup

Pipes and filtersRoute Transform

Page 12: WSO2 SOA Solution Patterns

Santa Clara

Usecase-1 (Implementation) cont..

Pipes and filtersRoute

Page 13: WSO2 SOA Solution Patterns

Santa Clara

Usecase-1 (Implementation) cont..

Pipes and filtersRoute Functional decompositionService encapsulation

Page 14: WSO2 SOA Solution Patterns

Santa Clara

Usecase-2 (Business Scenario)

Expose the service to the outside world?

NO you can't!

● A service that hosted in a local network required to accept requests from outside need to

● Need to virus scan & validate the content outside LAN before accepting.

● Incoming protocol may be different from the protocols allowed within the LAN

Page 15: WSO2 SOA Solution Patterns

Santa Clara

Usecase-2 (Pattern Mapping)

Service Firewall Protocol Bridge

Page 16: WSO2 SOA Solution Patterns

Santa Clara

Usecase-2 (Implementation)

Service FirewallProtocol Bridge

Page 17: WSO2 SOA Solution Patterns

Santa Clara

Usecase-3 (Business Scenario)

Throw away the old systems

$$ ? NO SOA!

Data ?

● SOA infrastructure to be implemented in an environment containing legacy systems and legacy databases.

● Existing systems are robust and the data is crucial for decision making.

Page 18: WSO2 SOA Solution Patterns

Santa Clara

Usecase-3 (Pattern Mapping)

MDM (Master Data Management) EDA (Event Driven Architecture)

Page 19: WSO2 SOA Solution Patterns

Santa Clara

Usecase-3 (Implementation)

MDM

Page 20: WSO2 SOA Solution Patterns

Santa Clara

Usecase-3 (Implementation) cont..

MDM

Page 21: WSO2 SOA Solution Patterns

Santa Clara

Usecase-3 (Implementation) cont..

MDMEDA

Page 22: WSO2 SOA Solution Patterns

Santa Clara

Enhancements

Governance ● Shared registry/repository operational/runtime governance

● Monitoring ● Management

Clustering ● Availability● Load

Create your own patterns for your needs

Page 23: WSO2 SOA Solution Patterns

Santa Clara

Summary - Patterns

Service broker Pipes & filters Route Trusted subsystems Transformation Functional decomposition Service encapsulation Service firewall Protocol bridge Master Data Management Event Driven Architecture

Page 24: WSO2 SOA Solution Patterns

Santa Clara

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.

Page 25: WSO2 SOA Solution Patterns

Santa Clara

QuestionsQuestions