In post #1 in this series, we defined hyper-convergence, then in the next post, we talked about some common use cases. Now, it’s time to talk about the potential pitfalls of hyper-convergence and what you can do to avoid them.
Luckily, this will be a short post because there aren’t all that many, but there are a few things that you should think about in the context of your overall IT strategy.
#1 Should you expand capacity in your on-premises data center?
Yes, hyper-convergence is easy to deploy and makes it easy to expand on-premises capacity. But should you? Before making any additional investments, take the time to consider whether the organization might benefit from housing those applications and databases in a public or private cloud.
#2 You need to understand your data storage requirements.
Again, because hyper-convergence is so easy to set up, it may lead you to deploy it in scenarios where it may not fit. For example, because compute and storage resources are sharing the same appliance, it can limit storage capacity. If you don’t understand the storage requirements of your applications, performance can suffer. If you have concerns, our hybrid IT experts can help you work through them.
#3 While technology advances, human nature stays the same.
If you have a team of IT staff focused on provisioning and maintaining data center resources, they may find themselves with a lot more time on their hands. Of course, most IT departments already have far too much to do, so that may not be an issue. And, these freed-up resources can often be better utilized in other ways, i.e., focusing on how technology can meet the needs of the business instead of on how the business can meet the needs of the technology. Nevertheless, you need to think through how the improved efficiency brought about by a hyper-converged infrastructure may be perceived, at least initially, by the human resources in your IT department.
#4 Consider the full ROI when making the business case.
Many IT departments use a continual upgrade loop for data center resources, upgrading servers in one cycle, storage resources the next, etc. Spreading the investment out like this may look cheaper on paper, but it increases costs in the long run. Plus, it decreases the IT department’s ability to respond to the dynamic needs of the organization. When something unexpected crops up, IT needs to go through a round of budget approvals, procure the resources, implement them, etc. That’s hardly an agile IT environment. When making the business case for hyper-convergence, make sure you’re looking at the total cost of ownership and not just the initial budget requirements.
In our next post, we’ll take a look at two hyper-converged offerings from HPE. As always, I’d love to hear from you. Please add your thoughts in the comments section or reach out to me directly at Glenn.Bontje@lvs1.com.