A Decentralized Reference Architecture for Cloud-native Applications
summary
Presents a cell-based reference architecture that groups components (microservices, databases, brokers, UIs) into independently deployable units with a cell gateway as the single ingress and versioned cells/components. Describes local and global meshes — local and global control plane plus data planes — for policy, auth caching, and observability. Cites a failed Seattle project with 100 APIs 60 message flows 80 services to motivate the pattern, and shows reference builds using WSO2, nginx, Spring, Ballerina, Kubernetes, Docker and measures success by flow efficiency, MTTD and MTTR.
AI-written summary · about
chapters (18)
- 0:00Start
- 5:12Reality of the Enterprise
- 5:32Brownfield Greenfield
- 6:13Reference Implementations
- 8:49Timeline
- 12:12Rise of Microservices
- 14:03Microservice: Technical definition
- 14:45Microservice: Business definition
- 16:00Platform of Platforms
- 17:54Component: Atomic Units
- 18:34Cell: Units of Enterprise Architecture
- 19:08Group of (Micro)services
- 19:51Connected Cells
- 20:43Inter and Intra Cell communication
- 22:15API-first Architecture
- 23:46Security of Cells
- 29:21Cell Types
- 35:50Summary: Cell-based Architecture
related talks
24mA Decentralized Reference Architecture for Cloud-native Applications
41mA Decentralized Reference Architecture for Cloud-Native Applications
46mAn Emerging Architecture Pattern for Agile Integration: Cell-based Architecture
24mReference Architecture for a Cloud Native Digital Enterprise
06mHow to be API-centric and microservice friendly
40mCell-Based Approach
27mManaging the Complexity of Microservices Deployments - Prithpal Bhogill, Google & Kenny Bastini
56mArchitecting Cloud Native Microservices