Avoid Building a Microservices Death Star
summary
Microservices often proliferate until the system becomes a brittle “death star” of dozens or hundreds of services. The talk claims the fix is not just more services but combining service mesh for discovery and networking with API management as a governance layer, adding a dedicated microgateway for east‑west traffic and application‑layer policies. It points out service meshes run at layer 4 and miss masking, user identity, business routing and analytics, and promotes Upmesh (API + mesh integration) to restore visibility and control.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 0:57Tradeoff between agility flexibility and scale
- 1:40Summary
- 2:13The Obvious
- 2:46Simplicity
- 3:11Why dont we do more
- 4:19Why its so bad
- 4:48What went wrong
- 7:13Service Mesh
- 8:20DomainDriven Design
- 8:52Ingress controllers
- 9:21Datadriven design
- 10:06Controlling microservices
- 10:52Missing components
- 11:09Apis and microservices
- 11:35Microgateway
- 12:43Service meshes
- 12:55One fundamental flaw
- 13:23Service Mesh will fall short
- 14:36Upmesh Architecture
- 15:00Control Governance
- 15:42Summarize
- 17:19SoftwareG Cloud
- 17:42Questions
- 18:00Service Measures
related talks
23mMicroservices Architectures: Agility vs Complexity
29mImpact of Microservices Architecture on API Management
26mBuilding Scalable Microservice APIs From The Beginning
52mI Have a Microservices Architecture and I Didn't Know.
44mMicroservices, Where Did It All Go Wrong
14mMonolith 2 MicroServices Houston we've got a problem
57mEmbracing Microservices
35mAdvanced Microservices Architectures