Hacker News Reader

When they pulled apart all those kubernetes clusters they probably found a single fat computer would run their entire workload.

“Hey, look under all that DevOps cloud infrastructure! There’s some business logic! It’s been squashed flat by the weight of all the containers and orchestration and serverless functions and observability and IAM.”

View on HN

I don't think this is a fair comment. This happens sometimes but usually people go with Kubernetes because they really do need its power and scalability. Also, any technology can be misused and abused. It's not the technology's fault. It's the people who misuse the technology's fault ().

() Even here, a lot of it comes from ignorance and human nature. 99.9% of people do not set out to fail. They usually do the best they can and sometimes they make mistakes.

The pointy is most organisations reach for container orchestration before they attempt to build fast software on a single machine.

My company has more microservices than paying customers.

Given that seemingly half the devs and orgs are antithetical to writing performant software, or optimising anything I somewhat doubt that’s going to happen anytime soon. As much as I’d like that to happen.

Performance isn’t the only reason to use container orchestration tools: they’re handy for just application lifecycle management.

Reply on news.ycombinator.com