data to consumer : end to end middleware capabilities
Post on 13-Apr-2017
419 Views
Preview:
TRANSCRIPT
Data to Consumer end to end middleware capabilities
Asanka AbeysingheVice President, Solutions Architecture WSO2, Inc.
Picture credit : http://flicker .com
Evolution of the platform
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
Platform 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 Pattern Driven Enterprise Architecture.
architecture patterns track | tomorrow | 9AM
Modern applications are System of Systems
(SoS)
System of systems
System 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
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.
Source: Forrester Research
Syst
em o
f Sys
tem
s
mid
dlew
are
func
tiona
l ca
pabi
lities
Prod
uct m
appi
ng
mid
dlew
are
func
tiona
l ca
pabi
lities
Enterprise middleware platform : 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.
Platform of platforms
Why we need a platform
- Demand from the business stakeholders- Rapidly changing business requirements - Quick release cycles
- Continues integration and testing - Rapid technology changes- Provide Middleware-as-a-Service (platform)
Do I need the entire platform ?
- Iterative architecture- Iterative implementation
Picture credit : http://flicker .com
Picture credit : http://flicker .com
Give a code name for the platform. e.g. Digital Platform
Don’t use product/vendor names.
Introduce an onboarding program.Including samples, documents, patterns and
training.
Evangelize the platform (internally).
Build foundation services and expose as APIs.
Increase the developer productivity and reusability.
Seamlessly integrated.
Have a common enterprise architecture practices across the
organization. Include architects from different BUs and
architecture groups.
“It was like Christmas “ Jin Chun, VP-Architecture PWI : Fidelity
top related