I was like that and ignored Docker for a number of years. The app I'm working on has one database, one queue, one API server and one web front end. Some of thes

I was like that and ignored Docker for a number of years. The app I'm working on has one database, one queue, one API server and one web front end. Some of these will scale when in production, but for eveloperment it's quite simple. I used to just run them at the command line and get on with development. But using docker has been an eye-opener. I can now get my front end developer to have a fully working database, queue, API server running with a simple `npm run docker`. They are free to develop the UI without having to worry about the underlying stack. I am free to change that stack without having to worry about telling them what commands to run on their laptop to get it up to date. As we add more services, such as email sending, image processing, video compression, it wont require anything special to configure from the front end perspective. We're now moving it into the cloud and are now seeing the benefits of Kubernetes with our docker containers to deploy, have a blue/green deployment, not worry so much about what the servers are doing but focusing on deployments. This is very clever stuff and will reduce our hosting cost without having to duplicate infrastructure. So yeah, I didn't get docker for a long time. It does depend on the types of apps your building though. My use case fits it perfectly.