04-17, 14:40–15:10 (Europe/Amsterdam), The Suite
Proxy-wasm is a standard that can be used to extend the features of proxies like Envoy to do things that can't be solved with pure configuration. The standard is rather young and has some very rough edges, both in the SDKs as well as languages and getting it loaded in a running Istio setup. In this talk, John talks about the experience going from nothing to a production setup and all the mistakes and faults that were discovered along the way (so you don't have to make them).
We've been modifying our HTTP traffic using proxy-wasm based on Go and Rust to get services migrated from an old home-grown traffic system on Mesos to Istio on Kubernetes. Along the way we've found that there isn't a whole lot of help out there, besides the many hello-world-type examples. This is a journey into learning how to wrangle proxy-wasm into something that is useful and works, even with all its shortcomings.
John has been working in the tech and cloud industry for a while and is currently leading the internal microservices and developer platform at Wehkamp. He is passionate about open source software and communities and tries to get teams to embrace open standards and systems for the betterment of us all.