Lyft’s Envoy and the Emerging Prospects of Service Mesh Architecture

September 26th, 2017 · 27 mins 21 secs

About this Episode

How best should an organization transition its old behemoth monolith architecture into the bright shiny new world of microservices? The principal software engineer of the brightest and shiniest service out there, Lyft, tells us you don't have to. Matt Klein told The New Stack Scott Fulton at PagerDuty Summit 2017, that a start up, just like Lyft was a few short years ago, can develop its own monolith more easily than it can develop complex microservices.

But with an underlying service mesh architecture, such as Klein's Envoy, that monolith can still be providing service-oriented functions to customers in the same way, and probably without service degradation.

Watch on YouTube: https://youtu.be/8GRDC5HbNZs

Episode Links

  • Lyft’s Envoy and the Emerging Prospects of Service Mesh Architecture — How best should an organization transition its monolith architecture into a set of microservices? Apparently, it might not have to. Matt Klein, principal software engineer at car-sharing service Lyft, told The New Stack at PagerDuty Summit 2017 that a startup can develop its own monolith more easily than it can develop complex microservices. But with an underlying service mesh architecture, such as Lyft’s Envoy, that monolith can still be providing service-oriented functions to customers in the same way, and probably without service degradation.