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 USA 2018] Deep-dive into Agile Architecture and Methodology


Published on

In this slide deck, Asanka will deep-dive into WSO2's brand new reference architecture and reference methodology for agility.

Watch video:

Published in: Technology
  • Be the first to comment

  • Be the first to like this

[WSO2Con USA 2018] Deep-dive into Agile Architecture and Methodology

  1. 1. Vice President, Architecture - CTO Office WSO2, Inc Deep-dive into Agile Architecture and Methodology Asanka Abeysinghe
  2. 2. Clay Hammond (Dennis Quaid) The Words
  3. 3. Recap
  4. 4. picture credit:
  5. 5. Reference Architecture
  6. 6. Guideline
  7. 7. 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.
  8. 8. Background: Layered Architecture
  9. 9. Background: Layered Architecture with MSA
  10. 10. Background: Segmented Architecture
  11. 11. Why do we need a new reference architecture? Architecture Technology {RI} Agility
  12. 12. Cell-based Reference Architecture
  13. 13. 2011 2018
  14. 14. CTO-Office: Reference Architecture
  15. 15. Building the Concept
  16. 16. 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
  17. 17. 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
  18. 18. Connected Cells Cell gateway (ingress/egress) Sidecar Adaptor Ambassador
  19. 19. Cell-based Architecture
  20. 20. Reference Implementation - L0
  21. 21. Inter and Intra Cell communication
  22. 22. Security and Governance of Cells
  23. 23. Lifecycle and Versioning of Cells
  24. 24. Reference Implementation - L1
  25. 25. Self-contained Deployable as a unit Independently elastic Data plane and control plane Summary : Cell-based Reference Architecture
  26. 26. Reference Methodology
  27. 27. People Process Technology
  28. 28. 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.
  29. 29. Timeline
  30. 30. Why do we need a new reference methodology? Agility Environment Layers Gates
  31. 31. People, Process, & Technology
  32. 32. Maturity Model
  33. 33. Maturity Model: Pragmatic View
  34. 34. Iterative Business Transformation
  35. 35. Moving to the Right -> Fast Waterfall API-Driven Early Agility
  36. 36. Integration Agile
  37. 37. Integration Agile: People Agile core Self-organized teams Everyone is an agile master
  38. 38. Integration Agile: Process Iterative Continuous (Agile + DevOps) Code over config Integration first
  39. 39. Integration Agile: Technology Pipeline tuned Multi environment based application lifecycle Test driven development Cloud-native Cell-based architecture Open source
  40. 40. Integration Agile: Digital Alignment Consumer driven requirements Start with a MVP Deliver digital-native applications (personalized, real-time, geo-sensitive, predictable) Enforce feedback loops
  41. 41. How to get engaged and apply the reference architecture and methodology for agility Contact me Download the papers
  42. 42. Transformation is a journey without a destination. - Marilyn Ferguson picture credit:
  43. 43. THANK YOU