The following diagram shows the typical architecture of a web application. We have the load balancer tier that receives traffic from the Internet and then the traffic, which is typically composed of user requests, is relayed to a farm of web application servers in a load-balanced fashion.
Depending on the nature of the request, some states will be grabbed by the web application from the persistent storage tier, similar to Database Servers:
As we can see in the preceding diagram, each tier is run inside a Docker container on top of Docker Hosts. With this layout for each component, we can take advantage of Docker's uniform way of deploying load balancers, applications, and databases, as we did in Chapter 2, Configuring Docker with Chef, and Chapter 7, Load Balancing. However, in addition to the Docker daemons in each Docker host, we need supporting infrastructure to manage and observe the whole stack of our web architecture in a scalable fashion. On the...