Login / Register

Scaling Docker #3 - Docker Service Registration with Etcd & Flannel

Thanks! Share it with your friends!


You disliked this video. Thanks for the feedback!

Sorry, only registred users can create playlists.

Added by Admin in Learning


2 of the biggest problems to solve with Docker infrastructure are service registration & service discovery. In this video, we'll cover the more complicated piece, which is service registration.

Every Docker container needs to register itself as a web service that can be consumed or load balanced by other containers.

VIDEO 1: https://youtu.be/wxUxtflalE4
- Cluster computing - CoreOS is our solution here. CoreOS allows us to make an expandable cluster of computers so we can add more computers should our application need more power to scale. CoreOS also allows us to run services on any machine in the cluster and they can all communicate with each other.

VIDEO 2: https://youtu.be/top0MlcKSw4
- Scheduling: we shouldn't manually choose which app runs on which machine - this idea doesn't work at scale. Fleet will be our scheduler that decides where our apps/services run. If a CoreOS machine goes down, fleet will reschedule any services that it was running onto a new machine.

THIS VIDEO: https://youtu.be/1zJ8FfC-gmU
- Service Registration
Since we never know what ip address or port a service will be running on, we need to register that service so other services can find it and communicate with it. We'll use Etcd and Flannel for this

VIDEO 4: https://youtu.be/R39VRocQtrQ
- Service Discovery:
Now that services have registered, we can discover them and load balance between them with a generic docker nginx container

- Public DNS: Once the app is working, we need a fixed way for the outside world to access it. We'll use Nginx and Confd for this. Confd will watch Etcd for service registration and when services come/go, it will build a new configuration file for Nginx and reload Nginx.

Post your comment


Be the first to comment