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

Sep 26th, 2017 3:00pm by Scott M. Fulton III

Also available on Apple Podcasts, Google Podcasts, Overcast, PlayerFM, Pocket Casts, Spotify, Stitcher, TuneIn

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.

In this Edition:

1:56: Exploring service mesh architecture and the Envoy project.
9:09: Scale and the overall usefulness of microservices within the development process.
12:54: For startups, what are the virtues of monolithic architecture and where you start if you want to produce a monolith in record time?
17:12: What’s next for Envoy and the Istio project.
22:18: What is the difference between what .NET Core is doing and what Envoy is doing.
24:28: Building Envoy and what small development teams can accomplish.

Scott M. Fulton, III is a 39-year veteran technology journalist, author, analyst, and content strategist, the latter of which means he thought almost too carefully about the order in which those roles should appear. Decisions like these, he’ll tell you,...