Uploaded December 2015 | Updated September 2026, 1 week ago
Now that we've registered all of our docker services, load balancing between them is easy.
VIDEO 1: 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: 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.
VIDEO 3: 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
THIS VIDEO: 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
NEXT VIDEO: youtu.be/4215szNHlC4
- 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.
-~-~~-~~~-~~-~-
Also watch: "Responsive Design Tutorial - Tips for making web sites look great on any device"
youtube.com/watch?v=fgOO9YUFlGI
-~-~~-~~~-~~-~-
Now that we've registered all of our docker services, load balancing between them is easy.
VIDEO 1: 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: 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.
VIDEO 3: 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
THIS VIDEO: 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
NEXT VIDEO: youtu.be/4215szNHlC4
- 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.
-~-~~-~~~-~~-~-
Also watch: "Responsive Design Tutorial - Tips for making web sites look great on any device"
youtube.com/watch?v=fgOO9YUFlGI
-~-~~-~~~-~~-~-
