WebAssembly on Kubernetes • Nicolas Frankel • YOW! 2025

2026-07-21 · Source: GOTO Conferences · Field: Technology & Digital — Software Development & Engineering, Cloud Computing & IT Infrastructure, Emerging Technologies & Innovation · Depth: Intermediate, extended

Summary

Nicolas Frankel's presentation "WebAssembly on Kubernetes" explores the evolution and practical application of WebAssembly (Wasm) beyond its initial web-centric role. Wasm has expanded to support all programming languages for client and server applications, offering benefits like strong security sandboxing, small binary sizes, high performance, and broad OS/architecture compatibility. A key demonstration involved running an HTTP server within Kubernetes using Wasm. Three container types were compared: a native Rust build (12MB), a Wasm build with an embedded runtime (8MB), and a Wasm build from scratch (2MB). While the 2MB scratch container failed with Docker, it successfully ran on Kubernetes by configuring a WasmEdge shim to manage the Wasm runtime, mirroring how runc handles traditional containers. The speaker noted the WasmEdge runtime's limited maintenance and the rapid, sometimes unstable, evolution of the Wasm ecosystem, highlighting that code working six months prior required dependency downgrades.

Key takeaway

For startup CTOs or Lead Architects evaluating new technology stacks, WebAssembly on Kubernetes offers a compelling path to competitive advantage. You should consider adopting it for applications requiring strong security, minimal binary sizes (e.g., 2MB HTTP servers), and polyglot development. However, be prepared for the rapidly evolving and sometimes unstable ecosystem, which demands continuous investment to manage dependency changes and maintain operational stability.

Key insights

WebAssembly offers a secure, performant, and polyglot containerization alternative, especially for Kubernetes deployments.

Principles

• WebAssembly provides strong security through sandboxing.
• Small binary sizes are a core advantage of WebAssembly.

Method

Configure Kubernetes containerd to use a WasmEdge shim instead of runc for running WebAssembly containers.

In practice

• Run HTTP servers in 2MB WebAssembly containers on Kubernetes.
• Extend platforms like Envoy with performant, sandboxed Wasm plugins.

Topics

• WebAssembly
• Kubernetes
• Containerization
• WasmEdge Runtime
• Rust Programming
• Cloud Native Development

Best for: Software Engineer, MLOps Engineer, AI Engineer

Related on AIssential

• WebAssembly on Kubernetes • Nicolas Frankel • GOTO 2025 — WebAssembly extends beyond browsers, offering a secure, efficient, and tiny runtime for server-side and edge applications.
• The desktop infrastructure problem that kubernetes finally solves — Kubernetes can unify application and desktop infrastructure, offering operational consistency and enhanced security through containerized workspaces.
• Uber’s Hive Federation Decentralizes 16K Datasets and 10+ PB for Zero-Downtime Analytics at Scale — Decentralizing monolithic data warehouses via pointer-based migration enhances scalability, security, and operational autonomy.
• Kubernetes vs. OpenShift: Choosing DevOps and CI/CD Workflows — OpenShift extends Kubernetes into a comprehensive, integrated platform for streamlined DevOps and CI/CD workflows.
• How Zalando Built an In-Process Client-Side Load Balancer for One Million Requests per Second — Zalando built an in-process client-side load balancer for extreme high-throughput, improving latency and cost by moving routing logic closer to the application.
• Hidden Technical Debt of AI Systems: Agent Runtime — Agent runtime, not the model, is the primary source of technical debt and security risk in agentic AI systems.

See Counsel's argued verdicts on the open AI decisions leaders are weighing →

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by GOTO Conferences.