As a software architect, I hate serverless. Not because it doesn't work, but because it forces design constraints that cripple your application. Here's why always-on servers matter.
I assume WASM will grow in popularity to ultimately replace containers and an open source serverless platform will emerge that has similar ubiquity to k8s. So far, we have projects like wasmCloud and Fermyon.
If WASM+WASI existed in 2008, we wouldn’t have needed to create Docker. That’s how important it is. WebAssembly on the server is the future of computing. - Solomon Hykes (co-founder of Docker)
Considering how important WASM is, I haven’t seen a single application of it.
WASM on the server seems especially weird since it’s not much more than a bytecode interpreter. At that point you could just use a JVM, maybe with some more cut-down API to make it more sandboxed.
I assume WASM will grow in popularity to ultimately replace containers and an open source serverless platform will emerge that has similar ubiquity to k8s. So far, we have projects like wasmCloud and Fermyon.
Huh? How would wasm replace containers?
Wasm will allow writing for web browser in golang and php. Server containers won’t go away
Considering how important WASM is, I haven’t seen a single application of it.
WASM on the server seems especially weird since it’s not much more than a bytecode interpreter. At that point you could just use a JVM, maybe with some more cut-down API to make it more sandboxed.
Well duh. But now it’s too late. It’s not replacing docker in part because mere execution is not only thing docker does.
I’m telling, I’m fully set for writing pho in the browser. Just to fuck with my dev team