Copy
Microsoft will not support a semi-annual release channel in the forthcoming Windows Server 2022, and users requiring frequent updates will be directed towards Azure Stack HCI (Hyperconverged Infrastructure).
In the old Windows Server world, users could choose between the Long Term Servicing Channel (LTSC) and Semi-Annual Channel (SAC) for installations, with LTSC being essentially the traditional model of a big release every two or three years, and SAC being more the as-a-service model with frequent feature updates to get the latest technology.
Businesses installing Windows Server for general-purpose use would normally use LTSC, which has five years of mainstream support and five years of extended support. The purpose of SAC is for container workloads (host or container image) or scenarios where a VM is short-lived and easily replaced. Limitations of SAC include only 18 months of support per release, a requirement for Software Assurance (a more expensive subscription licens
SQL Server beta for Windows Server Containers terminated with immediate effect theregister.com - get the latest breaking news, showbiz & celebrity photos, sport news & rumours, viral videos and top stories from theregister.com Daily Mail and Mail on Sunday newspapers.
Docker and Windows Server containers
Docker and Kubernetes are the main technologies for deploying containerized applications on cloud infrastructure. They are also directly responsible for the popularity of the microservice architecture in modern software development, where software is broken down into loosely coupled services running independently in their own secure containers.
Docker is the technology used to set up containers and is based on the kernel-based virtualization features built into the Linux kernel, while Kubernetes is the platform used to manage those containers and the applications running in them across multiple hosts (nodes) grouped into networks (clusters).
As the two platforms gained massive popularity for software development and deployment, Microsoft wanted Docker and Kubernetes to be able to run on Windows Server as well, but the Windows kernel lacked some of the process and filesystem isolation features that allowed containers to share the same kernel on