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

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.

A competitor with a simpler API

Isn't Helm already after K8s?

Hopefully we have more iteration on configuring k8s. I'm not convinced we'll so easily go back to managing instances with monoliths.

For some serivces in a kafka-based system i replaced the Postgres some services were using with File-based BoltDB stores or SQLite DBs.

With kafka as the data source every instance was autonomous and would keep itself up to date using the kafka partition offsets.

Went really well, took the DB cluster out of the scaling equasion and offloaded a lot of the cost to the SSD instead of memory or a managed DB Cluster.

If eventual consistency is enough i feel that this is a nice way to handle things.

Twobernetes: Tokyo Drift

Realistically VMs, the toolsets are very mature, and it was an incredible waste to spend so much time getting them to work so well and then dumping all of it for containers. Which has you starting all over at zero again due to the lack of maturity, tooling that is all over the place and requires tons of elbow grease to integrate and make work for your use case.