A decentralized reference Architecture for Cloud-Native applications
summary
A decentralized “cell” reference architecture defines a cell as a unit that bundles components (microservices, databases, brokers) behind a cell gateway and connects cells via local/global control plane and data plane meshes; it proves vendor-neutral with a reference implementation using Kubernetes, nginx, Spring Boot, Kafka and WSO2 components, supports sidecar/ambassador egress, versioned components and cells, converts monoliths into cells, and improves metrics like flow efficiency and mean time to repair.
AI-written summary · about
chapters (21)
- 0:00Start
- 2:45Centralized & Layered
- 3:37Reality of the Enterprise
- 4:02Brownfield Greenfield
- 4:27Reference Implementations
- 6:18Timeline
- 9:02Rise of Microservices
- 10:26Microservice: Technical definition
- 10:57Microservice: Business definition
- 12:31Platform of Platforms
- 13:50Component: Atomic Units
- 14:24Cell: Units of Enterprise Architecture
- 14:42Group of (Micro)services
- 15:19Connected Cells
- 16:31API-first Architecture
- 17:15Security of Cells
- 19:15Cell Types
- 20:17Cells and Cellular Organizations
- 20:40Measure the success
- 21:09Summary: Cell-based Architecture
- 21:22Invitation to consume and contribute
related talks
27mBuilding an Edge Computing Platform for Network Services Using Cloud Native Technology [I]
04mDecentralized architecture patterns
31mReverse Engineering Cloud Native: Interoperability and Community
11mThe Makings of a Modern Application Architecture
28mConnectivity Patterns for Cloud Native Applications
36mResilient Multi-Cloud Strategies: Harnessing Kubernetes, Cluster API, and Cell-Based Architecture
09mKeynote: Build an Open Source Distributed Cloud Native World
25mStandardizing Cloud Native Application Delivery Across Different Clouds