No, there's plenty of other use cases for containers. We actually don't use containers for deployments on one of my projects. Instead we use containers for development. Containers are a great way to package software, and that includes middlewares such as a database, cache, etc.
Its much easier to get everyone to install the same thing locally with containers. Its also simpler to start/stop services you need if there's more than one that your app relies on with compose.
No, there's plenty of other use cases for containers. We actually don't use containers for deployments on one of my projects. Instead we use containers for development. Containers are a great way to package software, and that includes middlewares such as a database, cache, etc.
Can you explain? Eg. it's more convenient for you to run Postgres from a Docker image than install it?
Its much easier to get everyone to install the same thing locally with containers. Its also simpler to start/stop services you need if there's more than one that your app relies on with compose.
Yes it is. No overhead of system installs and updating means just changing the version in your docker-compose.yml file.
Another advantage is you could send me your compose file and all I have to do is run it to get the exact same resources you use.