Oops!...I Did It Again — I Reinvented gRPC
summary
Spotify replaces a homegrown RPC stack with gRPC after years of running Hermes on 0mq, a working internal RPC, plus in-house tools like Helios and custom monitoring; Hermes scales but fragments tooling and slows composition. gRPC brings built-in load‑balancing, tracing, auth and uniform metrics across cloud services, so teams invest in a central proto registry and simple generators (a Maven plugin exists) while confronting migration cost and not‑invented‑here resistance.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 2:52History of Spotify tech
- 5:44Defining cloud native
- 7:48Lessons from in-house tools
- 10:53Strategic takeaways
- 12:49The gRPC case study
- 17:02Developer value proposition
- 19:39Future goals and community
- 25:17Q&A session
