Ask HN: What do you think will come after Kubernetes?

1

Node-RED

#DevOps Tools #Automation #API Tools 120 social mentions

2

Wasmer

Docker enabled Kubernetes. Before then we really didn't have a unit of compute that could be reproduce easily in different environments. However, Docker has some downsides: (1) It centers the unit of computation in the Operating System layer (2) Docker relies on a completely homogeneous infrastructure (same chipset, almost same Operating System). (3) It relies on a Virtualization layer (usually KVM) to be run securely I believe (1) caused a vast amount of complexity when scaling, since you are scaling "OS Instances", not applications or functions, which caused Kubernetes to inherit most of this issues and be perhaps much more complex than it should. I think (2) is key because with new trends coming up (such as Edge Computing, Serverless, IoT and 5G) we are starting to have the need of running software universally across a more diverse infrastructure (different chipsets and OSs). And (1) and (3) causes a significant slow-down for startup times (see Firecracker state of the art project with a ~250ms best startup time - not good enough). I believe most of this issues are solved with WebAssembly: simpler scaling, universal execution across diverse infrastructure and fast startup times. And I'm actually working full-time in Wasmer [1] to make of this vision a reality! Please shoot me an email to syrus@wasmer.io if you are interested on working together on this vision :) [1] https://wasmer.io/.

#Software Development #Cross Platform App Dev Tools #WebAssembly 50 social mentions

3

Convox

Convox[1] is another one [1] https://convox.com/.

#Cloud Computing #Cloud Hosting #Environment As A Service 12 social mentions