Docker/Kubernetes has obviously cut into the market that was once dominated by VMware. There are cases where a VM is able to meet requirements that a Container cannot. This often boils down to requirements for isolation or security or long-term support. If you're in charge of a department's cloud infrastructure, I'd recommend that you weigh costs and benefits carefully and be ready to use both VMs and containers. You can be careful with how much money you pay VMware or spend on dedicated equipment for VMs. You can use docker for those short-lived jobs that benefit from the caching of image layers and the fast start up times. And you can use VMs where you can keep an important services running uninterrupted even if you migrate them to a different machine or even location.
I'm not sure where to start with this, you seem to be conflating VMs and containers with on premise and cloud. When you got to container start times, oh boy... I have to help dispel this Inception-grade confusion that is hanging over Docker and K8s
A container is just a sandboxed process. That is all. There is _nothing_ else to it. Any other attribute credited to containers is a big lie. They're conventions that can be applied to any not-sandboxed process. Containers are not stateless, you're simply ru
Future? (Score:5, Interesting)
Re:Future? (Score:3)
Docker/Kubernetes has obviously cut into the market that was once dominated by VMware. There are cases where a VM is able to meet requirements that a Container cannot. This often boils down to requirements for isolation or security or long-term support.
If you're in charge of a department's cloud infrastructure, I'd recommend that you weigh costs and benefits carefully and be ready to use both VMs and containers. You can be careful with how much money you pay VMware or spend on dedicated equipment for VMs. You can use docker for those short-lived jobs that benefit from the caching of image layers and the fast start up times. And you can use VMs where you can keep an important services running uninterrupted even if you migrate them to a different machine or even location.
Re: Future? (Score:2)
I'm not sure where to start with this, you seem to be conflating VMs and containers with on premise and cloud. When you got to container start times, oh boy... I have to help dispel this Inception-grade confusion that is hanging over Docker and K8s
A container is just a sandboxed process. That is all. There is _nothing_ else to it. Any other attribute credited to containers is a big lie. They're conventions that can be applied to any not-sandboxed process. Containers are not stateless, you're simply ru