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
capabili0es
Asanka
Abeysinghe
Vice
President,
Solu8ons
Architecture
WSO2,
Inc.

2. Committer.
Architect and a technology evangelist.

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

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

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

7. Compliant
with
Microservice
architecture
(MSA).
We
will
discuss
MSA
in
detail
during
Pa9ern
Driven
Enterprise
Architecture.
architecture
pa?erns
track
|
tomorrow
|
9AM

8. Modern
applica9ons
are
System
of
Systems
(SoS)

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

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

12. System
of
Systems
middleware
func8onal
capabili8es

13. Product
mapping
middleware
func8onal
capabili8es

14. Enterprise
middleware
plaGorm
:
simplified

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

16. Pla/orm
of
pla/orms

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

18. Do
I
need
the
en9re
pla/orm
?

19. -­‐
Itera8ve
architecture
-­‐
Itera8ve
implementa8on
Picture
credit
:
h?p://flicker
.com

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

21. Give
a
code
name
for
the
pla/orm.
e.g.
Digital
Pla/orm
Don’t
use
product/vendor
names.

22. Introduce
an
onboarding
program.
Including
samples,
documents,
paNerns
and
training.

23. Evangelize
the
pla/orm
(internally).

24. Build
founda9on
services
and
expose
as
APIs.
Increase
the
developer
produc9vity
and
reusability.

25. Seamlessly
integrated.

26. Have
a
common
enterprise
architecture
prac9ces
across
the
organiza9on.
Include
architects
from
different
BUs
and
architecture
groups.

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

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