This document discusses pragmatic approaches to microservices and cell-based architecture. It begins by introducing WSO2 as the leading open source integration vendor and discusses how API-driven initiatives can drive integration. It then discusses key concepts of microservices including single responsibility, bounded contexts, independent development and deployment of self-contained services. The document also discusses service contracts, interaction models, data management, and governance for microservices. It introduces the concept of a cell-based architecture and defines a cell as an immutable and independently deployable application component. It describes a cell runtime for Kubernetes that includes components like an API gateway and cell control plane to deploy and manage cells.

1. Pragmatic Approach to Microservices
and Cell-based Architecture
Architecting for Innovation
7th February 2019, Sydney.
David Hymers, Regional Account Lead, ANZ, david@wso2.com
Dassana Wijesekara, Director Solutions Architecture, ANZ, dassana@wso2.com
www.wso2.com

2. #1
6th
50%
The Leading Open Source Integration Vendor
++++
Open Source Integration Vendor
Largest Open Source Vendor
ARR Growth
Cash Flow
2

3. Start with API
management
IDENTITY & ACCESS
MANAGEMENT
Secure and federated identity
for integration
● Identity management
● Identity federation
● Authentication
● Authorization
60M identities managed
ANALYTICS &
STREAM PROCESSING
Streaming data for
real-time analysis
100K+ TPS
● Streaming engine (Siddhi)
● Dashboards
● Business rules
ENTERPRISE
INTEGRATION
Quick, iterative integration of
any app, data, or system
6 trillion transactions / yr
● ESB
● BPM
● Message broker
● Data integration
● Integration designer
Further develop APIs with integration that connects
apps and data.
API
MANAGEMENT
API design, creation, reuse,
governance, and analytics
20K APIs for 200K orgs
● API analytics
● API designer
● API gateway
● API publisher
● API storefront/marketplace
● API repository/registry
API-Driven Initiatives Drive Integration

4. WSO2 Momentum
Accelerating growth with efficient return on capital
WSO2 DASHBOARD($000s)
Exiting Subscription ARR
ARR Growth
Subscription Customers
2015 2016 2017
$ 11,252
39%
$ 16,387
46%
$ 24,447
49%
451 438 471
201 251 324
Exiting Headcount
2018
$ 37,000
51%
571
406

5. WSO2 Is Now International First!
is now international with customers in
63 countries
53% of our business

6. 6
“... the only fully open source solution in
our Wave analysis, WSO2 provides good
breadth across all evaluation criteria.”
Leader in the Forrester
Wave: API Management
Solutions, Q4 2018

7. WSO2 Sydney Summit 7th March, 2019
https://wso2.com/summit/sydney-2019
7

8. WSO2 ANZ MeetUp Groups
WSO2 Sydney MeetUp Group WSO2 Melbourne
MeetUp Group
WSO2 Wellington MeetUp Group WSO2 Auckland MeetUp Group
8

9. Pragmatic
Microservices
Architecture
9

10. Single responsibility (SRP)
Bounded context - DDD*
Agile/independant development
Self-contained deployables
Independently elastic
Pragmatic “Micro” Concept
*DDD- Domain Driven Design : Martin Fowler

11. Simpler definition (YAML/JSON)
Supports querying the definition*
Swagger / RAML (+OpenAPI)
IDL** - non HTTP
The Service Contract
*GraphQL **IDL- Interface Definition Language

12. Simple message structure
Lightweight stateless interaction
Sync/Async {REST,AMQP,MQTT}
JSON/Apache Thrift/Avro
The Interaction Model

13. Sync. Integration Models
Point to point interaction
Gateway pattern
Lightweight message pipe

14. Async. Integration Models
One way request
Publisher - subscriber
AMQP/MQTT

15. Async. Integration Models
One way request
Publisher - subscriber
AMQP/MQTT

16. Decentralized Data Management
Own private database
No direct access to other DBs
SQL / NoSQL combination

17. Governance Model
No centralized governance model
Independant design governance
Run-time governance - API Gateway

18. Service Registry
Client-side discovery Server side discovery

19. Data Plane
Pod1
Proxy
Service
Pod2
Proxy
Service
ControlPlane
Addresses the challenges dev & ops face when moving to MSA
Service Mesh

20. Deployment

21. Cell-based
Architecture
21

22. Self-contained
Deployable as a unit
Independently elastic
Data plane and control plane
Cell-based Reference Architecture

23. What is a Cell?
A cell is an immutable application component that can be built, deployed and
managed as a complete unit.
The cell consists of multiple services, managed APIs, ingress and egress policies
(including routing, throttling, access control), security trust domain, deployment
policies, rolling update policies and external dependencies. The cell definition
captures all of these in a standard technology-neutral fashion.

24. Cell Runtime for Kubernetes
API Gateway
Global Data
Plane
Observability
APIManagerIdentityServer
Global Control
Plane
Cell Gateway
Cell Gateway
PO
D
PO
D
Cell
Cell control
plane Egress
pod
Kubernetes
Service
Proxy

25. 25
Discussion

26. OPEN TECHNOLOGY FOR YOUR AGILE DIGITAL BUSINESS
THANK YOU