"Do one thing at a time and do it well," has been one of the successful mantras in the Information Technology (IT) sector for quite a long time now. This widely used tenet fits nicely to build and expose Docker containers too, and it is being prescribed as one of the best practices to avail the originally envisaged benefits of the Docker-inspired containerization paradigm. This means that, we must inscribe a single application along with its direct dependencies and libraries inside a Docker container in order to ensure the container's independence, self-sufficiency, horizontal scalability, and maneuverability. Let's see why containers are that important:
- The temporal nature of containers: The container typically lives as long as the application lives and vice versa. However, this has some negative implications for the application data. Applications naturally go through...