Since we are moving from a local Docker Engine-Community Swarm deployment on a local developer machine to a Docker Enterprise Cluster deployment, we can take advantage of Docker Enterprise's Interlock 2 layer 7 routing feature. In addition to layer 7 routing, we can also use Interlock 2 for our TLS termination, as shown in the following diagram. Therefore, by using this feature in our application, we will replace the reverse_proxy service we used for our local deployment stack.
To describe how this feature works for our sample application, we can follow the inbound traffic from a remote computer, starting with the wildcard DNS entry, which resolves the atsea.mydoamin.com URL on port 443 on our external ...
