Can docker-compose services/containers span multiple droplets? (In DO, of course)
I’m fine with installing/using docker/docker-compose on a single host (a la my current dev environment). In DO’s IaaS, though, can I achieve something like Kubernetes, where my compose services would run in their own (independently scalable) droplets with networking between them?
Use case: my app has 8 services that have very different demands and usage trends. My ETL extractor will fetch every hour, with a huge spike in network activity and subsequent Translate/Load.
- It would stink if that activity interfered with my React/Express client service(s).
- It would equally stink if I had to keep my whole Droplet scaled to mitigate that load.
^— granular scaling is pretty important there :)