APIs: The Glue of Microservices - Introduction to the Cell-based Architecture
•
0 likes•595 views
In this slide deck, WSO2 VP of Architecture Asanka Abeysinghe discusses a new cell-based architecture which involves grouping components from design, implementation and deployment into cells. These cells are independently deployable, manageable, and observable.
Report
Share
APIs: The Glue of Microservices - Introduction to the Cell-based Architecture
- 1. API: the Glue of Microservices Introduction to the Cell-based Architecture Asanka Abeysinghe Vice President, Architecture - CTO Office WSO2, Inc
- 2. Motivation
- 3. Centralized & Layered picture credit: https://www.flickr.com/photos/kaktuslampa/
- 4. Greenfield < Brownfield picture credit: https://www.flickr.com/photos/137826074@N08/
- 5. Reference Implementations picture credit: https://www.marinersmuseum.org/
- 6. Underutilization of the Technology picture credit: http://unlocked.footlocker.com/
- 7. Not enough support for Agility
- 9. Timeline 9
- 12. picture credit: https://www.flickr.com/photos/imcountingufoz/ Rise of Microservices
- 13. Pragmatic Microservices Netflix: APIs Uber: Edge Gateway eBay: API Facade Gartner: Mini Services
- 14. Background: Layered Architecture with MSA 14
- 17. A code exposes through an interface that describes a collection of operations that are network accessible using a standardized messaging protocol. Service: Technical definition
- 18. 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: Technical definition
- 19. Software components that can be spontaneously discovered, combined, and recombined to provide a solution to a business problem. Service: Business definition
- 20. 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
- 22. The cell is the basic structural, functional, and biological unit of all known living organisms
- 24. 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
- 25. 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
- 27. Inter and Intra Cell communication 27
- 28. Connected Cells Cell gateway (ingress/egress) Sidecar Adaptor Ambassador
- 29. Gateway Pattern picture credit: https://www.flickr.com/photos/ell-r-brown/
- 30. 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?
- 31. Security of Cells picture credit: https://www.flickr.com/photos/laurelfan/ https://www.flickr.com/photos/sahdblunders/ 31
- 33. Lifecycle of a Cell
- 34. 34
- 35. 35
- 37. Structured Agility Versioned Components Versioned Cells Dependency managed Autowired Reusable MSA & CNA compliant
- 39. 39
- 41. 41
- 43. 43
- 44. Cells and Podular Organizations
- 45. 45 Connected Cells picture credit: https://www.medicalnewstoday.com/
- 47. Self-contained Deployable as a unit Independently elastic Data plane and control plane Summary: Cell-based Reference Architecture
- 48. picture credit: https://www.flickr.com/photos/josephmorris/ Just a (steady) start https://wso2.com/architecture/