Data  to  Consumer    end  to  end  middleware  capabili0es  

Asanka  Abeysinghe  Vice  President,  Solu8ons  Architecture    WSO2,  Inc.  

Committer. Architect and a technology evangelist.

Picture  credit  :  h?p://flicker  .com  

Evolu8on  of  the  plaGorm  

Pla/orm  1.0  -­‐  Mainframe  and  before    :  centralized  compu9ng    Pla/orm  2.0  -­‐  Messaging,  object  orienta8on,  SOA,  EDA  :  distributed  compu9ng  and  internet     Pla/orm  3.0  -­‐    PlaGorm  2.0  +  next-­‐genera8on  middleware  :  the  cloud      

   

PlaGorm  3.0  

Mobile, social, store Event driven,

IoT Bigdata, analytics DevOps Iterative

Cloud native Open source API driven

{  }  Polyglot

programming QoS

Compliant  with  Microservice  architecture  (MSA).  

   We  will  discuss  MSA  in  detail  during    

Pa9ern  Driven  Enterprise  Architecture.    architecture  pa?erns  track  |  tomorrow  |  9AM    

 

Modern  applica9ons  are    System  of  Systems  

(SoS)  

System  of  systems  

System   of   systems   is   a   collec0on   of   task-­‐oriented   or   dedicated   systems   that   pool   their  resources   and   capabili0es   together   to   create   a  new,   more   complex   system   which   offers   more  func0onality   and   performance   than   simply   the  sum  of  the  cons0tuent  systems.    

-­‐  Wikipedia  

Systems  of  record  are  technologies  that  manage  and  store  transac8ons,  content,  and  processes.    

Systems  of  engagement  are  technologies  that  directly  support  customer  interac8ons  through  soVware.  

Systems  of  automa1on  are  technologies  that  intelligently  manage  physical  products,  networks,  and  infrastructure.    

Source:  Forrester  Research  

System

 of  Systems  

middlew

are  func8o

nal  

capabili8

es    

Prod

uct  m

apping  

middlew

are  func8o

nal  

capabili8

es    

Enterprise  middleware  plaGorm  :  simplified    

Platforms are systems that support a community. A platform is an investment, often a long-term investment that will only pay for itself over a long period of time. A platform supports a network — a shared resource — and in order to thrive, it must attract and retain members. - Gray, Dave; The Connected Company.

Pla/orm  of  pla/orms  

Why  we  need  a  plaGorm  

-  Demand  from  the  business  stakeholders  -  Rapidly  changing  business  requirements    -  Quick  release  cycles  

-  Con8nues  integra8on  and  tes8ng      -  Rapid  technology  changes  -  Provide  Middleware-­‐as-­‐a-­‐Service  (plaGorm)    

Do  I  need  the  en9re  pla/orm  ?  

-­‐  Itera8ve  architecture  -­‐  Itera8ve  implementa8on      

Picture  credit  :  h?p://flicker  .com  

Picture  credit  :  h?p://flicker  .com  

Give  a  code  name  for  the  pla/orm.  e.g.  Digital  Pla/orm  

Don’t  use  product/vendor  names.    

Introduce  an  onboarding  program.  

Including  samples,  documents,  paNerns  and  

training.      

Evangelize  the  pla/orm  (internally).  

Build  founda9on  services  and  expose  as  APIs.    

Increase  the  developer  produc9vity  and  reusability.  

Seamlessly  integrated.    

Have  a  common  enterprise  architecture  prac9ces  across  the  

organiza9on.    Include  architects  from  different  BUs  and  

architecture  groups.    

“It  was  like  Christmas  “                                  Jin  Chun,  VP-­‐Architecture  PWI  :  Fidelity      

Thank  You!  @asankama  h?p://asanka.abeysinghe.org  asankaa  AT  WSO2.com