Why would anyone choose Docker over fat binaries?
* If my colleagues don&#x27;t have to understand how do deploy applications properly, their work is simplified greatly. If I can just take their work, put it in a container, no matter the language or style, my work is greatly simplified. I don&#x27;t have to worry about how to handle crashes, infinite loops, or other bad code they write.<p>* We have a whole lot of HTTP services in a range of languages. Managing them all with fat binaries would be a chore - the author would have to give me a way to set port and listen address, and I have to keep track of every way to set a port. With a net namespace and clever iptables routing, docker can do that for me.<p>* sometimes, I have to deploy and insecure app. Usually, it&#x27;s a badly configured memcache or similar. With net namespaces, I can make sure only a certain server has access to that service, and that the service cannot ruin my host server.<p>* Its possible for me to namespace everything myself with unshare(1) and &quot;ip netns&quot;  and cgroups and chroot and iptables... but that would consume all my available time.  Docker can do that for me.<p>* When you reach more then 20 or so services to keep track of, you need tools to help you out.<p>* load balancing. Luckily, I don&#x27;t have to deal with extreme network loads which would require hand-made solutions, but just pushing up that number a little to do ad-hoc load balance makes things a lot easier.