A declarative solution that combines terraform + k8s + hardware management, that elegantly partitions between stateful and stateless resources. Stateful resources will have well defined, easy to understand modes of behavior, explicitly describing caching policies and persistence layers.
Ask HN: What do you think will come after Kubernetes?
31–40 of 176 posts
Re: Ask HN: What do you think will come after Kubernetes?
#32I think Kubernetes will be a part of things (as Docker still is) but it'll be the next level of abstraction -- the thing that turns Kubernetes into Heroku. There's been a few popping up recently, time will tell who wins
What have you seen in that space so far?
Space Cloud https://news.ycombinator.com/item?id=26997595
and Porter https://news.ycombinator.com/item?id=26993421
were the ones I've seen recently, although admittedly on re-look I may have misunderstood Space Cloud and I could have sworn there was a third
Re: Ask HN: What do you think will come after Kubernetes?
#33Hopefully some sanity! But realistically serverless functions.
Re: Ask HN: What do you think will come after Kubernetes?
#34Somebody wins the market and stays until the market disappears due to innovation.
If we were to say that it is not established enough and it could be disrupted within the existing market then I like Nomad, good enough for most cases I think, a lot simpler.
Disclaimer: I have not Kubernetes experience, show a few documents and opted for Nomad with great success so far.
Re: Ask HN: What do you think will come after Kubernetes?
#35A declarative solution that combines terraform + k8s + hardware management, that elegantly partitions between stateful and stateless resources. Stateful resources will have well defined, easy to understand modes of behavior, explicitly describing caching policies and persistence layers.
It may abstract many differences between monoliths and microservices
Re: Ask HN: What do you think will come after Kubernetes?
#36Kubernetes automates and standardizes some of the best practices around building reliable systems in a platform agnostic way. We never got there with VMs: Amazon ec2 instances are not the same as GCE instances are not the same as VMware VMs but a kubernetes api is the same everywhere (and providers are incentivized to standardize their offerings). Whatever comes next would have to be something that can standardize ev…
> We never got there with VMs: Amazon ec2 instances are not the same as GCE instances are not the same as VMware VMs
This is true but is that such a huge deal? We successfully moved from AWS to GCP and it wasn't a massive deal; just different terminology for the same concepts.
Re: Ask HN: What do you think will come after Kubernetes?
#37Something simpler. Please god.
Re: Ask HN: What do you think will come after Kubernetes?
#38Now I don't need to download, setup and install Postgresql, I can run it with Docker with one command.
Why don't do the same for a typical Kubernetes setup with Hasura, API server, Gateway, load balancer, Postgresql, Redis, and a couple of services for logs and monitoring all in one, with all the networking stuff already setup? Just give me an image or template made by someone else, maintained on Github, and ready to customise and develop for my needs.
Re: Ask HN: What do you think will come after Kubernetes?
#39A new programming language which hides the fact that your code is running across multiple machines from you. Similar to OOP, you'll define some level of structure and the compiler will figure out how to best distribute it across the resources given to it.
Re: Ask HN: What do you think will come after Kubernetes?
#40Something much, much, simpler. I'm not convinced that /for most companies/ k8s adds enough value when compared to all the added complexity (not to mention the yaml soup!).
Working for a small startup that uses both k8s and more traditional infrastructure, I've found the yaml soup that comprises a reliable k8s system is not much worse than the yaml/hcl soup of our ansible/terraform provisioning scripts.