Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

news.ycombinator.com

Post reply on HN
Print view View original

171–176 of 176 posts

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

#171

Post by imhoguy »

c0ffe wrote: post #53

Compiling every dependency into a single WASM binary (including database engine, language runtime, etc) and just deploy and scale it on a serverless platform. No more containers to develop or to deploy, and eventually, no UNIX filesystem around the runtime.

This, WASM, some virtual OS API, and edge deployment (5G), even on user devices. Also some energy efficient blockchain mechanisms and smart contracts may bring us closer to trusted computing. Although that won't happen quickly enough, not next after K8s.

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

#172

Post by airhead969 »

derefr wrote: post #147
airhead969 wrote: post #101

Earlier quoted context omitted.

Serverless? There are always servers. APIs don't exist in a vacuum or scale magically. If you don't understand how to build what's underneath, then you don't understand what's involved and are at the mercy of vendors or someone else.

I have built what was underneath — and then threw it away, because the managed-services vendor built it better, and the OpEx of paying them to manage it was less than the OpEx of paying myself to maintain it.

It absolutely depends on scale. Smaller teams of better staff can sustain cloud infrastructure, especially if grabbing as many internal needs as possible so as to gather critical mass to make it pay for itself.

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

#173

Post by airhead969 »

o-__-o wrote: post #149
derefr wrote: post #147

Earlier quoted context omitted.

I have built what was underneath — and then threw it away, because the managed-services vendor built it better, and the OpEx of paying them to manage it was less than the OpEx of paying myself to maintain it.

This has been the story repeated over the past 30 years

Not thirty years. 10-15. IT was a big industry that everyone did up until about 2010.

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

#174

Post by o-__-o »

airhead969 wrote: post #173
o-__-o wrote: post #149

Earlier quoted context omitted.

This has been the story repeated over the past 30 years

Not thirty years. 10-15. IT was a big industry that everyone did up until about 2010.

I’ve been involved in IT for over 25 years, I’ve seen a lot :)

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

#175

Post by clebio »

rektide wrote: post #122
rektide wrote: post #83

Simpler and monolith (an endlessly re-suggested reply) has it's place, but I see it as impossible for any "simple" solution to ever gain enough mindshare to win. A lot of people suggesting monoliths & hosted services, but they are never going to have the community, the presence of something like Kubernetes, which unites people, which people collaborate over, in the same way we all got to learn & experience & co-devel…

I took a pretty wide swing at what's next in computing. In ops world, I think getting much better at Kubernetes is going to be ongoing for a while. Devs running k3s or microk8s will become more common for local-dev. We'll need better deployment tools, and #GitOps & project like Flux are going to help a lot. Helm does ok, but it could definitely be disrupted. The various code-oriented approaches are ok but honestly un…

I appreciated the read.

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

#176

Post by papito »

airhead969 wrote: post #99
fredsted wrote: post #18

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…

The biggest problems with microservices are the lack of injecting cross-cutting concerns like security, monitoring, circuit breakers, resource metering, alerting, service dependencies, logs, resource isolation, upgrading on-the-fly, migrations, backups/restores of data, and configuration. These all have to be handled. Docker with k8s is awful when it comes to resource metering. Docker is terrible with security and re…

You can do circuit breakers with a monolith. "Release It!" is an excellent book that covers many patterns that do not involve the last resort of distributed systems.
Post reply on HN