Has Anyone Actually Used WASM in Production to Replace Docker?

I’ve had some success running projects using WASM where I could keep user data secure without needing a backend. It's efficient for certain applications, although some standards in the WASI specification are still pending, so you might hit some bumps. But it's definitely exciting!

I utilize WASM binaries as plugins within my existing setups, usually stored in an OCI container registry. It enhances rather than replaces containers because it seamlessly integrates with existing infrastructure while optimizing performance for specific tasks.

We're dabbling in using WASM primarily to shift some backend workloads to run in users' browsers, rather than replacing Docker or Kubernetes entirely. It feels like a cool tool, but it's more of a supplement at this stage.

WASM itself doesn’t replace Docker directly, but it can be used in some cases as a more lightweight alternative for certain workloads. There are projects like Spinkube that let you run WASM modules for serverless functions without needing full containerization. In theory, WASM plus WASI can provide smaller sizes and faster starts, but it's still not widely adopted. So, while it's promising for security and efficiency, it's not a full Docker replacement just yet.

It's awesome that you're exploring this topic! The goal of WASM is to create a universal executable that fits into modern workflows. Instead of packaging your Python code with all its dependencies, you can just compile it to a WASM target. That way, you avoid the hassle of managing different images for different architectures, which is pretty convenient.