Panel: Were Microservices a Huge Mistake?
summary
Panel argues specific tradeoffs: one claim predicts a multi‑billion dollar cleanup industry from misapplied microservices; another warns of distributed monoliths and of baking org change into code. Examples and tools cited: Linkerd/service mesh, Kubernetes, GraphQL, Dagster, distributed tracing; case numbers like Uber’s ~5,000 services and votes shifting from 98 voters (77.6% saying “not a mistake”) to 49 voters (50% overall, team‑mistake at 26.5%, ~+4% swing). Microservices make routine changes faster but raise p99, cross‑cutting, GDPR and ownership costs.
AI-written summary · about
chapters (7)
- 0:00Introduction and voting
- 1:27Panelist introductions
- 12:07Opening statements
- 29:45Debate begins
- 37:56Technology impact on microservices
- 55:00Closing statements
- 1:02:15Voting results and Q&A
related talks
43mPanel: Microservices, Where Did It All Go Wrong
44mMicroservices, Where Did It All Go Wrong
55mMicroservices, Where Did It All Go Wrong
01h 00mMicroservices, Where Did It All Go Wrong?
47mMicroservice Panel
42mMicroservices are Not Worth the Trouble!!??
43mHow to Avoid Doing Microservices Completely Wrong
06mIGNITE: Are you still doing microservices?