Native Docker DNS

One of the biggest benefits of running a containerized infrastructure is the ability to quickly and effortlessly scale your workloads horizontally. Having more than one machine in a cluster with a shared overlay network between them means that you can have many containers running across fleets of servers.

As we saw in the previous exercise, Docker gives us the power to allow containers to directly talk to other containers in a cluster through the various network drivers that Docker provides, such as bridge, macvlan, and overlay drivers. In the previous example, we leveraged Docker bridge networking to allow containers to talk to each other by their respective IP addresses. However, when your containers are deployed on real servers, you can't normally rely on containers having consistent IP addresses that they can use to talk to each other. Every time a new container instance terminates or respawns, Docker will give that container a new IP address.

Similar...