We are living in the microservice era, where we have a number of applications to support a business model. But our application success cannot be determined by the features only, it should have a scalable model as well. Otherwise, something like this would happen:-
When we generally talk about the scaling in the microservices, people think that applications that are running inside Kubernetes as containers. Since Kubernetes has its own method of autoscaling using the metrics-server, we don’t have to worry about the scaling of the applications inside it.
Continue reading “Autoscaling in Nomad Cluster”
Container adoption is significantly increasing across various modern use cases, but it’s not a simple plug-and-play. Adopting containers becomes highly complicated, especially when it comes to executing them at scale as most enterprises have only limited skills and capabilities.
Many leading companies believe that Kubernetes is the first step to building scalable modern applications and they are adopting K8s to overcome container adoption barriers.
Spotify is one of these. Leveraging Kubernetes benefits, Spotify has observed significant cost-saving values as described in this case study. It has seen 2-3x CPU utilization by using the orchestration capabilities of K8s, resulting in better spend optimization.
Continue reading “A Comparison Between Various Container Orchestration Services! (ECS vs Kubernetes)”
Whenever someone says orchestration for microservices, the first thing that usually comes to mind is Kubernetes. I believe that’s normal. I used to think the same but then I came across an interesting scenario that changed the way I used to think about microservice orchestration completely.
Usually, people think microservices mean containers, hence they build their application in a cloud-native approach so that it can easily run on any platform using the containerized approach. Well, I agree that containerization is a decent way of designing a cloud-native application especially when we integrate it with orchestrators like Kubernetes or OpenShift. It takes away a lot of overhead from us like:- scaling, failover, deployment, etc but it doesn’t imply that microservices can only be managed inside a containerized ecosystem. Microservice is an ideology or mindset for designing the application and containerization is a power-up that supports the ideology.
Continue reading “Running Non-containerized Microservices”