Live data from Hacker News

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

news.ycombinator.com

151–160 of 176 posts

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

#151

I think the question is: what comes after micro services/distributed systems? Whatever that is, will make k8s obsolete. My bet: rich fat clients. Super powerful phones that can run your entire e-commerce monolith to process my checkout. I’m talking about hosting your backend (most of it) and DB on my phone. Cheap syncs from my phone to your “main” server is fine because I’m always online and I have 10G connection. Th…

How would such a fat client setup handle authorisation?

Closest thing to what you mention is fire base as a back end. I guess that can work.

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

#152
But Erlang / Elixir seemed very promising to me.

- Supervisor processes. - Small process size. - Failure friendly design.

All of which allows easy vertical / horizontal scaling, robust concurrency and scalability, and automated process management.

Seemed promising the way WhatsApp / Discord have used this. Obviously not a classic DevOps deployment or a direct competitor for Kubernetes. But doesn't disruption happen from the sidelines?

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

#153

As businesses start to realize microservices aren't really worth it due to the complexity and cost it entails, they will start reverting back to hosting monoliths on VMs or services like Heroku/Netlify/Laravel Forge/Beanstalk, and they'll find out they can save a lot of money on compute and man hours by doing this. For more simple workflows, e.g. a single API endpoint, there's serverless and other SaaS services out t…

Microservices are worth it, just not for every use case. It sounds like you're blaming Google for misleading PMs into using something they didn't need. However, Google made a great product for those who need it. It's not google's fault that PMs love cargo-culting.

What makes you think it’s PMs making architecture decisions? That’s usually the engineers and engineering leaders (as it should be).

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

#154

As businesses start to realize microservices aren't really worth it due to the complexity and cost it entails, they will start reverting back to hosting monoliths on VMs or services like Heroku/Netlify/Laravel Forge/Beanstalk, and they'll find out they can save a lot of money on compute and man hours by doing this. For more simple workflows, e.g. a single API endpoint, there's serverless and other SaaS services out t…

Portainer comes to mind.

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

#155
post #20

Something 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.

I find Ansible simple: it's just a way of sending over the wire idempotent commands. It's like bash scripts, but better. On the other hand, k8s is a best of hundreds of heads.

Sure, yaml is a pita in both of them.

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

#156
post #25

I very much hope to see Hashicorp Nomad getting more traction, as a simpler, yet feature rich solution to probably most use cases in our industry. Pretty interesting to see the adoption of podman and also micro-vms (like fly.io does it), and other Nomad providers that does not nessasarly need to be docker. I know there are great terraform modules out there already, but i wonder if many of Hashicorp's products soon wi…

Problem is, hashicorp stuff is so scattered and it's really not documented how to combine all the things (TF, nomad, consul, vault, all documented and released independently). Plus you need a bunch of extra computers laying around to run the nomad and consul servers before you can even begin with the jobs on it.

The benefit is huge though - you can orchestrate VMs and processes in addition to containers

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

#157
I've been agonizing over devops lately and for me K3s looks like a lighter version of the full API. Another option is NixOS, if we integrate some Kubernetes orchestration features with an autoscaling group of NixOS nodes we get a ton of benefits - version controlled declarative configuration of the hosts enables Dev Prod parity, shared immutable dependencies across containers makes them pull and cold start faster, automatic and easy rebuilds with latest updates...

NixOS is weird and Nix language is super weird but the concept is powerful and the dev community can benefit tremendously from it

If Hashicorp does substantial work to put the pieces together on a full Hashistack deployment to compete with K8s that will be a good option, too.

Also, there's the option of just using cloud stuff instead of an orchestrator. You could use AWS ALB and autoscaling groups to do much of the same thing, and even manage the infrastructure in Typescript or Python with both Pulumi and CDK (or just use TF or CF)

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

#158
post #25

I very much hope to see Hashicorp Nomad getting more traction, as a simpler, yet feature rich solution to probably most use cases in our industry. Pretty interesting to see the adoption of podman and also micro-vms (like fly.io does it), and other Nomad providers that does not nessasarly need to be docker. I know there are great terraform modules out there already, but i wonder if many of Hashicorp's products soon wi…

If anyone wants to test nomad/consul on AWS, and you just want to type 'terraform apply' and then have a consul cluster, nomad cluster, and example app to play around with: https://github.com/groovemonkey/tutorialinux-hashistack/ It's a work in progress but might be helpful to someone!

Thank you!

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

#159
post #95

I feel like it’s a bit like asking what’s next after linux. hard to say because the solution is good enough it’s going to last. There almost has to be a fundamental revolution in computing to overthrow linux at this point. That will come, but it’s a ways out and difficult to see. Most of what we’ll see are different abstractions that will utilize linux under the hood. Same with kubernetes. It’s not that a new kind of…

I agree completely. Look at all of the things that K8s is growing with —- service mesh, etc. The platform is doing more and more for you.

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

#160

I think complete CI/CD+hosting solutions are somewhat likely; open versions of things like AWS lambda or GCP cloud functions. Roll the entire tech stack into a automated service. What most backend devs want is to write code and stick it behind a URI endpoint and make sure it keeps running with networking, auth, security, monitoring, scaling, and reliability taken care of by someone else.

I agree. That’s the idea behind https://www.ibm.com/cloud/blog/ibm-cloud-code-engine-enjoy-y... . (Full disclosure, I work for IBM.)
Post reply on HN