[drej]

It’s always nice when there is some sort of consensus in the industry, however, there is one thing I worry about.

Now that there is a usable solution for complex orchestration, many newcomers will consider it the goto solution, regardless of scale. You need nginx and some python scripts? Kubernetes! You have 100 daily visitors? Kubernetes!

It’s not really their fault, it’s just a sad consequence of a convenient cloud solution.

[jrs95]

Part of this is also people jumping to microservices when they really have no need for them. When you have less than 5 developers and very little traffic...it's just absurd. But people are doing it anyways. Because "monoliths" are "bad". And honestly, I wouldn't be surprised if a lot of these microservice architectures end up totally botched and creating a ton of headaches without delivering much benefit.

[netheril96]

Another part is claiming Kubernetes experiences on your resume.

[aphextron]

Is that really a problem though? The entire history of software development is just building on one layer of abstraction over another. Is it sad that people these days don't write their own web server for new projects?

[jrs95]

A lot of people are only adopting Kubernetes because they think they will benefit from Dockerized microservices when they don't even have most of the problems that solves. There's a lot of extra development and operations effort going into things for no real reason other than mistaking this technology for a silver bullet.

[kerneltime]

The point is not to rewrite from scratch.. the point is that your judgement to use a piece of technology should come from your understanding of the problem and direction and not based on what is a legitimately a hot topic in a context that does not apply to you.. in other words do not let google search results be the bar you meet in solving your problems..