The advantage is that you have _one_ Docker container for hosting your wasm host, and they can use some clever communications inside there, instead of having ma

The advantage is that you have _one_ Docker container for hosting your wasm host, and they can use some clever communications inside there, instead of having many containers which have to find each other and communicate using only basic networking primitives. At work I have a Rust web server with basically two parts - What humans see (HTML), and what computers see (API) The API rarely changes, and I was thinking of splitting them into two services so that I could iterate on the human side without worrying about breaking the API side. But I don't want to do that because it means extra management overhead in Docker, extra build steps, etc. And the Docker image is unwieldy from having all of Debian packed in it. So 1 Docker image with 2 Wasm servers in it, is less overhead (of ops) and less risk. I should still use testing to prevent the API breaking, and I still have to figure out a deterministic way to get Wasm images into the server, and measure the performance overhead of Wasm, but it's a tempting option.