When it comes to technology, the only constant is change. We've all heard exaggerated stories about brand-new systems...
that became outdated before they were even plugged in. Although stories of rapid technology obsolescence have traditionally revolved around hardware components, there is no such thing as static technology.
Everything in IT evolves, even the related vocabulary. Take the evolution of the hyper-converged infrastructure definition, for example.
In the recent past, the hyper-converged infrastructure definition referred to something very specific. Hyper-converged systems consisted of a series of nodes containing performance-matched compute, storage and virtualization resources. These nodes were designed for modular scalability and were bundled with a hypervisor and various management tools.
The main advantage to this type of hyper-convergence is that the hardware and software have all been tested and certified to work together. Furthermore, because the nodes are self-contained, there is a single point of contact for technical support. This eliminates the problem of vendor finger-pointing.
However, the hyper-converged infrastructure definition is changing. Whereas the term once referred to self-contained nodes that were tightly integrated with an enterprise hypervisor, it has evolved to include a number of other technologies.
Some vendors have begun referring to certain reference architectures as being for hyper-converged systems. Previously, reference architectures could be used to build converged systems, which could be similar to hyper-converged systems, but almost no one referred to a reference architecture as being hyper-converged. These types of reference architectures defined hardware components and configuration settings, but lacked the deep software integration that is a staple of hyper-converged systems.
Today, there are also software-only hyper-converged products. The Windows Server 2016 Storage Spaces Direct feature, for example, allows for hyper-converged system-like behavior, but is software-only.
The lines have blurred between converged systems and hyper-converged systems. A converged or hyper-converged infrastructure definition means different things to different people. In the context of Storage Spaces Direct, for example, a hyper-converged infrastructure uses internal, node-level storage, while a converged infrastructure links failover cluster nodes to a shared storage volume that is based on Storage Spaces Direct.
E-Handbook: Top uses for hyper-converged technology
Should you choose converged or hyper-converged infrastructure?
Explore differences among hyper-converged offerings
Dig Deeper on Hyper-Converged Infrastructure Implementation
Related Q&A from Brien Posey
Setting up Office 365 generally involves multiple devices. With nonpersistent VDI, the rules of the game change for IT admins.continue reading
Much has been said about the inability to scale storage separately from other resources in a hyper-converged system, but are there any advantages to ...continue reading
Licensing Office 365 for VDI deployments is not simple. The requirements change depending on the deployment type. Microsoft RDS, for example, ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.