What is composable infrastructure? If you’ve read any industry blogs or articles lately, chances are you’ve come across the term. So what exactly is "composability?" Why do we need it? Is this the same thing as "converged infrastructure?"
If you listen to some vendors, there is no need for on-premises infrastructure anymore. Everything that you want to do you, you can do in the cloud. All you need to do is rent the infrastructure--no capital expenditure cost, just ongoing usage-based operational expenditures. The reality isn’t quite that straightforward.
It happens with almost any new technological advance: Suddenly, every product is in the cloud, or mobile-based, or big data-ready—whether they really are or not. The same thing is happening with the word “converged.”
In recent years there has been a trend toward increasing workload density. A decade and a half ago, you would generally run one workload on one hardware chassis. While it was certainly possible to install different products, such as Exchange Server or SQL Server, on the same server running Windows 2000, administrators would generally avoid doing so unless they were deploying a Small Business Server-type solution. If you were doing enterprise IT on Windows systems in those days, you’d rarely see SQL Server and Exchange Server on the same chassis in a production environment. All that changed with the widespread adoption of virtualization.
Chances are, if you’re reading this blog, you’re familiar with hyperconverged infrastructure. And you’re probably also aware of the value that a cloud solution can deliver. But you may not be aware of the great synergies that you can achieve by combining these technologies and what that can do for your data center.