How One Startup Uses WebAssembly to Replace Container Sidecars

Failed to add items

Sorry, we are unable to add the item because your shopping cart is already at capacity.

Add to basket failed.

Please try again later

Add to wishlist failed.

Please try again later

Remove from wishlist failed.

Please try again later

Adding to library failed

Please try again

Follow podcast failed

Unfollow podcast failed

How One Startup Uses WebAssembly to Replace Container Sidecars

Listen for free

View show details

Episode 78 dives into a specific technical decision: how one early-stage infrastructure startup replaced its sidecar proxies with WebAssembly modules running in the data plane. Lucas and Luna walk through the company's original architecture—a standard Envoy sidecar per pod—and the problems that emerged as they scaled to 200 microservices: memory overhead, version drift, and cold-start latency. They explain the shift to a Wasm-based filter chain, how it cut memory-per-node by 60 percent and reduced deployment coupling between platform and product teams. Luna raises the operational trade-off: Wasm debugging is still immature. Lucas points to the emerging Wasm ecosystem—specifically the bytecode alliance's runtime and the rise of Wasm-native API gateways. The episode ends with a reflection on when a sidecar replacement makes sense and when it doesn't, using the startup's specific metrics as the guide. If you're evaluating service mesh alternatives or wondering where WebAssembly fits in production infrastructure, this episode gives you one grounded example to start from. #WebAssembly #SidecarProxy #Envoy #ServiceMesh #CloudNative #Infrastructure #Startup #Microservices #PlatformEngineering #BytecodeAlliance #WasmRuntime #DataPlane #PodArchitecture #ColdStart #MemoryOptimization #BusinessAndTechnology #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo

No reviews yet