In this slide deck, WSO2 VP of Architecture Asanka Abeysinghe explores how to build an agile enterprise using WSO2's agile methodology and reference architecture.

1. Building an Agile Enterprise
Asanka Abeysinghe
Vice President, Architecture - CTO Office
WSO2, Inc.

2. Centralized & Layered
picture credit: https://www.flickr.com/photos/kaktuslampa/

3. Greenfield < Brownfield
picture credit: https://www.flickr.com/photos/137826074@N08/

5. July-16th, 2018: San Francisco,California
picture credit: https://www.flickr.com/photos/143850343@N06/

6. picture credit: https://www.flickr.com/photos/josephmorris/
Just a (steady) start

7. Reference Architecture

8. Guideline
8

9. A reference architecture in the
field of software architecture or
enterprise architecture
provides a template solution
for an architecture for a
particular domain. It also
provides a common
vocabulary with which to
discuss implementations, often
with the aim to stress
commonality.

10. Why do we need
a new reference
architecture?
Ref.Architecture
Technology
{RI}
Agility
G/B
field

11. picture credit: https://www.flickr.com/photos/tiocfaidh_ar_la_1916/
Architecture Patterns

12. Timeline
12

13. Background: Layered Architecture
13

14. picture credit: https://www.flickr.com/photos/23119666@N03/

15. picture credit: https://www.flickr.com/photos/imcountingufoz/
Rise of Microservices

16. Pragmatic Microservices
Netflix: APIs
Uber: Edge Gateway
eBay: API Facade
Gartner: Mini Services

17. Background: Layered Architecture with MSA
17

20. Background: Segmented Architecture
20

21. Building the
Concept

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

24. A code exposes through an
interface that describes a
collection of operations that
are network accessible using
a standardized messaging
protocol.
Service: Technical definition

25. A microservice must have a
single purpose and be loosely
coupled in design and
deployed independently of
other microservices.
"Micro" is a concept of scope
rather than size.
Microservice

26. Software components that
can be spontaneously
discovered, combined, and
recombined to provide a
solution to a business
problem.
Service: Business definition

27. Microservices is an approach to
application development in
which a large application is built
as a suite of modular
components or services.
These services are built around
business capabilities.
Microservice: Business definition

28. Group of Microservices

29. Cell-based
Reference Architecture

30. A component represents a
process or business logic
running in a container,
serverless environment, or an
existing runtime. A component
is designed based on a specific
scope, which can be
independently run and reused
at the runtime.
Component: Atomic Units

31. A cell is a collection of
components, grouped from
design and implementation
into deployment. A cell is
independently deployable,
manageable, and observable.
Cell: Units of Enterprise Architecture

32. Cell:Components
1:M
1:1

33. Inter and Intra Cell communication
33

34. Connected Cells
Cell gateway (ingress/egress)
Sidecar
Adaptor
Ambassador

35. Gateway Pattern
picture credit: https://www.flickr.com/photos/ell-r-brown/

36. Automated Governance (Re)-enables Flow
Policy
Store
(Registry)
Observability
(Monitoring/
Analytics)
Policy
Enforcement
(GW)
Automated governance is made
of three things:
● A source of truth:
○ Policy store/registry
● Enforcement of the policy
○ Gateway or plugin attempting to
keep the desired state
● Observability
○ How close to the desired state
are we?

37. Security of Cells
picture credit: https://www.flickr.com/photos/laurelfan/ https://www.flickr.com/photos/sahdblunders/
37

38. Security of Cells
38

39. Lifecycle of a Cell

40. 40

41. 41

42. picture credit: https://www.flickr.com/photos/rincon_de_lula/

43. Structured Agility
Versioned Components
Versioned Cells
Dependency managed
Autowired
Reusable
MSA & CNA compliant

44. Cell-based Enterprise
Architecture

45. 45

46. Reference Implementation L0

47. 47

48. Reference Implementation L1

49. 49

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

51. Reference Methodology

52. People Process
Technology

53. Methodology is the
systematic, theoretical
analysis of the methods
applied to a field of study. It
comprises the theoretical
analysis of the body of
methods and principles
associated with a branch of
knowledge.

54. Timeline
54

55. Why do we need
a new reference
methodology?
Agility
Environment
Layers
Gates

56. People, Process, & Technology
56

57. Maturity Model

59. Maturity Model: Pragmatic View
59

60. Iterative Business Transformation
60

61. Moving to the Right ->
Fast Waterfall API-Driven Early Agility
61

62. Integration Agile

63. Integration Agile: People
Agile core
Self-organized teams
Everyone is an agile master

64. Integration Agile: Process
Iterative
Continuous (Agile + DevOps)
Code over config
Integration first

65. Integration Agile: Technology
Pipeline tuned
Multi environment based application lifecycle
Test driven development
Cloud-native
Open source
Cell-based architecture

66. Integration Agile: Digital Alignment
Consumer driven requirements
Start with a MVP
Deliver digital-native applications (personalized, real-time, geo-sensitive, predictable)
Enforce feedback loops

67. Summary: Integration Agile
67

68. picture credit: https://www.flickr.com/photos/vasile23/
From Theory to Practice

69. Transformation is a journey
without a destination. - Marilyn Ferguson
picture credit: https://www.flickr.com/photos/zoomzoom/

70. THANK YOU
wso2.com