Establishing an SOA Focused Enterprise Architecture Asanka Abeysinghe WSO2, Inc Vice President, Solutions Architecture

Goal of the day -Service Oriented Architecture -Enterprise Architecture -EA challenges -How SOA helps to address EA challenges -Common business architecture pattern -Lab exercise (Solution building) -Q&A

Service Oriented Architecture “Architecture paradigm to build highly loosely coupled distributed systems”

Service Oriented Architecture cont. “Nothing NEW, architecture style to fix the broken architectures”

Pre-services Era

SOA at Kindergarten

SOA cont.

SOA today – Design Time

SOA today – Run Time

API-centric SOA “ API Management, the missing link for SOA success. ” - Sanjiva Weerawarana

API-centric SOA cont.

API Façade

Enterprise Architecture “ Manage the complexity of the IT environment and applies principles and techniques to reduce the complexity, improve efficiencies, and reduce capital and operational expenditure.”

EA Challenges -Enterprise Architecture has changed -Less visibility to projects -Difficult to find -Availability -Ownership -Development cycles: -From 18 to 6 months to 3 months -Change management -Real standards -Technical (REST, SOAP, protobuf) -Business (ACORD, HL7, FIX, FAST) -Integration is key (extend to connected business) -Companies without integration are falling behind -Heterogeneous systems

The finale YOU’RE FIRED! and MEET MY LAWYER!

Building the Reference Architecture Integration Patterns Solution

L0 (Level 0) – Architecture

L1 (Level 1) – Architecture

Example : MDM – L0

Example : MDM-L1

Business Services Platform : Component Architecture

BSP : Magnitude View

BSP : Layered Architecture Integration Layer - 1 Datamodel Integration Layer - 2 Services Platform Datamodel Data Layer Business Services

BSP – Implementation : Integration and Data

BSP – Implementation : Services and Governance

BSP – Implementation : Business Processes, Security

BSP – Implementation : Monitoring and Portals

Code vs Configuration “ Professional coders make errors per thousand lines of code.”

Configuration Driven

Recap SOA principlesEA challenges Loosely coupled servicesLoosely coupled development efforts (e.g. accommodate some schedule asynchrony) Flexibility under changing business conditions Flexibility under changing requirements Fast time to market of new business capabilities Short release cycle with incremental utility Heterogeneous environmentsChoose the best tool for each job Good governance practices and toolsCommunity-centric tools: Versioned repository Peer visibility and review Rich communication channels Issue and status tracking Automated build/test

Skip the Ad in N seconds ->|

Thin slice - Demo -Configuration driven -Pattern driven -Decoupled architecture

Thank