Successfully reported this slideshow.
Your SlideShare is downloading. ×

Cell-based Architecture : An Emerging Architecture Pattern for Agile Integration

Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad

Check these out next

1 of 67 Ad

Cell-based Architecture : An Emerging Architecture Pattern for Agile Integration

Download to read offline

The number of microservices running in enterprises increases daily. As a result, service composition, governance, security, and observability are becoming a challenge to implement and incorporate. A “cell-based” architecture is an approach that can be applied to current or desired development and technologies to address these issues. This technology-neutral approach helps cloud-native dev teams become more efficient, act in a more self-organized manner, and speed overall release times. In this keynote, Asanka will introduce the "cell-based" reference architecture, which is API-centric, cloud-native and microservices-friendly. He will explain the role of APIs in the cell-based approach, as well as examine how real applications are built as cells. Asanka will explore the metrics and approaches that can be used to measure the effectiveness of the architecture and explore how organizations can implement the cell approach.

The number of microservices running in enterprises increases daily. As a result, service composition, governance, security, and observability are becoming a challenge to implement and incorporate. A “cell-based” architecture is an approach that can be applied to current or desired development and technologies to address these issues. This technology-neutral approach helps cloud-native dev teams become more efficient, act in a more self-organized manner, and speed overall release times. In this keynote, Asanka will introduce the "cell-based" reference architecture, which is API-centric, cloud-native and microservices-friendly. He will explain the role of APIs in the cell-based approach, as well as examine how real applications are built as cells. Asanka will explore the metrics and approaches that can be used to measure the effectiveness of the architecture and explore how organizations can implement the cell approach.

Advertisement
Advertisement

More Related Content

Slideshows for you (19)

Similar to Cell-based Architecture : An Emerging Architecture Pattern for Agile Integration (20)

Advertisement

More from Asanka Abeysinghe (16)

Recently uploaded (20)

Advertisement

Cell-based Architecture : An Emerging Architecture Pattern for Agile Integration

  1. 1. Asanka Abeysinghe Cell-based Architecture An Emerging Architecture Pattern for Agile Integration Vice President, Architecture - CTO Office WSO2 Inc.
  2. 2. Motivation
  3. 3. Centralized & Layered picture credit: https://www.flickr.com/photos/kaktuslampa/
  4. 4. Not enough support for Agility
  5. 5. Brownfield > Greenfield picture credit: https://www.apstra.com/home/landscape-of-meadow-field-with-the-changing-environment-2/ Legacy, monolithic Microservices, sprawl
  6. 6. Reference Implementations picture credit: https://www.marinersmuseum.org/
  7. 7. picture credit: http://unlocked.footlocker.com/ Underutilization of the Technology
  8. 8. Gap: architecture | development | deployment picture credit: https://www.flickr.com/photos/28994379@N02/
  9. 9. picture credit: https://www.solarpowerworldonline.com/2017/07/georgia-contractor-sells-farmers-solar-tough-market/ Dependency management
  10. 10. picture credit: https://www.flickr.com/photos/tiocfaidh_ar_la_1916/ Architecture Patterns
  11. 11. Timeline
  12. 12. Background: Layered Architecture
  13. 13. picture credit: https://www.flickr.com/photos/23119666@N03/ A platform with an agile team 100 APIs, 60 message flows, 80 services, n DBs Multi-tenanted, 3 active tenants First release after 3 years
  14. 14. picture credit: https://www.flickr.com/photos/imcountingufoz/ Rise of Microservices
  15. 15. Pragmatic Microservices Netflix: APIs Uber: Edge Gateway eBay: API Facade Gartner: Mini Services
  16. 16. Background: Layered Architecture with MSA
  17. 17. Background: Segmented Architecture BS-1 BS-2 BS-n G-1 G-2 US-1 US-n
  18. 18. Platform of Platforms Platform (shared capabilities) Project1 Project2 Project3 Projectn Platform (shared capabilities) Project1 Project2 Project3 Projectn Platform (shared capabilities) Project1 Project2 Project3 Projectn Platform (shared capabilities) Project1 Project2 Project3 Projectn CI/CD User Store
  19. 19. picture credit: https://www.flickr.com/photos/ableman/
  20. 20. Making of…… picture credit: https://commons.wikimedia.org/wiki/User:Frank_Schulenburg CC BY 3.0
  21. 21. picture credit: https://sportzwiki.com/football/sir-alex-ferguson-reveals-best-player-managed-man-united/
  22. 22. 2014 2018
  23. 23. Building the Concept
  24. 24. Business vs technical services picture credit: https://www.flickr.com/photos/arpadlukacs/
  25. 25. Service: Technical definition A code exposes through an interface that describes a collection of operations that are network accessible using a standardized messaging protocol.
  26. 26. Microservice: Technical definition 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.
  27. 27. Service: Business definition Software components that can be spontaneously discovered, combined, and recombined to provide a solution to a business problem.
  28. 28. Microservice: Business definition 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.
  29. 29. Group of (Micro)services
  30. 30. The cell is the basic structural, functional, and biological unit of all known living organisms
  31. 31. Cell-based Reference Architecture
  32. 32. Component: Atomic Units 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.
  33. 33. Cell: Units of Enterprise Architecture A cell is a collection of components, grouped from design and implementation into deployment. A cell is independently deployable, manageable, and observable.
  34. 34. Cell:Component 1:M 1:1
  35. 35. Connected Cells picture credit: https://www.medicalnewstoday.com/
  36. 36. Control Plane: - Signaling of the network - Makes decisions about the traffic flow Data Plane: - Forwards traffic between hops - Takes data packets picture credit: https://www.flickr.com/photos/teflon/
  37. 37. Inter and Intra Cell communication
  38. 38. Connected Cells Cell gateway (ingress) Sidecar (egress) Adaptor (egress) Ambassador (egress)
  39. 39. API-centric Architecture
  40. 40. Gateway Pattern picture credit: https://www.flickr.com/photos/ell-r-brown/
  41. 41. 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?
  42. 42. Security of Cells picture credit: https://www.flickr.com/photos/laurelfan/ https://www.flickr.com/photos/sahdblunders/
  43. 43. Security of Cells
  44. 44. Developer Experience (DX) of a Cell
  45. 45. Creating Cells Brand new Cell Existing (micro)services Update an existing Cell Create a new version
  46. 46. Lifecycle of a Cell
  47. 47. picture credit: https://www.flickr.com/photos/rincon_de_lula/
  48. 48. Structured Agility Versioned Components Versioned Cells Dependency managed Autowired Reusable Enhanced MSA & CNA
  49. 49. Cell-based Enterprise Architecture
  50. 50. Reference Implementation L0
  51. 51. Reference Implementation L1
  52. 52. Cells and Podular Organizations
  53. 53. Measure the success picture credit: https://www.marketingdonut.co.uk/direct-marketing/running-a-direct-mail-campaign/getting-the-measure-of-your-marketing
  54. 54. https://www.tasktop.com/blog/5-best-metrics-youve-never-met/ https://dzone.com/articles/reducing-mttr Mean Time to Repair
  55. 55. Self-contained Deployable as a unit Independently elastic Data plane and control plane Summary: Cell-based Reference Architecture
  56. 56. picture credit: https://www.flickr.com/photos/josephmorris/ Just a (steady) start https://github.com/wso2/reference-architecture
  57. 57. picture credit: https://www.flickr.com/photos/vasile23/ From Theory to Practice https://github.com/wso2/reference-methodology
  58. 58. Transformation is a journey without a destination. - Marilyn Ferguson picture credit: https://www.flickr.com/photos/zoomzoom/
  59. 59. WSO2.COM THANK YOU

×