Good article that discusses something I have not touched in years, simply because of a lot of the drawbacks he talks about. Also is a wonderful sales pitch, som

Good article that discusses something I have not touched in years, simply because of a lot of the drawbacks he talks about. Also is a wonderful sales pitch, someone has been practicing. In the virtualization world we argue often about how to do things “right” and what the “industry standards” are. I started a series a while back to help define and explain virtualization and various related topics. Specifically I even talk about this subject ( http://ewams.net/?date=2012/01/04&view=The_4_Types_of_Virtualization#b http://ewams.net/?date=2012/01/04&view=The_4_Types_of_Virtua... ). The main problem with saying VM’s are “no longer the future” is they are mainstream and have been for a while, so they probably are not not cool enough for hackers but they are not going anywhere fast. Containers have a place and full blown virtual machines have a place. The trick is finding which one will benefit your organization and for which purpose. Most likely both can work depending on the requirements. The other topic I notice that is usually overlooked when talking about virtualization is the actual OS. Here in this article it discusses mostly Red Hat based distro’s. Some organizations strictly use OSX, others Ubuntu, others RHEL, while others use some sort of mix. Each is different and even for closely related like Fedora and RHEL, what works on one may not work on another without hacking it or some other black magic. (Or it may work just fine, you know how it goes). The other point of the OS talk is where is Windows? We can pretend to be ostriches but Windows server is out there and in large numbers. Lots of people make lots of money writing applications that work strictly on Windows (same for *nix). Just do not forget about it. If we move forward with containers, and since the topic has come up at least twice in the last 6 months, let’s start to see recommendations on how to run containers. How to pick workloads. How to optimize applications and kernels to run them. What kind of hardware to run them on. How to code for them. Etc.