| |
|
Traditional vs Docker
Well here we have put some example for Traditional Deployment vs Docker Deployment. And to understand this we will take an example for traditional deployment first. Let's look that we have a web application which was created in one of the particular Python version and we have used some libraries or we can say some third party libraries. And to run that application on any of new server we need to Python version, the required libraries, and the environment configuration which need to be manually installed on the new server. And this process need to be run on each and every server. And this process can be laborious and prone to errors.
And here Docker have changed some scenrio and quick can do all this stuff. Here developers can use Docker to create a container image which may contains application code together with all of its dependencies and that dependecies are( particular third party libraries and pariculare Python version) and the setups that every new system may require in traditional deployment. And once that image is created we can quickly installed on any host that has the docker installed.
And by providing the container with an isoldated environment the Docker engine prevents problems with other programs or libraries on the host system. And this will saves developers time and there works because this will makes deployment so simpler but also ensures consistent behavior across all settings. | |
|
|
|
|