KUBERNETES AND DOCKER

INTRODUCTION 

    If you are a Devops then you would have definitely heard of kubernetes . The devops world knows enough of what exactly Kubernetes is and where it's used and what is KUBERNETES . Firstly start off by talking about What is The need of kubernetes?  There are lot of myths surrounding communities and there is a lot of confusion people have misunderstand Kubernetes to be a containerization platform well. 

BENEFITS AND DRAWBACK OF CONTAINERS

     First of all containers are good they are amazingly good any container for that matter of fact a Linux container or a docker container or even a rocket container . They all do one thing they package your application and isolated from everything else they isolates the application from the host mainly and this make  the container fast reliable efficient lightweight and scalable . Now hold the thought , yes containers are scalable but then there is a problem that comes with that and this is what is the resultant of the need for KUBERNETES evem though containers are scalable they are not very easily scalable.

      So let's look at it this way you have one container or three containers well it's possible right it's going to a little bit of manual efforts but you can scale it up . But look at the real world scenario then in that case what happens  I mean after scaling up what do you do have to manage those containers  right you have to make sure that they are all working. 

CONTAINERS COULD NOT COMMUNICATE WITH EACH OTHER :

       They are all active and they are not talking to each other because if they are not talking to each other then there is no point of scaling up itself because in that case servers would not be able to handle the roads. If they are not able to talk with each other. So it's really important that they are manageable when they are scaled up.

PROBLEM WITH SCALING UP THE CONTAINER :

  1. CONTAINER COULD NOT COMMUNICATE WITH EACH OTHER :

    It is really tough to scale up container well the answer for that might be known it might not be tough it's preety easy to scale up containers but the problem is what happens after that once you scale up container you will have a lot of problems like the container first for the staff to communicate with each other because there are so many in number and they work together to basically host the service the application and if they are not working together and talking together then the application is not hosted and the scaling up is a waste so that's the number one reason.

2. CONTAINER HAD TO BE DEPLOYED APPROPRIATELY : Containee had to be approprietely and also be manager they have to be deployed appropreitely because you cannot have the container random places you have to plug them in the right place. You  van not hone container in one particular cloud and other one some where else so that would have a lot of complications. 

3.  AURO SCALING WAS NOT POSSIBLE : Autoscaling is never a functionality over here one of the things which is the biggest benefits with cuba neta the problem technically is no auto scaling functionality. There is no concept of that at all and you may ask at this point why do we even need auto scaling so let me explain the need for auto scaling an example - so let's say that you are an e - commerce portal something like an Amazon, or a Flip card and let's say that you have decent amount of try on the work on the weekends you have a spike in traffic's probably you have like 4x or 5x the usual traffic's and in that case what happens is may be your servers are good enough to handle coming in on week days but the request that come on the weekends right from increased traffic's that cannot be serviced by your servers may be it's too much for your servers to handle the load and may by in the short term it's fine may be once or twice you can servive but thing will definitely come a time when your server is start crashing because it cannot handle many request per second or per minutes and of you really want to avoid this problem what do you do you have to scale up and now would you ideally keep scaling up every weekend and scaling down after the weekend . 

4. DISTRIBUTION OF TRAFFIC THAT IS STILL CHALLENGING : Without something that manage your containers I mean you have so many containers but how will the traffic be disappeared load balancing how does that happen you just have container ready half a free container how does does the load balancing happen so all these are questions we should really consider because the containerization is all good and cool ot was much better than VMs. Yes Containerization it was basically a concept wich was sold on the basis of for scaling up , we said that VMs cannot be scaled up easily so we told the use of containers and with container you can easily scale up so that was the whole reason we basically sod continuous with the tagline of fist killing up but in today's world our demand is every more that even the regular. 

SO WHAT IS NEEDED ?

We need something right and that is exactly what Cuban Aires is so Cuba Nettie's is a container management tool, " KUBERNETES IS AN OPEN SOURCE CONTAINER MANAGEMENT TOOL WHICH AUTOMATES CONTAINER, DEPLOYMENT ,COMTAINER(DE) SCALING AND CONTAINER LOAD BALANCING " .

      The benefits with this is that it works brilliantly with all the cloud windows with all your pu lic cloud vendors or your hybrid cloud vendors and it also works on promises so that is one big selling point of few birdies right if I should give more information about KUBERNETES then let me tell you that thus was a GOOGLE DEVELOPED PRODUCT.  It's basically a BRAINCHILD OF GOOGLE and that pretty much is the end of the story for every other competitors out there because the community that GOOGLE brings in along with it is going to be hug or basically the head start that kubernete would get because of being a google brainchild is homogenous and that is one of the reason why Kubanetties is one of the best container management tools in the market period and given that cuba noddy's is a Google product they have written the whole product on go language and of course now google has contributed this whole kuber news project to the CNCF which is nothing but the CLOUD NATIVE COMPUTING FOUNDATION.

      FEATURES OF KUBERNETES :

1. AUTOMATIC BIN PACKING

2. SERVICE DISCOVERY AND LOAD BALANCING

3. STORAGE ORCHESTRATION

4. SELF HEALING

5. BATCH EXECUTION.

   FEW MYTHS ABOUT KUBERNETES :

        Now moving forward here let's talk about few myths surrounding Cuban aries and we are doing this because of lot of people have confusion with respect to what exactly it is so people have this misunderstanding that kubernetes is like docker which is container Ization platform.  Let's me start with what it's not now the first thing is that queue penalties is not to be compared with docker because it's not the right set of parameters which you are comparing them against docker is  a containerization platform and Cuban at ease is a container management platform which means that once you have continued rise your application with the help of docker containers or Linux containers and when you are scaling up these containers to a big number like 50 ,100 that's where Cuban undies would come in when you have like multiple container which need to be managed that's where cuba nadi's can come in and effectively do it you can specify the configuration and cuba leti's would make sure that at all time these conditions are satisfied.

WHAT IS DOCKER ?

    Docker is currently the most popular container platform . Docker appeared on the market at the right time and was open source from the beginning which likely led to its current market domination. 30 % of enterprises currently use docker in their AWs environment and that number continues to grow.

     When most people talk about Docker they are talking about Docker engine, the run time that allowes gou to build and run container. But before you can run a docker container they must be build , starting with a docker file. The docker file defines everything needed to run the Image Including the OS network specifications and file locations, now that you have a docker file , you can build docker image which is the portable , static components that jete run on the docker even has a service called DOCKER HUB, where you can store and share image.