The latest articles on DEV Community by Sam Price (@price_76). https://dev.to/price_76 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4211012%2Fe55e8ec6-0010-421a-9cb6-609d154ee353.jpg https://dev.to/price_76 en Sam Price Tue, 27 Oct 2026 15:51:44 +0000 https://dev.to/price_76/webassembly-modules-as-deploy-artifacts-4dn8 https://dev.to/price_76/webassembly-modules-as-deploy-artifacts-4dn8 <p>We started deploying a few internal tools as WebAssembly modules instead of containers. The pitch was simple: smaller artifacts, faster cold starts, one runtime.</p> <p>What we learned:</p> <ul> <li>Cold start went from seconds to milliseconds</li> <li>The artifact is a single file, which makes rollbacks trivial</li> <li>Sandboxing is a real security win for untrusted plugins</li> </ul> <p>The rough edges:</p> <ul> <li>Debugging is still immature</li> <li>Not every library compiles cleanly</li> <li>Observability needs custom plumbing</li> </ul> <p>We're keeping it for small, stable tools and staying on containers for the rest. But I think WASM-as-artifact is going to be normal in a few years.</p> <p>Right now I'm digging into the module format and the memory model. It's a good excuse to learn something new.</p> devops webassembly deployment