A Decentralized Reference Architecture for Cloud-Native Applications
summary
Claims a cell gateway that enforces ingress, egress and per-cell policies, groups runtimes into self-contained cells, and versions components and cells separately. Offers a Kubernetes-based reference using Kubernetes CRDs, WSO2 runtimes, Node.js/Nginx/Angular/React and the Ballerina language. Cites a surprising case: a supposedly agile platform with 100+ APIs, 60 message flows and 80 services that took three years to deliver. Measures success by flow efficiency, MTTR and MTTD.
AI-written summary · about
chapters (27)
- 0:00Start
- 1:46Objectives
- 3:20Centralized & Layered
- 4:39Reality of the Enterprise
- 5:09Brownfield Greenfield
- 5:51Reference Implementations
- 7:11Gap: architecture | development | deployment
- 7:56Timeline
- 10:54Rise of Microservices
- 12:55Microservice: Technical definition
- 13:27Microservice: Business definition
- 14:08Background: Layered Architecture with MSA
- 14:31Background: Segmented Architecture
- 14:52Platform of Platforms
- 16:59Component: Atomic Units
- 17:33Cell: Units of Enterprise Architecture
- 18:00Group of (Micro)services
- 18:50Connected Cells
- 19:35Inter and Intra Cell communication
- 21:05API-first Architecture
- 22:02Security of Cells
- 25:45Cell Types
- 28:27Human-centric Architecture
- 29:46Defining Cell boundaries
- 31:06Measure the success
- 33:21Summary: Cell-based Architecture
- 34:08Invitation to consume and contribute
related talks
39mA Decentralized Reference Architecture for Cloud-native Applications
24mA 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
27mCloud Native: why, oh why?
18mArchitecting Resilient Cloud Native Applications: A Practical Guide to Deployment and Runtime