This slide deck discusses conventional centralized integration, the role of integration in microservices, microservice integration patterns, and hybrid architecture with centralized vs. decentralized integration for brownfield enterprises Learn more: https://wso2.com/library/conference/2018/08/wso2con-asia-2018-adaptive-and-iterative-integration-for-microservices-and-cloud-native-architectures/

1. Associate Director - Solutions Architecture,
WSO2
Adaptive and Iterative Integration for
Microservices and Cloud Native
Architectures
Chanaka Fernando

2. ● Integration and digital transformation
● Role of integration in cloud native architectures
● Microservice integration patterns
● Realizing cloud native and microservices architecture
with WSO2 Integration Platform
Overview

3. Digital
Transformation and
Integration
● Integration is possibly the
most important aspect of
digital transformation
● Not a one-off thing
● Iterative and adaptive

4. What is
Cloud Native?
Methodology of building
and running applications
that fully exploits the power
of cloud computing

5. Cloud Native
Applications
● Cloud native apps are
composed of microservices
or serverless functions
● Packaged in containers
● Runs on a Continuous
Delivery model
● Adaptive governance

6. Rise of Cloud Native
Applications

7. Scaling for masses
(Scale cube)

8. Why
Microservice
Architecture
(MSA)?
● Do your work at best
● Run/Modify/Scale
independently
● Innovate fast

9. Integrating
Microservices and
Cloud Native Apps
Integration is essential to build
any real world use case with
cloud native apps

10. Virtual
Service 1
● Centralized ESB layer provides the integration and network
communication and governance capabilities
ESB as the Central Integration Bus
Service A
Virtual
Service 2
Virtual
Service 3
Service B Service C Service D
ESB
Consumers

11. ● Microservices code has to take care of all network
communication and governance of services
Smart Endpoints and Dumb Pipes
Microservice
X
Microservice
P
Microservice
Y
Microservice
z
Microservice
Q
Microservice
R
Microservice
S
Java
Consumers
Node.js Go

12. Source : https://medium.com/netflix-techblog/
Engineering-trade-offs-and-the-netflix-api-re-
architecture-64f122b277dd
Integrating Microservices - Anti-Patterns
● API gateway with business
logic
○ E.g. Previous architecture of
Netflix API Gateway
● Integrate microservice with a
central ESB

13. How to Integrate
Microservices

14. Active Composition/Orchestration Pattern
Synchronous/request-response communication
Consumer 1
API Service P API Service Q API Service R API Service S
Consumers
Consumer 2 Consumer 3
μ Service A
Proprietary
& Legacy
Systems
Web API /
SaaS
API Services/
Edge Services
Composite Service/
Integration Services
Core Services/
Atomic Services μ Service I
μ Service H
μ Service J
μ Service E
μ Service C
μ Service D
μ Service G
μ Service B
μ Service F

15. Reactive Composition/Choreography Pattern
μ Service A μ Service B μ Service C
Event Bus
Asynchronous event-driven communication
Produce Consume
Produce Consume
Produce Consume
Produce Consume
Application

16. Active
or
Reactive?
● Active Composition
○ Ideal for interactive services
○ Services are NOT autonomous
● Reactive Composition
○ Ideal for asynchronous
interactions
○ Composition logic is opaque

17. Hybrid of Active and Reactive Composition
Consumer 1
API Service P API Service Q API Service R API Service S
Consumers
Consumer 2 Consumer 3
μ Service A
Event Bus
Proprietary
& Legacy
Systems
Web API /
SaaS
API Services/
Edge Services
Composite Service/
Integration Services
Core Services/
Atomic Services μ Service I
μ Service H
μ Service J
μ Service E
μ Service C
μ Service D
μ Service G
μ Service B

18. No ‘Green Field’
Enterprises!

19. Isolate the legacy and modern systems by placing an
anti-corruption layer between them
Anti-Corruption Layer Pattern
Data
Store
Data
Store
Data
Store
Data
Store
Microservice
Data
Store
Subsystem B
Anti-
Corruption
LayerMicroservice
Microservice
Subsystem A

20. ● Incrementally replace specific pieces of functionality with new
applications and services
● Create a façade that intercepts requests going to the backend
legacy system
Strangler Pattern
Legacy
Modern
Strangler Façade
Early Migration
Modern
Legacy
Strangler Façade
Later Migration
Modern
Migration Complete

21. Building Microservices Integration with WSO2
Consumer 1
API Service P API Service Q API Service R API Service S
Consumers
Consumer 2 Consumer 3
μ Service A
μ Service B
μ Service F
Event Bus
Proprietary
& Legacy
Systems
Web API /
SaaS
API Services/
Edge Services
Composite Service/
Integration Services
Core Services/
Atomic Services
μ Service I
μ Service H
μ Service J
μ Service E
μ Service C
μ Service D
MicroESB

22. Service Mesh
● Microservices code has to take care of all network
communication and governance of services
● Hence such capabilities can be offloaded to a separate layer
Microservice A
Network Stack
Service Mesh
Sidecar
Microservice B
Network Stack
Service Mesh
Sidecar
Control Plane
HTTP1.x.HTTP2.gRPC,TCP
Application Network
Functions
Business
Logic
Primitive
Network
Functions Data Plane

23. Service Mesh - Guidelines
● Service Mesh is only meant for commodity features
○ Interservice communication resiliency
○ Governance of services: observability, security, throttling
● Never implement business logic at the service mesh layer!
● Data plane more or less supports synchronous
communication

24. Cell-based architecture

25. Conclusion
● Cloud native shift is inevitable
● Adaptive and iterative approach is required
● Use a hybrid set of microservices integration patterns

26. Questions?

27. THANK YOU
wso2.com