Source: medium.com
Why not use KubernetesCategory: Deployment, Software, Kubernetes, containerization, automation
Many teams are excited to start using Kubernetes as soon as they can, for the most distinct reasons. Some developers want to acquire experience with it, so they can add another highly demanded skill in their resumé.
As defined by the official documentation website, “Kubernetes provides you with a framework to run distributed systems resiliently. It takes care of scaling and failover for your application, provides deployment patterns, and more”.
If your team is very comfortable with Kubernetes and you have a growing amount of containerized applications, it can be worth it to centralize hosting in a single Kubernetes Platform, like Azure Kubernetes Service.
If you are not dealing with many applications, don’t use distributed architecture or don’t have available specialists working in your staff, you won’t be able to avail the advantages Kubernetes offers, basically because it was not made for you.
As defined by the official documentation website, “Kubernetes provides you with a framework to run distributed systems resiliently. It takes care of scaling and failover for your application, provides deployment patterns, and more”.
If your team is very comfortable with Kubernetes and you have a growing amount of containerized applications, it can be worth it to centralize hosting in a single Kubernetes Platform, like Azure Kubernetes Service.
If you are not dealing with many applications, don’t use distributed architecture or don’t have available specialists working in your staff, you won’t be able to avail the advantages Kubernetes offers, basically because it was not made for you.
Related Articles
Community Partners
DevOps Careers