Cloud & Architecture

This week on The InfoQ Podcast Wes Reisz talks with the CTO of Bouyant Oliver Gould. Bouyant is the maker the LinkerD Service Mesh and the recently released Conduit. In the podcast, Oliver defines a service mesh, clarifies the meaning of the data and control plane, discusses what a Service Mesh can offer a Microservice application owners, and, finally, discusses some of the considerations they took into account developing Conduit.

Why listen to this podcast:

- Service mesh is dedicated infrastructure that handles interservice communication.
- There are two components to a service mesh: the data plane handles communication and the control plane is about policy and config.
- LinkerD and Conduit are two open service meshes made by Bouyant. Conduit has a small memory footprint and provides a convention over configuration approach to service mesh deployment.
- Adopting Rust (language used for implementing the data plane in Conduit) requires thinking of memory differently, and the best way to adopt Rust is to read other people’s code.

More on this: Quick scan our curated show notes on InfoQ http://bit.ly/2skWF61

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

Subscribe: www.youtube.com/infoq
Like InfoQ on Facebook: bit.ly/2jmlyG8
Follow on Twitter: twitter.com/InfoQ
Follow on LinkedIn: www.linkedin.com/company/infoq
Check the landing page on InfoQ: http://bit.ly/2skWF61

Show Notes

Oliver Gould on Service Mesh for Microservices, LinkerD, and the Recently Released Conduit

Owen Garrett, Head of Products @NGINX, talks about some of the biggest challenges companies are facing transitioning from monoliths to microservices. He describes the proxy model (Kubernetes-Ingress controller model), delves into why and when you might need to use a service mesh and reviews the various service mesh products on the market today.  Finally, he introduces NGINX Unit, a dynamic web and application server – configured via API – that is designed to run applications in multiple languages. https://unit.nginx.org/	

Owen Garrett leads the product and go-to-market strategy for NGINX’s web acceleration and application delivery technologies. Owen has over 15 years of experience in software engineering and product leadership at companies such as Zeus and Riverbed, and holds a number of patents in the field.

InfoQ Podcast

Owen Garrett: Pragmatic Microservices, Service Mesh, and NGINX Unit

On today’s podcast, Wes Reisz talks to Matt Klein about Envoy. Envoy is a modern, high performance, small footprint edge and service proxy. While it was originally developed at Lyft (and still drives much of their architecture), it is a fully open source driven project. Matt addresses on this podcast what he sees as the major design goals of Envoy, answers questions about a sidecar performance impact, discusses observability, and thinks out loud on the future of Envoy.

Why listen to this podcast:

- Envoy’s goal is to abstract the network from application programmers. It’s really about helping application developers focus on building business logic and not on the application plumbing.
- Envoy is a large community driven project, not a cohesive product that does one thing. It can be used as a foundational building blocks to extend into a variety of use cases, including as an edge proxy, as a service mesh sidecar, and as a substrate for building new products.
- While there is performance cost for using sidecar proxies, the rich featureset is often a worthwhile tradeoff. With that said, there is work being done that is greatly improving Envoy’s performance.
- Envoy is built to run Lyft. There were no features that were in Envoy when it was open sourced that were not used at Lyft.
- Envoy emits a rich set of logs and has a plugable tracing system. The goal is observability first and one of the main project goals.
- Lyft deploys Envoy master twice per week.
- Envoy’s roadmap includes work on automating settings (rate limits and retries), focus on ease of operation (such as where things got routed what the internal timings), and additional protocol support such as Kafka.

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

Subscribe: www.youtube.com/infoq
Like InfoQ on Facebook: bit.ly/2jmlyG8
Follow on Twitter: twitter.com/InfoQ
Follow on LinkedIn: www.linkedin.com/company/infoq
Check the landing page on InfoQ: https://bit.ly/2tmUKMl

Cloud & Architecture

buddhima-w-wickramasinghe