Hundreds of Microservices without breaking your APIs

on YouTube ↗31m

" summary

Describes how a system that grows to 120 microservices introduces unknown producers and consumers, how switching sync HTTP to kafka persists messages avoids data loss but explodes the dependency graph, and how instrumenting services with OpenTelemetry + Jaeger yields per-request traces, trace IDs in logs, and the ability to replay or auto-generate mocks and docs from real traffic. Claims: tracing plus persisted async messaging reduces incident time and improves test fidelity; demonstrates tools, tradeoffs, and concrete workflows.

AI-written summary · about

" chapters (13)

1. 0:00Start
2. 0:41Microservices complexity
3. 3:07Microservices growth
4. 7:21Production risks
5. 11:34HTTP limits
6. 14:21Async challenges
7. 17:31Complexity scaling
8. 18:55Distributed tracing solution
9. 21:47How tracing works
10. 24:12Debugging with tracing
11. 25:56Service dependencies
12. 27:44Tracing data uses
13. 30:32Summary

" related talks

• 31mUnderstanding Microservices with Distributed TracingLita Cho · Strange Loop 2018
• 39mObservable microservicesMaria Gomez, Taruj Mathur · Codemotion Madrid 2017
• 20mHigh Velocity Development of MicroservicesVenky Ganti, Rahul Lahiri · GOTO Chicago 2020
• 50mChallenges in Implementing MicroservicesFred George · GOTO Copenhagen 2015
• 33mEffective observability in microservice architecturesLesley Cordero · LeadDev New York 2022
• 49mChallenges in Implementing MicroservicesFred George · GOTO Amsterdam 2015
• 45mMicroservices: A retrospectiveTomer Gabel · Øredev 2019
• 01h 18mIn Defense of MicroservicesChad Green · Conf42 Cloud Native 2025