4 ms·
I value developer productivity over machine performance too, but they're doing the opposite here: developer productivity is not helped with an unnecessary secon
by nailer 10y ago
I value developer productivity over machine performance too, but they're doing the opposite here: developer productivity is not helped with an unnecessary second layer of containment.
With containers on top of VMs, you now have to manage which containers run on which VMs (and the cloud provider worries about physical boxes), with a pure container solution you just spawn containers (and the cloud provider worries about physical boxes)
- jhall1468 10y agoIt is helped if the second layer further automates deployment. I would imagine Netflix is better at understanding its velocity than we are.
- nailer 10y agoYep but Netflix also has a decade of large scale arch wielded to AWS that we don't. They might not be deploying containers on VMs on bare metal because they want to, but because they /have/ to.
- brendangregg 10y agoMind quantifying this overhead you assume containers-on-metal vs VMs will solve?
- nailer 10y agoIt's not assumed, it's widely known VMs have poor IO performance, that one of the main points for containers in the first place. Short ver: GIYF.
- brendangregg 10y agoIf you can't provide numbers, then please talk about what technologies you're assuming are involved that create this overhead.
- tracker1 10y agoI've been developing for a while with a simple Dockerfile in the root of a given project's output... from there I rarely care about it.. in dev, I can mount the app path to the container for dev, and use environment variables set for any other services that are needed. I'm much more productive with Docker for (Windows|Mac) than I've ever been with the likes of vagrant, or whatever bastion of technology that manages VMs... I don't have to think of the VMs, that's generally IT/Infrastructure/DevOps job. yeah, sometimes I wear that hat, but not when I'm coding.