We deploy lots of small apps for internal usage, and we deploy those with docker compose. If your app fits on a single VM, and you don't have k8s, this is incr

We deploy lots of small apps for internal usage, and we deploy those with docker compose. If your app fits on a single VM, and you don't have k8s, this is incredibly straightforward. It's even "easier" to just use kubernetes to deploy something - but that's if you already have kubernetes! As my org is adopting k8s we are favoring that over docker-compose where applicable, but there's a huge complexity gap between docker-compose and this isn't an overnight transition. I guess you could view docker-compose as a much more accessible stopgap as your team learns how to run the more complex orchestration strategies, or a preferred solution if you have a small number of VMs you want to explicitly configure to run specific services on (where you don't need the scheduler etc).