3 ms·
You mean like the author says, at the end of the article: > I compare WebAssembly to K8s, but really it's more like processes and private namespaces. So one an
by x3ro 5y ago
You mean like the author says, at the end of the article:
> I compare WebAssembly to K8s, but really it's more like processes and private namespaces. So one answer to the question as initially posed is that no, WebAssembly is not the next Kubernetes; that next thing is waiting to be built, though I know of a few organizations that have started already.
> One thing does seem clear to me though: WebAssembly will be at the bottom of the new thing,
Edit: formatting
- kitd 5y agoYes, you're right. I missed that. A bit of a shame to leave it to the end though.
- ghostoftiber 5y agoWhenever anyone does that they might as well simply state "I wrote this entire article and then realized I was wrong". Writing is a thinking exercise.
- dr_hooo 5y agoSounds more like clickbait an some [0] [0]https://en.wikipedia.org/wiki/Betteridge%27s_law_of_headlines?wprov=sfla1 https://en.wikipedia.org/wiki/Betteridge%27s_law_of_headline...
- almostdeadguy 5y agoBut to the point that K8s has "nothing a priori to do with containers" made by a sibling comment to yours, there's no reason for WASM to necessitate "the next Kubernetes". WASM is just a different workload type that could be orchestrated w/ Kubernetes. I haven't looked too much into it, but I assume that's what projects like Krustlet are working on: https://krustlet.dev/ https://krustlet.dev/ I think that's kind of essential to understanding the role Kubernetes fulfills: it's an automation platform.