Today on The InfoQ Podcast, Wes Reisz speaks with CEO and founder of Solo Idit Levine. The two discuss the Three Pillars of Solo around Gloo, their API gateway, interoperability of service meshes (including the work on Service Mesh Interface), and on extending Envoy with Web Assembly (and the recently announced Web Assembly Hub).

Why listen to this podcast:

- Gloo is a Kubernetes-native ingress controller and API gateway. It’s built on top of Envoy and at its core is open source.

- The Service Mesh Interface (SMI) is a specification for service meshes that runs on Kubernetes. It defines a common standard that can be implemented by a variety of providers. The idea of SMI is it’s an abstraction on top of service meshes, so that you can use one language to configure them all.

- Autopilot is an open-source Kubernetes operator that allows developers to extend a service mesh control plane.

- Lua has been commonly used to extend the service mesh data plane. Led by Google and the Envoy community, web assembly is becoming the preferred way of extending the data plane. Web assembly allows you to write Envoy extensions in any language while still being sandboxed and performant.

- WebAssembly Hub is a service for building, deploying, sharing, and discovering Wasm extensions for Envoy.

- Wasme is a docker like an open-source commandline tool from Solo to simplify the building, pushing, pulling, and deploying Envoy Web Assembly Filters.

More on this: Quick scan our curated show notes on InfoQ https://bit.ly/37sYIoE

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/37sYIoE