Docker vs. Hyper-V

You are going to be able to find the most resources and examples using Docker whenever you are working with a container orchestration software like Kubernetes. There will always some entropy when you run in a container, a containerized application will never be as purely performant as an app running directly on the OS. However, in most scenarios this loss will be negligible to the time saved in deployment, monitoring, etc.

Because Hyper-V is a Microsoft product and based on Windows OS, creating virtual Windows servers and clients are easy. When we want to test our group policies it it best to do it on hyper-v environment then implement to production clients. The same goes with operating system quality and features updates as well as operating system upgrades.

• Packaging of application to limit the space occupied
• Ease of running the application
• Provide multiple ways to handle the application issues and integration of different components like pipeline, ansible, terraform etc

• Easy to use GUI - very easy for someone with sufficient Windows experience - not necessarily a system administrator.
• Provisioning VMs with different OSes - we mostly rely on different flavors of Windows Server, but having a few *nix distributions was not that difficult.
• Managing virtual networks - we usually have 1 or 2 VLANs for our business purposes, but we are happy with the outcomes.

• Docker hub image retention policy can be relaxed
• Docker hub policies can be more developer friendly
• Docker CLI help section can be improved
• Image and container storage (local) management can be optimized

• The only issue I have with Hyper-V is I am unable to use Veeam on my Windows 2016 Server to backup my FreeBSD HAProxy VM.
• There is some sort of checkpoint issue that I have been unable to figure out, but it works just fine on my Windows 2012 Servers. I do believe this is a Microsoft issue and not a Veeam issue though.
• Another thing that could be useful that Hyper-V does not have would be some sort of GUI that shows the status of all the VM's on a given server to help us manage them easier and know what is going on. However, I do have Zabbix for this and that does a good job at monitoring all my servers.

Cheap and easy is the name of the game. It has great support, it doesn't require additional licenses, it works the same if it is a cluster or stand-alone, and all the servers can be centrally managed from a system center virtual machine manager server, even when located at remote sites.

Very easy to use, great tutorials, documentation and cheat sheets out there to help you become a Docker Wiz

It is very easy to configure new virtual machines and manage them. But you have to use different interfaces to perform various tasks. Especially as soon as it comes to clustering you have to use at least two different interfaces (Hyper-V Manager and Failover-Cluster Manager) to perform all necessary tasks. The newly released Windows Admin Center is a way into the right direction to get all management tasks into one single interface.

Haven't seen any outages, fatal/unrecoverable errors in my usage so far. Enough said.

In the past 2 years our Hyper-V servers have only had a handful of instances where the VM's on them were unreachable and the physical Hyper-V server had to be restarted. One time this was due to a RAM issue with the physical box and was resolved when we stopped using dynamic memory in Hyper-V. The other times were after updates were installed and the physical box was not restarted after the updates were installed.

Docker Desktop. The CPU high usage is a known issue. Needs fixing. Otherwise, it is great overall. Would not use anything else still.

Hyper-V itself works quickly and rarely gave performance issues but this can be more attributed to the physical server specifications that the actual Hyper-V software in my opinion as Hyper-V technically just utilizes config files such as xml, and a data drive file (VHD, VHDX, etc) to perform its' duties.

Hyper-V is greatly supported by techs around the world. There are tons of forums, help websites and individuals ready to answer questions. I've never needed to contact Microsoft for help...because help is so easy to find out there. Do a search online for anything related to Hyper-V and you will certainly find an article with spelled out steps on how to do what you are looking to do.

We had in person training from a third party and while it was very in depth it was at a beginner's level and by the time we received the training we had advanced past this level so it was monotonous and redundant at that point. It was good training though and would have provided a solid foundation for learning the rest of Hyper-V had I had it from the beginning.

The training was easy to read and find. There were good examples in the training and it is plentiful if you use third party resources also. It is not perfect as sometimes you may have a specific question and have to spend time learning or in the rare case you get an error you might have to research that error code which could have multiple causes.

initial configuration of hyper-v is intuitive to anyone familiar with windows and roles for basic items like single server deployments, storage and basic networking. the majority of the problems were with implementing advanced features like high availability and more complex networking. There is a lot of documentation on how to do it but it is not seamless, even to experienced virtualization professionals.

The reason why we are still using Docker right now is due to that is the best among its peers and suits our needs the best. However, the trend we foresee for the future might indicate Amazon lambda could potentially fit our needs to code enviornmentless in the near future.

While many have additional features or lower overhead the ease of use and low-cost licensing make Hyper-V our preferred choice for most clients. And because we are mostly a Microsoft shop and it is built on Windows when we need to troubleshoot the hypervisor itself we already have the needed skillset with very little additional training and no need to learn an additional OS like Linux.

It is the only tool in our toolset that has not [had] any issues so far. That is really a mark of reliability, and it's a testimony to how well the product is made, and a tool that does its job well is a tool well worth having. It is the base tool that I would say any organisation must have if they do scalable deployment.

Nothing is perfect but Hyper-V does a great job of showing the necessary data to users to ensure that there is enough resources to perform essential functions. You can also select what fields show on the management console which is helpful for a quick glance. There are notifications that can be set up and if things go unnoticed and a Hyper-V server runs out of a resource it will safely and quickly shut down the VM's it needs to in order to ensure no Hardware failure or unnecessary data loss.

• Reduces the number of virtual machine which impacted our quarterly billing
• Using docker with proxy we run multiple application on same port on same host.
• impact on billing is we have to provide docker training to the people who are working on it.

• Hyper-V has provided for an extremely cost-effective virtual environment with disaster recovery. For the size of our business, it's all we need to ensure our desired level of continuity of services and protection against hardware failures.
• Since we are a Windows shop, deploying Hyper-V means we don't have the added cost of a hypervisor, since it's included in the cost of the Windows Server license. It's all we needed to achieve our goal of running all our virtual machines on a single server with another, less expensive server on tap for replication and failover.
• We wanted easy deployment and management with disaster recovery while having the ability to leverage our years of Windows SysAdmin experience. Hyper-V fit the bill.