Establishing  an  SOA  Focused  Enterprise  Architecture  

Asanka  Abeysinghe  WSO2,  Inc  

Vice  President,  Solu5ons  Architecture    

Goal  of  the  day  

-  Service  Oriented  Architecture  -  Enterprise  Architecture  -  EA  challenges    -  How  SOA  helps  to  address  EA  challenges    -  Common  business  architecture  pa>ern    -  Lab  exercise  (SoluBon  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  opera5onal  

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)  

-  IntegraBon  is    key  (extend  to  connected  business)  -  Companies  without  integraBon  are  falling  behind  - Heterogeneous  systems  

 

The  finale  

YOU’RE FIRED!

and MEET MY LAWYER!

Building  the  Reference  Architecture    

Integration Patterns

Solu9on  

L0  (Level  0)  –  Architecture    

L1  (Level  1)  –  Architecture    

Example  :  MDM  –  L0  

Example  :  MDM-­‐L1  

Business  Services  Plaaorm  :  Component  Architecture    

BSP  :  Magnitude  View  

BSP  :  Layered  Architecture  

Integration Layer - 1

Datamodel

Integration Layer - 2

Services Platform

Datamodel

Data Layer

Business Services

BSP  –  ImplementaBon  :  IntegraBon  and  Data  

BSP  –  ImplementaBon  :  Services  and  Governance  

BSP  –  ImplementaBon  :  Business  Processes,  Security  

BSP  –  ImplementaBon  :  Monitoring  and  Portals  

Code  vs  ConfiguraBon  

“Professional  coders  make  100-­‐150  errors  per  thousand  

lines  of  code  .”    

ConfiguraBon  Driven  

Recap  

SOA  principles   EA  challenges  

Loosely  coupled  services   Loosely  coupled  development  efforts  (e.g.  accommodate  some  schedule  asynchrony)  

Flexibility  under  changing  business  condiBons  

Flexibility  under  changing  requirements  

Fast  Bme  to  market  of  new  business  capabiliBes  

Short  release  cycle  with  incremental  uBlity  

Heterogeneous  environments   Choose  the  best  tool  for  each  job  

Good  governance  pracBces  and  tools   Community-­‐centric  tools:  •  Versioned  repository  •  Peer  visibility  and  review  •  Rich  communicaBon  channels  •  Issue  and  status  tracking  •  Automated  build/test  

Skip  the  Ad  in  N  seconds  -­‐>|  

Thin  slice  -­‐  Demo  

-  ConfiguraBon  driven    -  Pa>ern  driven    -  Decoupled  architecture    

Thank  You  

@asankama  hQp://asanka.abeysinghe.org  

hQp://wso2.com