Из ленты dev.to devops — кратко, чтобы не потерять.
A few months ago, while discussing the architecture for a new client project, a junior engineer on the team asked, “Of course we’ll use Kubernetes, right?” At that moment, I thought to myself, “No, of course we won’t!” because my 20 years of experience have taught me that not every shiny technology is a panacea. Kubernetes is undoubtedly a powerful tool, but it’s not suitable for every project, every budget, or every team. This question actually reflects a common misconception I encounter in the industry: the idea that every new project, regardless of its complexity, should start with the most popular and “coolest” technology. However, for me, architecture is about balancing a project’s real needs, the team’s capabilities, and the budget; one should not underestimate the power of simple so
Полный текст и контекст у первоисточника: https://dev.to/merbayerp/not-everyone-needs-kubernetes-3m32