System of Systems Building a Connected Business
Asanka Abeysinghe Vice President, Solu<ons Architecture
WSO2,Inc
Challenges : Objec/ves
empty seats
geBng ready to go home
Picture Credit : Flicker
electrifying atmosphere
geBng ready to party
past experience
informa<on overloaded
Picture Credit : Flicker
Next-‐genera/on middleware
“Pla>orm 1.0 … 3.0“ John Mathon, VP-‐Enterprise Evangelism
Pla>orm 1.0 -‐ Mainframe and before : centralized compu/ng Pla>orm 2.0 -‐ Messaging, object orienta<on, SOA, EDA : distributed compu/ng and internet Pla>orm 3.0 -‐ PlaKorm 2.0 + next-‐genera<on middleware : the cloud
Features of PlaKorm 3.0 • Cloud na<ve • Open Source • API driven • Mobile, social , App, *store is cri<cal • Polyglot programming model • Event driven, analy<cs, big data is fundamental • DevOps/ALM built-‐in
– Con<nuous tes<ng, integra<on, deployment
• QoS -‐ scalability, reliability, security • Connect everything to anything (IoT)
System of Systems System of systems is a collec.on of task-‐oriented or dedicated systems that pool their resources and capabili.es together to create a new, more complex system which offers more func.onality and performance than simply the sum of the cons.tuent systems.
-‐ Wikipedia
Componen<zed architecture
Gartner view of System of Systems
Forrester view of System of Systems
Systems of record are technologies that manage and store transac<ons, content, and processes.
Systems of engagement are technologies that directly support customer interac<ons through so[ware.
Systems of automa1on are technologies that intelligently manage physical products, networks, and infrastructure.
WSO2 view of System of Systems
WSO2 View of System of Systems
WSO2 View of System of Systems
WSO2 View of System of Systems
WSO2 View of System of Systems
WSO2 View of System of Systems
WSO2 View of System of Systems
WSO2 View of System of Systems
Enterprise middleware plaKorm
“It was like Christmas “ Jin Chun, VP-‐Architecture PWI : Fidelity
Do I need the en/re pla>orm ?
What will happen to the current system(s), data, people ?
How can I get there ?
Journey
Technical Non-‐technical
Picture Credit : Flicker
Business architecture
Requirements Current
applica/ons/systems
Δ Delta
Architecture approach
Business Architecture
Solu/on Architecture
• Level 0 • Level 1
Applica/on Architecture
• Integra/on • Datamodels • APIs
Run/me Architecture
• Capacity Planning • Deployment • Security
Level 0 to level 1
What enterprises look like
Iden<ty/Access control
Services
Registry, repository, governance
Internal connec<vity
External connec<vity
Connector store h`ps://storepreview.wso2.com/store/
APIs internal/external
Monitoring, analy<cs, audits
Filling the blanks
Non-‐technical
h`p://us14.wso2con.com/videos/
Podular
Picture Credit : The Connected Company – Dave Gray
Podular
Picture Credit : The Connected Company – Dave Gray
Open systems
Picture Credit : The Connected Company – Dave Gray
Produc<on line to frontline
Picture Credit : The Connected Company – Dave Gray
Edge leadership
Picture Credit : The Connected Company – Dave Gray
PlaKorm
Picture Credit : The Connected Company – Dave Gray
Enterprise middleware and cloud pla>orm from system of record to
system of engagement
( data to consumer )
Thank You
asankaa AT wso2.com @asankama h`p://asanka.abeysinghe.org