Download - Digital Technology Landscape
The action or process of adapting one thing to fit with another, or suit specified conditions, esp. a new or changed environment
The only competitive organisations in the future will be those that create adaptive
digital experiences
Decoupling Ph
ysic
al
Functional
Linux/OS
Virtualization
Cloud
Containers
K8s, Cloud Orchestration
ABIs Web Services SOA APIs Endpoints
Time
Leve
l of
Dis
aggr
egat
ion
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 FTP Coded Integration iPaaS
The Breakup of the Enterprise Application
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
Decoupling Ph
ysic
al
Functional
Linux/OS
Virtualization
Cloud
Containers
K8s, Cloud Orchestration
ABIs Web Services SOA APIs Endpoints
Decoupling Ph
ysic
al
Functional
Linux/OS
Virtualization
Cloud
Containers
K8s, Cloud Orchestration
ABIs Web Services SOA APIs Endpoints
Freq
uenc
y O
f Rel
ease
s
Time
Emerging Velocity Gap
for Integration
Integration Release
Code Release
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
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
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
Adaptive Enterprise
An Adaptive Enterprise is made up of decomposed units • Functional • Architectural • Organizational
● 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
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
An Adaptive Enterprise Needs Architectural Units of Composition
Internal APIs, Events and Streams
Centralised Integration
SAP Oracle Legacy
• 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”
• 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
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