4 ms·
Good point. Of course, one of those ways is by charging the same price-per-tenant but increasing the number of tenants-per-server. If multiple companies do this
by chatmasta 12y ago
Good point. Of course, one of those ways is by charging the same price-per-tenant but increasing the number of tenants-per-server. If multiple companies do this, we should expect the price-per-tenant floor to decrease.
- Someone1234 12y agoI liken containers to adding an extra row of seats on a commercial aircraft. Right now the airline (host) operates one aircraft (server) and can fit X number of seats on it (split due to both consumption but also overhead from the seat's depth (hypervisor overhead)). If containers have lower overhead than hypervisors then it would be akin to an airline buying thinner seats and getting an extra row in. However it does remain to be seen how much more efficient containers are over hypervisors, and also how secure they are (there are lot's of unanswered questions on the security front).
- derefr 12y agoI don't think most people are comparing containers to hypervisors (VMs); they're comparing using just VMs to using containers on top of VMs. Especially, they're comparing running one-VM-from-some-IaaS per workload, to running several of those workloads (possibly from multiple tenants) on top of the same VM-from-some-IaaS. If it wasn't insane to run a hypervisor within a hypervisor, this platform war would have started years ago, with Heroku taking AWS VMs and splitting them into tiny Heroku VMs.