How Lyft Built a Service Mesh with Envoy

SHOW: 403

DESCRIPTION: Brian talks with Jose Nino (@junr03, Software Engineer @Lyft) about how they evolved from a monolithic application to 300+ microservices, including a service mesh using the Envoy proxy.

SHOW SPONSOR LINKS:

Datadog Homepage - Modern Monitoring and AnalyticsTry Datadog yourself by starting a free, 14-day trial today. Listeners of this podcast will also receive a free Datadog T-shirtDash is a two-day conference presented by Datadog. Learn about building and scaling the next generation of applications, infrastructure, and technical teams. Register today at https://www.dashcon.io/attend/Digital Ocean HomepageGet Started Now and Get a free $50 Credit on Digital OceanGet 20% off VelocityConf passes using discount code CLOUD

SHOW INTERVIEW LINKS:

Envoy Proxy [homepage]Jose Nino’s talk at Velocity Conf

SHOW NOTES:

Topic 1 - Welcome to the show. Tell us a little bit about your background and some of the things you work on at Lyft. 

Topic 2 - Lyft was the original creator of the Envoy proxy project. As Lyft was going through their migration from a monolith to microservices, when did they realize that they needed to start creating a service mesh. 

Topic 3 - What functions of Envoy does Lyft use for both networking and security?

Topic 4 - How does Lyft manage who interacts with the Service Mesh, since it has impacts on the applications (microservices) and the infrastructure teams (networking, security)? 

Topic 5 - What recommendations would you make to any other teams that are evaluating Envoy or Service Mesh technologies? 

FEEDBACK?

Email: show at thecloudcast dot netTwitter: @thecloudcastnet and @ServerlessCast