System of SystemsBuilding a Connected Business

Asanka AbeysingheVice President, Solutions Architecture

WSO2,Inc

Challenges : Objectives

empty seats

getting ready to go home

Picture Credit : Flicker

electrifying atmosphere

getting ready to party

past experience

information overloaded

Picture Credit : Flicker

Next-generation middleware

“Platform 1.0 … 3.0“John Mathon, VP-Enterprise Evangelism

Platform 1.0 - Mainframe and before : centralized computing

Platform 2.0 - Messaging, object orientation, SOA, EDA : distributed computing and internet

Platform 3.0 - Platform 2.0 + next-generation middleware : the cloud

Features of Platform 3.0• Cloud native• Open Source • API driven• Mobile, social , App, *store is critical• Polyglot programming model • Event driven, analytics, big data is fundamental• DevOps/ALM built-in

– Continuous testing, integration, deployment

• QoS - scalability, reliability, security• Connect everything to anything (IoT)

System of SystemsSystem of systems is a collection of task-oriented or dedicated systems that pool their resources and capabilities together to create a new, more complex system which offers more functionality and performance than simply the sum of the constituent systems.

- Wikipedia

Componentized architecture

Gartner view of System of Systems

Forrester view of System of Systems

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

Systems of engagement are technologies that directly support customer interactions through software.

Systems of automation 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 platform

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

Do I need the entire platform ?

What will happen to the current system(s), data, people ?

How can I get there ?

Journey

Technical Non-technical

Picture Credit : Flicker

Business architecture

RequirementsCurrent

applications/systems

Δ Delta

Architecture approach

Business Architecture

Solution Architecture

• Level 0• Level 1

Application Architecture

• Integration • Datamodels• APIs

Runtime Architecture

• Capacity Planning• Deployment • Security

Level 0 to level 1

What enterprises look like

Identity/Access control

Services

Registry, repository, governance

Internal connectivity

External connectivity

Connector store https://storepreview.wso2.com/store/

APIs internal/external

Monitoring, analytics, audits

Filling the blanks

Non-technical

http://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

Production line to frontline

Picture Credit : The Connected Company – Dave Gray

Edge leadership

Picture Credit : The Connected Company – Dave Gray

Platform

Picture Credit : The Connected Company – Dave Gray

Enterprise middleware and cloud platform from system of record to

system of engagement

( data to consumer )

Thank You

asankaa AT wso2.com@asankamahttp://asanka.abeysinghe.org