> Can you elaborate why they are correct with this view? What is inherently superior about 1 process per container? At sufficient scale, horizontally scaling i

> Can you elaborate why they are correct with this view? What is inherently superior about 1 process per container? At sufficient scale, horizontally scaling is complicated and involves implementing the things I avoid until I have no choice [Dynamic Service Discovery on a per-process basis, etc.]. I'm mostly deferring to stuff I've read about it since I haven't really worked at companies that are larger than $XX million a year. It generally is things like principle of least privilege, the fact you already have to bite the bullet on managing your service discovery through yet another tool, etc. Personally, I've never dealt with anything larger than 2-3 datacenter locations with a rack of equipment in each. > And why should Docker containers only run on bare metal? That you can just ignore. I really just meant don't do: bare metal -> Spin up Xen VM -> Spin up docker containers Any of these are valid imo: AWS -> Docker Containers Bare metal -> Docker Containers [Insert hosting option X] -> Docker Containers