Join us on June 5th for a Tech Talk with Bill Doerrfeld and Kenn Hussey as we discuss the future of open source. Register now
Back to blog

The Mechanics of Deploying Envoy at Lyft

Matt Klein
July 27, 2017 | 4 min read
Deploying Envoy at Lyft

Deep Dive into Envoy Deployment at Lyft

The idea of the "service mesh" is becoming very popular in microservice design circles. However, the mechanics of deploying one into an existing infrastructure are far from simple. In this talk we will cover the logistical details of how Envoy was developed and deployed incrementally at Lyft, focusing primarily on the evolution of service mesh configuration management. We will also discuss why high level systems such as Istio are likely to be the main mechanism by which most customers ultimately get access to service mesh technology.

Transforming the Microservices Practitioner Virtual Summit Insights into Actionable Strategies

Understanding Envoy and Service Mesh

Before diving into the specifics, Matt offers a refresher on Envoy and the service mesh concept. He explains the fundamental role of Envoy as an out-of-process proxy, managing application traffic and simplifying network complexities for services.

Deployment Journey: From Monolith to Microservices

Matt outlines Lyft's transition from a monolithic architecture to a sophisticated microservice ecosystem. This section covers the step-by-step deployment strategies, starting with the initial use of Envoy as an edge proxy, moving through its integration into the monolithic core, and finally, the expansion across the service architecture.

Advanced Configuration and Management

The evolution of Envoy's configuration management at Lyft is highlighted, illustrating the shift from static JSON configurations to dynamic management with APIs. Matt discusses the current hybrid configuration approach and future plans for a more decentralized and dynamic configuration system.

A significant portion of the presentation is dedicated to the development of Envoy's control planes and APIs, including the transition from v1 to v2 APIs. This section also explores how Lyft handles service discovery and the role of various discovery services in maintaining efficient operations.

Looking Forward: The Role of Istio and Future Trends

Integration with Istio

Matt expresses enthusiasm for Istio, a project that separates the control plane from the data plane, offering a more robust and scalable approach to managing microservices. He elaborates on how Istio complements Envoy and the potential benefits for organizations adopting this framework.

Future Directions and Industry Impact

The concluding section discusses the future of microservices architectures, focusing on the integration of global load balancing, centralized health checking, and the potential for proprietary management servers. Matt shares his vision for the evolving landscape of microservice management and the critical role of community and open-source initiatives.

Conclusion: Harnessing Microservices for Optimal Performance

The summit wraps up with a Q&A session, where Matt addresses questions about network latency, configuration practices, and the strategic direction of Envoy within the CNCF. This blog post not only captures the essence of the summit but also serves as a guide for practitioners looking to implement or optimize their microservices architecture using Envoy and related technologies.

We hope this detailed exploration inspires you to consider new strategies in your microservices journey. For further engagement and to share your experiences, join the conversation at our upcoming summits and online platforms.