Berlin

November 4 & 5, 2024

New York

September 4 & 5, 2024

The (updated) story of why we migrate to gRPC and how we go about it

Matthias Grüter addresses technical discussions of advanced gRPC concepts such as interceptors, load balancing, and traffic management and how they are essential in large distributed systems.

Register or log in to access this video

Create an account to access our free engineering leadership content, free online events and to receive our weekly email newsletter. We will also keep you up to date with LeadDev events.

Register with google

We have linked your account and just need a few more details to complete your registration:

Terms and conditions

 

 

Enter your email address to reset your password.

 

A link has been emailed to you - check your inbox.



Don't have an account? Click here to register
December 20, 2022

At Spotify, we have historically built services based on our own proprietary messaging protocol and framework. Three years ago we kicked off the daunting multi-year task of migrating everything to gRPC. Migrating over 3000 services to gRPC poses interesting challenges, many of them are not technical in nature – it all boils down to questions of engineering culture and leadership at scale: How do you get 400 autonomous engineering teams to align on something as fundamental and cross-cutting as a new RPC framework? How do you roll-out gRPC at scale with minimal disruption to both the organization and to the end-user? This presentation will address these questions alongside more technical discussions of advanced gRPC concepts such as interceptors, load balancing, and traffic management and how they are essential in large distributed systems.