Website under construction

Figure 3-7:
Windows Server 2016 containers and Hyper-V containers on the same physical box 
As shown in the illustration, one physical host can offer a mix of Hyper-V containers, VMs, and 
Windows Server containers. With two potential container options, the question is when to use either 
Windows Server containers or Hyper-V containers for developing and deploying the applications. The 
deciding criteria come when you identify scale and hardware-assisted isolation requirements for the 
application or customer using the containers. 
For example, if you require greater scale, Windows Server containers are the best option because you 
can achieve this goal. However, if you require the isolation benefits of hardware-assisted virtualization, 
and scale is not as important, Hyper-V containers are the best option to use. 
When looking at either type of containers, it is important to understand the development lifecycle. 
From a developer’s perspective, the tools they are familiar with, such as Visual Studio, will allow them 
to write and deploy applications directly into containers. The tools will also give them the ability to 
describe what core functionality is required in the underlying OS, what libraries can be shared 
between applications, or what libraries are to be dedicated for a container. Figure 3-8 highlights 
the dependencies and runtime mode of the containers. 
Figure 3-8:
Containers and dependencies 

---

101 
CHAPTER 3 | Application platform 
No matter which technology you choose, the application you deploy into a container is compatible 
between both technologies. This essentially means that a developer can easily build the application 
in a container hosted on Windows Server containers and move it to a Hyper-V container with no 
changes required. This gives great flexibility, especially if the requirements of scale or isolation change 
after the initial planning of the system.