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.
6. Compliant with Microservice
architecture (MSA).
We will discuss MSA in detail during
Pattern Driven Enterprise Architecture.
architecture patterns track | tomorrow | 9AM
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
9.
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
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.
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)