Sidecars, eBPF and the Future of Service Mesh

Controversy over the future of service meshes and their architectures is swirling. This is a vital discussion as enterprise migration to microservice and Kubernetes-based architectures continue. This talk incorporates the latest community developments to explore what the future looks like.

A lot of dust has been kicked up recently around the roles of sidecars, Envoy proxy, and eBPF in the future of service meshes. Envoy proxy is the de-facto proxy for service mesh implementations today, and it delivers excellent support for Layer 7 capabilities that most users need. There is no question that eBPF and the OS Kernel can be used to improve the execution of the network at Layer 3/4 (short circuiting for optimal paths, offloading TLS/mTLS, observability collection, etc). But complex application networking features (retries, timeouts, TLS, HTTP2 protocol, etc) must remain in the user space at L7.

eBPF offers a great complement to the sidecar proxy, but is it a replacement?

Can the two co-exist? How can we optimize proxy placement?

In this talk, we explore the challenges of service mesh today, along with the latest developments in what the service mesh community is doing to improve its implementations. Both slides and a live demo will be presented.


Speaker

Jim Barton

Field Engineer @Solo

Jim Barton is a Field Engineer for Solo.io whose enterprise software career spans 30 years. He has enjoyed roles as a project engineer, sales and consulting engineer, product development manager, and executive leader of tech startups. Prior to Solo, he spent a decade architecting, building and operating systems based on enterprise open-source technologies, at the likes of Red Hat, Amazon, and Zappos. After two years of COVID-driven, Zoom-encrusted isolation, Jim especially enjoys sharing with and learning from three-dimensional people at technical conferences around the world.

Read more
Find Jim Barton at:

Date

Tuesday Oct 25 / 05:25PM PDT ( 50 minutes)

Share

From the same track

Session

API Evolution Without Versioning

Tuesday Oct 25 / 10:35AM PDT

Versioning is usually the first–and too often, the only–technique architects reach for when imagining a breaking change to an API’s interface. Based on my experience managing the evolution of a public API, I’ve recently cataloged several alternative techniques and their tradeoffs.

Brandon Byars

North America Head of Technology @thoughtworks

Session

What API Product Managers Need

Tuesday Oct 25 / 11:50AM PDT

More details coming soon.

Deepa Goyal

Product Strategy @Postman

Session

Scaling GraphQL Adoption at Netflix

Tuesday Oct 25 / 01:40PM PDT

GraphQL is steadily gaining popularity as an API technology choice for Client to Server communication. However, it can be daunting to realize the benefits of GraphQL without significant investment.

Tejas Shikhare

Senior Software Engineer @Netflix

Session

Who Cares About Your API?

Tuesday Oct 25 / 02:55PM PDT

Who cares about your API?  Everyone. DevOps has shown us that when developers care about operations, they write better software.  What other viewpoints should developers consider when they're building software?

Brandon Byars

North America Head of Technology @thoughtworks

Jim Barton

Field Engineer @Solo

Deepa Goyal

Product Strategy @Postman

Tejas Shikhare

Senior Software Engineer @Netflix

Session

Unconference: Modern APIs

Tuesday Oct 25 / 04:10PM PDT

What is an unconference? At QConLondon, we’ll have unconferences in most of our tracks.

Shane Hastie

Director of Agile Learning Programs @ICAgile