Azure Stack HCI: Hyper-converged, though not as Azure as you’d think

Microsoft has launched Azure Stack HCI, that provides hyper-converged infrastructure (HCI) in that virtualised environments can run on internal hardware with simplified entrance to a Azure cloud for hybrid cloud operations.

The branding creates it demeanour like an further to a existent Azure Stack environment, that allows internal datacentres to run Azure program on-site and to advantage from Azure cloud services, though it is a rebranding and harmony has a limitations.

Azure Stack HCI provides hyper-converged infrastructure functionality with a two-node smallest pattern and virtualisation around a Hyper-V hypervisor, that runs practical machines with virtualised storage from Storage Spaces Direct, aka S2D, a software-defined storage underline that originated in Windows Server 2016.

Azure Stack HCI was formerly called Windows Server Software Defined (WSSD), so a pierce to apropos Azure Stack HCI is a rebranding move.

What might distortion behind it is that WSSD is not amply widely deployed to figure in IDC’s numbers for hyper-converged infrastructure.

According to a many new figures, from Oct 2018, HCI from Nutanix and VMware (ESX, vSAN, NSX, vCenter) any take around 34% of a market, while those from Dell EMC (VxRails), Cisco and HPE any form around 5%.

WSSD has been buried in a “others” category, that accounts for about 16% of a market. Microsoft Azure, meanwhile, is resolutely placed as series dual in a open cloud marketplace with – according to Microsoft – income expansion of around 90% each year.

WSSD connected to a Azure open cloud in flattering most a same approach as other Windows network solutions, around a practical private network (VPN), or improved still with Microsoft’s ExpressRoute, that provides dedicated Azure connectivity around an MPLS-enabled VPN connection.

With Azure Stack HCI, business can quit practical machines from on-premise to cloud, or to set a Microsoft cloud as a aim for internal backup. Azure does also offer this functionality to other hyper-convergence platforms, however.

Azure Stack HCI is docile around a Azure authentication service, like any other Windows Server.

Azure Stack HCI doesn’t seem to have a good understanding of reciprocity to other Azure products, however. If an focus has been created to interface with Azure services, it won’t duty on Azure Stack HCI, nonetheless it will with Azure Stack. 

Another disproportion between Azure Stack on-site or Azure in a cloud and Azure Stack HCI is a middle of consumption.

The initial dual are billed according to apportion of use resources used per month. Azure Stack HCI is bought discretely with additional options such as a SDN Azure Network Adapter or Azure Security Center monitoring modules.  

We should note, in this regard, that Azure Stack is generally granted pre-installed on authorized servers, while Azure Stack HCI is deployable by a patron on a far-reaching operation of server hardware.