Consumer-driven and rapidly changing business requirements are creating the need to go beyond traditional middleware in enterprises today. Because the middleware layer has enough functional capabilities it empowers architects to convert their blueprints to solutions without changing the architecture to fit into the middleware limitations. Asanka will first look at the evolution of middleware and how current and next-generation middleware looks like (Platform-3.0). Following this, he will analyze the middleware requirements from data (system of record) to consumer (system of engagement) by illustrating a layered architecture of modern enterprise middleware.

1. Data to Consumer
end to end middleware capabilities
Asanka Abeysinghe
Vice President, Solutions Architecture
WSO2, Inc.

3. Picture credit : http://flicker .com

4. 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

5. Platform 3.0
Mobile,
social, store
Event driven,
IoT
Bigdata,
analytics DevOps Iterative
Cloud native
Open source API driven
{ }
Polyglot
programming
QoS

6. Compliant with Microservice
architecture (MSA).
We will discuss MSA in detail during
Pattern Driven Enterprise Architecture.
architecture patterns track | tomorrow | 9AM

7. Modern applications are
System of Systems
(SoS)

8. 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

10. 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

11. SystemofSystems
middlewarefunctional
capabilities

12. Productmapping
middlewarefunctional
capabilities

13. Enterprise middleware platform : simplified

14. 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.

15. Platform of platforms

16. 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)

17. Do I need the entire platform ?

18. - Iterative architecture
- Iterative implementation
Picture credit : http://flicker .com

19. Picture credit : http://flicker .com

20. Give a code name for the
platform. e.g. Digital Platform
Don’t use product/vendor names.

21. Introduce an onboarding program.
Including samples, documents, patterns and
training.

22. Evangelize the platform
(internally).

23. Build foundation services and
expose as APIs.
Increase the developer productivity and reusability.

24. Seamlessly integrated.

25. Have a common enterprise
architecture practices across the
organization.
Include architects from different BUs and
architecture groups.

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

28. Thank You!
@asankama
http://asanka.abeysinghe.org
asankaa AT WSO2.com