Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

[WSO2Con Asia 2018] How to Build an Agile Enterprise


Published on

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:

Published in: Technology
  • Be the first to comment

  • Be the first to like this

[WSO2Con Asia 2018] How to Build an Agile Enterprise

  1. 1. Vice President, Architecture - CTO Office WSO2, Inc How to Build an Agile Enterprise Asanka Abeysinghe
  2. 2. July-16th, 2018: San Francisco,California picture credit:
  3. 3. “Agility”
  4. 4. Original Remake picture credit:
  5. 5. Agile is here - just not very evenly distributed
  6. 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. 7. Centralized & Layered picture credit:
  8. 8. Greenfield < Brownfield picture credit:
  9. 9. 2014 2018
  10. 10. CTO Office: Reference Architecture
  11. 11. picture credit: Just a (steady) start
  12. 12. Reference Architecture
  13. 13. Guideline
  14. 14. 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.
  15. 15. Why do we need a new reference architecture? Ref.Architecture Technology {RI} Agility G/B field
  16. 16. picture credit: Architecture Patterns
  17. 17. Timeline
  18. 18. Background: Layered Architecture
  19. 19. picture credit:
  20. 20. picture credit: Rise of Microservices
  21. 21. Pragmatic Microservices Netflix: APIs Uber: Edge Gateway eBay: API Facade Gartner: Mini Services
  22. 22. Background: Layered Architecture with MSA
  23. 23. Background: Segmented Architecture
  24. 24. Building the Concept
  25. 25. The cell is the basic structural, functional, and biological unit of all known living organisms
  26. 26. Cell-based Reference Architecture
  27. 27. 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
  28. 28. 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
  29. 29. Cell:Components 1:M 1:1
  30. 30. Connected Cells Cell gateway (ingress/egress) Sidecar Adaptor Ambassador
  31. 31. Cell-based Architecture
  32. 32. Reference Implementation - L0
  33. 33. Inter and Intra Cell communication
  34. 34. Gateway Pattern picture credit:
  35. 35. 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?
  36. 36. Security of Cells picture credit:
  37. 37. Security of Cells
  38. 38. Lifecycle and Versioning of Cells
  39. 39. picture credit:
  40. 40. Reference Implementation - L1
  41. 41. Self-contained Deployable as a unit Independently elastic Data plane and control plane Summary: Cell-based Reference Architecture
  42. 42. Reference Methodology
  43. 43. People Process Technology
  44. 44. 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.
  45. 45. Timeline
  46. 46. Why do we need a new reference methodology? Agility Environment Layers Gates
  47. 47. People, Process, & Technology
  48. 48. Maturity Model
  49. 49. Maturity Model: Pragmatic View
  50. 50. Iterative Business Transformation
  51. 51. Moving to the Right -> Fast Waterfall API-Driven Early Agility
  52. 52. Integration Agile
  53. 53. Integration Agile: People Agile core Self-organized teams Everyone is an agile master
  54. 54. Integration Agile: Process Iterative Continuous (Agile + DevOps) Code over config Integration first
  55. 55. Integration Agile: Technology Pipeline tuned Multi environment based application lifecycle Test driven development Cloud-native Open source Cell-based architecture
  56. 56. Integration Agile: Digital Alignment Consumer driven requirements Start with a MVP Deliver digital-native applications (personalized, real-time, geo-sensitive, predictable) Enforce feedback loops
  57. 57. Summary: Integration Agile
  58. 58. picture credit: From Theory to Practice
  59. 59. Transformation is a journey without a destination. - Marilyn Ferguson picture credit:
  60. 60. THANK YOU