4 ms·
Years ago, the hypervisor was nailed by VmWare, while Xen was a joke. Then the AWS/Google/DO/other worked hard on the hypervisor and they released infra that w
by user5994461 10y ago
Years ago, the hypervisor was nailed by VmWare, while Xen was a joke.
Then the AWS/Google/DO/other worked hard on the hypervisor and they released infra that worked and is entreprisey ready... but it's a complete offering, you cannot just get their Xen package and put it on your systems (assuming it's even powered by Xen anymore), you have to use their platforms.
Docker is unstable now.
AWS/Google/RedHat/CoreOS are all working pretty hard to pull out an offering for containers that works and is entreprisey ready. It's gonna take years to be production ready enough for critical systems, and it's as likely to reuse Docker as to replace it with their own more stable tech.
The point is, docker is nowhere near ready in its current state. Wait and see.
- majewsky 10y agoIIRC it's pretty likely that AWS runs on Xen, or at least did so at some point in the past. There was some striking correlation between Xen security advisories and mass reboots of AWS nodes.
- seanp2k2 10y agoAFAIK AWS runs patched Xen. They seem to have built quite a bit on top though, and e.g. Have re-written lots of the network stack. This also seems to be why their networking stuff would break or be very flaky regularly as of a few years ago.
- jacques_chester 10y agoI'd argue, with the benefit of infinite bias, that an enterprise offering for containers already exists: Cloud Foundry. Running in production for years. The commercial distributions (by Pivotal, IBM, SAP most notably) are licensed to gigabuck corporations worldwide. That said, other companies and opensource projects will absolutely move towards the value line. There's no money or glory in building blocks. Disclosure: I work for Pivotal, the major contributor of engineering to Cloud Foundry.