A Decentralized Reference Architecture for Cloud-native Applications
summary
A decentralized, cell‑based reference architecture claims to replace layered stacks with self‑contained deployable units called cells, each grouping components (services, gateways, DBs, brokers) behind a cell gateway and exposing API‑first intercell communication for REST, gRPC, events or streams. It supports legacy and microservices, enforces policies, observability and either local STS or external IdP security, and enables per‑cell versioned deployments (blue/green, canary) for “structured agility.” Reference artifacts include language/runtime work such as Ballerina and a sample implementation plus local and global control and data planes.
AI-written summary · about
chapters (22)
- 0:00Start
- 4:42Centralized & Layered
- 5:44Reality of the Enterprise
- 6:09Brownfield Greenfield
- 6:52Reference Implementations
- 9:15Timeline
- 11:07Rise of Microservices
- 11:57Platform of Platforms
- 14:27Microservice: Technical definition
- 14:52Microservice: Business definition
- 15:13Group of (Micro)services
- 15:47Component: Atomic Units
- 16:06Cell: Units of Enterprise Architecture
- 16:27Connected Cells
- 16:57Inter and Intra Cell communication
- 17:49API-first Architecture
- 18:18Security of Cells
- 19:53Cell Types
- 20:50Cells and Cellular Organizations
- 21:38Measure the success
- 22:20Summary: Cell-based Architecture
- 22:37Invitation to consume and contribute
related talks
39mA 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
06mHow to be API-centric and microservice friendly
24mReference Architecture for a Cloud Native Digital Enterprise
37mWorkshop on Defining a Reference Model for Cloud-Native Application Delivery
40mCell-Based Approach
11mThe Makings of a Modern Application Architecture