Lightning Talk: Domain-Oriented Microservice Architecture with Kuma
summary
Argues that grouping services as mesh per domain gives true isolation by assigning each mesh its own CA so cross-domain calls require explicit gateways, reducing control-plane work because one control plane no longer recalculates config for unrelated meshes. Shows an Envoy-based MeshGateway (supports Gateway API) that keeps mTLS with per-mesh CA on, exposes domain-level routes, and enforces cross-domain routing and policy — demonstrated end-to-end and intended to prevent distributed monoliths.
AI-written summary · about
chapters (4)
related talks
36mThe Service Mesh: Past, Present, and Future [B]
31mDeploying Microservice Architectures with Cloud Foundry
09mLightning Talk: MARA: An Easily Deployable Modern Application Architecture
38mThe Untapped Power of Services - L7 Load Balancing Without a Service Mesh
56mArchitecting Cloud Native Microservices
31mMonolith to Microservices: A Guide to Seamless Transitions
34mArchitektury Aplikacji: The last mile of microservices
09mLightning Talk: Where Has My Circuit Breaker Gone?
