The application of Wasm has already started expanding in cloud-native infrastructure to Kubernetes, Envoy Proxy, and Envoy based solutions like Istio and Gloo. In particular, the Envoy project has been working to integrate and stabilize the use of Wasm as the model going forward for extensibility. Envoy is popular for its cloud-native architecture, performance, and that it can be extended in many ways through the use of filters, tracers, monitors, and more. Specifically, the filters are what’s used to modify the behavior of the proxy to manipulate the traffic that flows through it. The proxy ships with some filters out-of-the-box and with the open nature of Envoy, any end user can write and add their own filter to extend Envoy.
However there are challenges related to writing your own custom filters for Envoy including having enough expertise in C++ (Envoy language) to the effort needed to integrate and compile the customization to Envoy, and maintaining a separate build of Envoy over time. The addition of WebAssembly into the Envoy community and ecosystem dramatically improves, streamlines, and expands the ability to extend Envoy and Envoy based solutions like gateways and service meshes. Wasm provides the ability to dynamically update running Envoy processes without having restarts, isolation from failures and security issues, removes the overhead of compiling and maintaining a build of the Envoy code base, and comes with an active and growing developer community. (source: https://www.solo.io/solutions/webassembly/)
Who should attend?
All developers interested in the intersection of cloud native and web assembly.
