This content originally appeared on DEV Community and was authored by DevPool
Before I talk about Docker, let me give you a common problem in software development that developers used to have.
Let’s say a developer who just finished developing and testing a new feature worked fine on their environment. But when the same code reached production, suddenly, the system crashed. One of the possible reasons is that the development and production environments are different from each other.
Before Docker, developers would use Virtual Machine to create a virtual environment to ensure that the developer’s station matches the production server. The problem with that is now we are wasting resources and not able to usefully our Disk Space, Memory, Processing Power, and more.
Docker is different to set it up and use. It is installed directly onto the user’s machine, and developers can install multiple containers responsible for their microservice. As you can see, we didn’t have to allocate any of the resources for our containers, and it will automatically use what it needs for the need of an application.
We can now have our code base with all the tools running equally on any environment with that setup.
In conclusion, if you were to start to work on the project, I would recommend using Docker as it will remove the environmental issues.
For more tips, subscribe to my channel and don't miss the future topics.
YouTube - DevPool
This content originally appeared on DEV Community and was authored by DevPool
DevPool | Sciencx (2021-06-26T16:49:29+00:00) Why Docker?. Retrieved from https://www.scien.cx/2021/06/26/why-docker/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.