wonder what the 'orchestration feature set' of 2 years in the future will be
speaking just for myself, feels like I want a system that runs a mix of serverless (like knative), normal containers, raw linux binaries (easy w/ fat binary systems like golang), language-specific packages like heroku does, maybe firecracker VMs.
hard to get knative right if you don't have a reverse proxy tightly integrated with your tool
Wild guess, probably more than 2 years ahead (also kinda what I'm hoping for)
A natively distributed runtime providing similar capabilities to Docker + Nomad but running on "bare" WASM, providing a compilation target, distributed and clustering primitives right in your application code.
Imagine the nodejs cluster module, targeting nomad directly, or talking to an instance of a service running on another node, the communication and addressing would be handled by the runtime.
Similarly, cluster or instance level ports could be opened directly from your code and the distributed runtime will do the external/internal load balancing. Maybe taking it one step further and advertising services directly abstracting ports away.
Service mesh + Scheduling + Capability-based Runtime in one binary you could run on Linux. One can dream.
speaking just for myself, feels like I want a system that runs a mix of serverless (like knative), normal containers, raw linux binaries (easy w/ fat binary systems like golang), language-specific packages like heroku does, maybe firecracker VMs.
hard to get knative right if you don't have a reverse proxy tightly integrated with your tool