Peace to you all , Here is the Link to my previous blogs, Where I have posted about my journey with DevOps.
This is Day 11 of documenting my DevOps journey .
This blog focuses on what is container orchestration.
On hosting on cloud, the images we build , will be sent to the cloud provider we use . The cloud provider will have a container runtime engine , where containers are created with images.
For each and every commit we do to the application we have , a CI/CD process should be running ,So that there is no downtime and everything is deployed continuously.
We will focus on CI/CD in the upcoming blogs.
Running number of instances of a single container
Once CI/CD builds successfully , the image will be updated and that updated image will be used to create the updated container .
As the number of users who access the project increases, a single container will not be sufficient for hosting , since performance can get very less and even sometimes the container can crash.
So In order to solve this problem, multiple instances of the same container is used . This way we can scale up, if we need more and scale down, if we need less.
Handling multiple instances of different containers
As the users of the application increases, we have to have more containers and also there should be containers for backend and database as well .
Imagine , having a full stack web application , with frontend, backend and a database.
Number of containers for each service should be allocated as per need . They should be constantly monitored and changed if it fails , scale up if the performance gets down, scale down if usage is less and etc.
Container Orchestration comes to place in order to solve these problems.
Most of us know ,Orchestration as in music , But what is Orchestration in computing means ?
In short , It is the management of applications in an automated way.
So ,Container orchestration literally means , management of containers in an automated way.
As the workload increases on a project/container , we tend to increase our containers . The increase in the number of containers makes it tedious for humans to monitor each and every container , and that’s where a container Orchestration tool comes to place.
Not only that, but when a container fails , we have to manually allocate another container which can be done by constant monitoring, there comes container orchestration tools which does it automatically.
Different container Orchestration tools
There are many different container orchestration tools which can be used to handle containers.
Some of the well known are Kubernetes, Docker Swarm and Openshift.
Kubernetes is the most widely used container orchestration tool . In the upcoming blogs , we are about to start Kubernetes and how it is used.
What have we done
We looked at why a container orchestration tool is important , what is the role of a container orchestration tool and what are different container orchestration tools available in the market.
See you Tomorrow
Okay . So hold on, stay with me as we get to know Kubernetes and how it is used.
Okay Then , Will get back Tomorrow with more!
Peace be upon you!