3 ms·
Is there a purpose to using WASM for this if you control the whole server/VM? i.e. it's not shared by a bunch of multi-tenant services, which means your server
by brundolf 4y ago
Is there a purpose to using WASM for this if you control the whole server/VM? i.e. it's not shared by a bunch of multi-tenant services, which means your server trusts the service being run. Your server would also not have to be language-agnostic, so you could just push the code and then build a native binary on the server itself
I guess if you're really worried about layered security the extra sandboxing could be desirable, to protect the other services in case one of them gets compromised
- Kinrany 4y agoThe thought is that compiling to WASM results in less overhead than wrapping in a container.
- brundolf 4y agoSure, but I'm suggesting you could skip the container too if all you need to deploy is a binary anyway
- pjmlp 4y agoI see it as ideas for venture capitalists trying to make a business out of WebAssembly, that should never have left the browser anyway. Maybe if we ignore it long enough it will go the way of NoSQL hype wave.
- brundolf 4y agoI think WebAssembly can be plenty valuable outside the browser, I just don't see much value in the exact use-case from the OP But it's probably just for the sake of example and not intended to be a real life use-case