Digital technologies are becoming increasingly decentralized and disaggregated. To remain competitive, organizations must become more adaptive by decomposing into independent and observable architectural units. This involves decoupling systems using containers, microservices, serverless functions and cloud services. Integration will rely more on open APIs, events and data streams between these distributed units. The future adaptive enterprise will consist of independently managed "cells" that communicate through a centralized integration and governance layer to form integrated products and services. Kubernetes has emerged as the dominant platform for orchestrating containers and microservices across clouds at scale.

1. Digital Technology Landscape
Paul Fremantle
CTO and Co-Founder

3. The action or process of adapting one thing
to fit with another, or suit specified
conditions, esp. a new or changed
environment

5. The only competitive
organisations in the future will
be those that create adaptive
digital experiences

6. How can you become more
adaptive?

7. Decoupling
Physical
Functional
Linux/OS
Virtualization
Cloud
Containers
K8s, Cloud
Orchestration
ABIs Web Services SOA APIs Endpoints

8. Time
LevelofDisaggregation
Increasing Disaggregation / Endpoints
Monolithic
Business App
Enterprise
Apps
Departmental
Apps
10’s
100’s
Increasing Digital Business Agility
Serverless & Microservices
SaaS Apps
Public/Private
API Services
1,000’s
ESB
Multiple
ESBs and codes
integration
Decentralised
Microintegration
100,000’s
10(7)’
s
EAI and FTPCoded Integration
iPaaS
The Breakup of the Enterprise Application

9. Serverless and Microservices
(Google Trends - UK)
9
● Serverless
● Microservices

10. Cloud Economics Is Driving This Push

11. K8s Has Won The Cloud Orchestration War

12. The Intersection of Microservices and
Serverless is Happening in Kubernetes
● Deploy code directly onto Kubernetes
● Let Kubernetes manage the SLA outcomes
● Protect against {Amazon, Azure, Google} lock-in

13. Kubernetes provides Cross-Cloud Decoupling
13

14. Decoupling
Physical
Functional
Linux/OS
Virtualization
Cloud
Containers
K8s, Cloud
Orchestration
ABIs Web Services SOA APIs Endpoints

15. Decoupling
Physical
Functional
Linux/OS
Virtualization
Cloud
Containers
K8s, Cloud
Orchestration
ABIs Web Services SOA APIs Endpoints

16. If everything is an
endpoint, everyone
is an integrator.
16

17. FrequencyOfReleases
Time
Emerging
Velocity Gap
for Integration
Integration Release
Code Release

19. A Shift from CoE to Adaptive Enterprise
19
Centre of Excellence Adaptive Enterprise
Fixed Infrastructure Cloud orchestration
Paper and legacy processes Automated, bottom-up governance
Versioning a monolith Adding or changing individual
microservices and serverless
Scaling the whole Scaling individual components
Complex testing Automated testing
Manual deployment CI/CD
Centralised logs and monitoring Distributed observability
Centralised legacy data Microservices/serverless data stores
with big data streaming

20. An Adaptive Enterprise Needs Both
Centralised and Decentralised Integration
Microservices and Serverless
Cloud Orchestration Platform
Internal APIs, Events and Streams
Centralised Integration
SAP Oracle Legacy

21. Centralised Decentralised
Config over
Code
Traditional ESB Containerised ESB
Code over
Config
Jakarta EE
Node.js
Ballerina Server
Ballerina Microservices,
Spring
Different Flavours of Integration

22. Adaptive Enterprise
An Adaptive Enterprise is made up of
decomposed units
• Functional
• Architectural
• Organizational

23. ● Already we are seeing
proliferation of microservices
○ E.g. 200 microservice with a 10
developer team
○ No clear structure
○ No registry
● However, good observability
○ OpenTracing, Zipkin,
Jaeger
Microservices and Serverless Need
Governance
Registry
Gateway
Observability

24. Microgateway
● A control point for microservices and serverless
architectures
● Provides a well-defined interface to a subset of APIs,
Events and Streams
● A policy enforcement point
● An observability touchpoint
● Governance for Cloud Native

25. An Adaptive Enterprise Needs Architectural
Units of Composition
Internal APIs, Events and Streams
Centralised Integration
SAP Oracle Legacy

26. Units of Composition
26

28. The cell is the basic
structural, functional, and
biological unit of all known
living organisms

29. • A governance and architecture approach
• Independently deployable, manageable, observable
• Within the cell, any-to-any communication
• External parties must communicate via
microgateway
Cells
aka “Units of Enterprise Architecture”

30. • The only competitive enterprises will be adaptive
• Adaptive enterprises must decouple into cells
• Products, processes and services become
integrations of APIs, Events and Streams
• Open source and open cross-cloud create unique
value in this business architecture
Summary

31. Upcoming Sessions
Lean Digital Agility with WSO2
Asanka Abeysinghe, VP, Architecture - CTO Office, WSO2
Empowering Citizens and Their Family Doctors Through
Digital Access of Their Health Data in Malta
Brian Muscat, Solutions Architect, MITA

32. 32

33. THANK YOU