โฌ๏ธ Main Note
https://docs.google.com/document/d/1sZMHy4FLlMlizJLtX0S6ww5C3U3ftPuKN5LDTaqVAdc/edit
: Connecting Frontend and Backend Server
: Docker manager
Docker= container
Docker-compose = Bunch of containers
Docker-Swarm = Container Orchestration
Mesos, Docker-Swarm, Kubernetes, etc
โค What container orchestration does is something like re-building dead containers
Each computers are connected with network, so docker orchestrations manage docker and its traffics.
โค At this point, Kubernetes tells which docker is dead and which computer needs more docker.
Because we don't operate docker in only one computer.
We distribute multiple dockers in diverse computers, so we should manage them.
Problems while deploying
: Let's suppose that we made a backend-API and did docker-compose up
Infront of backend, DNS exists. If I updated createBoard API, we should re-deploy createBoard API again.
To do so, we should do docker-compose stop
to stop the original createBoard API, and do docker-compose up
to operate the updated API.
But at this point, when we do docker-compose down
, the service will stop.
So to deplpoy without any breakpoints, we need Kubernetes.
A single computer is called Node, and bunch of nodes are called Cluster.
Master computer : Master Node
Other computers : Worker Node
POD contains docker container so that docker can be operated.
โค Inserting one docker per one POD is regular. But this isnt's a rule.
If dependency between diverse dockers are strong, then those dockers can be in a group of one POD.
Cluster โ Node โ POD โ Container
์.์ฐ.์ .๊ฑฐ.๊ฐ.๋ค.์.ํ.ํ.ํ Yolo