Community & Extensibility: Building Envoy's Flexible Compression Subsystem
summary
Envoy now exposes compressors and decompressors as first‑class extensions (landed in v1.15) so different algorithms or implementations can be plugged in without changing HTTP filters; a reference Intel QAT compressor lives as an external extension (compress only today, decompression coming), and the old gzip filter is slated for removal by 1.17. Use cases proved practical: zero-touch bidirectional decompression between mobile clients (Envoy Mobile) and edge proxies, and hardware offload to free CPU. Benchmark note: an alternative gzip engine runs about 25% faster than Envoy's current gzip.
AI-written summary · about
chapters (16)
- 0:00Start
- 2:02Terminology
- 4:35Existing Advantages
- 7:37Community Collaboration
- 12:00Generic compressor HTTP filter
- 13:05Pluggable compressor libraries
- 13:32What about Decompression?
- 13:54Generic Decompressor HTTP filter
- 14:34End-to-end response compression solution
- 15:14Compression Extensions
- 16:43Rationale for hardware accelerated compression
- 17:39Hardware Accelerated Gzip
- 23:47Zero-touch response compression
- 26:38Bidirectional compression
- 27:06Compression Algorithm experimentation
- 27:43Envoy Compression Roadmap
related talks
33mThe End of a De...
01h 02mEnvoy Overview and Maintainer Q&A
13mClosing Remarks
26mRunning Envoy at the Edge
12mLightning Talk: Adding MxN Streaming Support for Envoy External Processing Filter
05mWelcome + Opening Remarks
36mFine Grained Mesh Metrics for Better Visibility With Native Performance
26mMaking Envoy Sustainable