In this slide deck, Asanka looks at the interaction between enterprise agility and integration agility. He explores the architecture and methodology required for enterprise agility and outline a roadmap to increase agility at the enterprise level. Learn more: https://wso2.com/library/conference/2018/08/wso2con-asia-2018-how-to-build-an-agile-enterprise/

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

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

3. “Agility”

4. Original
Remake
picture credit: https://www.flickr.com/photos/florencia123/

5. Agile is here
- just not very
evenly distributed

6. App Logic
. . .
Scaling HA Resilience Observability
Scaling HA Resilience Observability
HA Resilience Observability
Compute Network Storage
Ops Infrastructure
Centralized
Dev Org
Middleware
& Integration
CoE Teams
Ops
Team
HA Resilience ObservabilityScaling
INTEGRATION
HA Resilience ObservabilityScaling
MESSAGING
HA Resilience ObservabilityScaling
DATA
HA Resilience ObservabilityScaling
SECURITY
App LogicApp Logic
App 1 App 2 App (n)
Fast Waterfall
Wagile
Water-Scrum-Fall
Agilefall

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

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

9. 2014
2018

10. CTO Office: Reference Architecture

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

13. Reference Architecture

14. Guideline

15. 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.

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

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

18. Timeline

19. Background: Layered Architecture

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

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

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

23. Background: Layered Architecture with MSA

26. Background: Segmented Architecture

27. Building the
Concept

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

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. Connected Cells
Cell gateway (ingress/egress)
Sidecar
Adaptor
Ambassador

34. Cell-based Architecture

35. Reference Implementation - L0

36. Inter and Intra Cell communication

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

38. 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?

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

40. Security of Cells

41. Lifecycle and Versioning of Cells

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

43. Reference Implementation - L1

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

45. Reference Methodology

46. People Process
Technology

47. 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.

48. Timeline

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

50. People, Process, & Technology

51. Maturity Model

53. Maturity Model: Pragmatic View

54. Iterative Business Transformation

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

56. Integration Agile

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

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

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

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

61. Summary: Integration Agile

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

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

64. THANK YOU
wso2.com