The future of on-prem and the cloud

We’re excited to bring Transform 2022 back to life on July 19th and virtually July 20-28. Join AI and data leaders for sensible conversations and exciting networking opportunities. Register today!

Any organization that shifts from on-premise IT infrastructure to public cloud infrastructure-as-a-service (IaaS) Will Spend some time working inside the hybrid model. There is no magic switch you can flip to instantly transfer everything from your data centers to the cloud. But how long can they stay together (or should)?

If you’ve been planning on using Hybrid Infrastructure for a long time, here’s my advice: Don’t do it. While it is impossible to avoid a hybrid setup during the transition period, most organizations offer the best service by fully committing to Cloud IaaS (or as much as possible) and following a plan that can deliver you consistently over a two to three year period.

Why businesses are moving towards the cloud

One of the main drivers for conducting cloud IaaS migration is the current talent pool, for a number of reasons. First, as legacy on-premises hardware and networks age, the pool of people with the skills to properly maintain those devices and systems shrinks. At this level, it is not uncommon for professionals to retire or change careers, and certainly not many small talents with experience working with older IBM or Sun Microsystems hardware. Long-term knowledge is very valuable in an organization, which makes it both expensive to change and expensive to lose.

Similarly, with more cloud focus coming out of “young” talent from schools, Cloud IaaS is where the organization wants to be if it wants to attract and retain new employees. The goal is to develop, grow, and (hopefully) retain talent, and if the company Only Offers on-premises infrastructure and related equipment.

The game has a variety of skill sets, looking at cloud infrastructure versus on-premises. For example, the toolsets used to manage and support on-premises hardware and network devices differ from those typically used in a cloud environment. These include differences in monitoring, performance management and implementation support. And I’m not just talking about differences in terminology around how these tools work; Cloud IaaS management and security tools are generally quite different in function and use compared to on-premises tools.

Top 3 drawbacks of the long-term hybrid model

Working under a hybrid setup is always possible in principle, but doing so over an extended period of time doesn’t make sense to the business unless you have an unlimited budget. Here’s why:

  • It needs additional administrative support. Under the hybrid model, you need professional system administrators who support on-premises and in the cloud. These teams handle things like patch, monitoring, failover, backup and restore. This is more than just extra work; It involves additional knowledge – and perhaps additional sets of tools.
  • Strict costs reach the tipping point. At times, the physical footprint supporting your on-premises architecture – which was probably created years ago when it was economically sound – stops delivering the required ROI. Imagine for a second you were transposed into the karmic driven world of Earl. The house may be nice, but it’s not very efficient. You’re essentially paying for space you don’t need or use. Your needs have changed, but you still pay for the whole house. Eventually, overhead costs spread on a smaller scale, so unit costs increase.
  • Different policies. If an organization has both a cloud team and a non-cloud team, it has essentially told its people that they are on either a university or a junior university team. I have talked to a lot of clients who have inadvertently raised the issue, which can lead to resentment on the team. If the company says, “We are Cloud IaaS First,” expect everyone to be on the cloud team. If the organization says the future is in the cloud, but they want IT staff to manage on-premises, what do those staff do in three years when their colleagues work in the public cloud? How are they retrained and retrained? Organizations need to be aware of the problems of this type of situation over time.

Like most things, it comes down to people

Businesses should think about what it takes to support their on-premises and cloud IaaS based on the available talent. If you reach a certain level depending on the size and scale and need 24/7 coverage – essentially All Businesses in this age need that level of support – how many engineers do you need to cover all your different systems for 365 days a year?

There are definitely organizations that have hired a team of smart people who get stuck over time, but this team eventually realized that living outside of work is also difficult. Not only sound education but his alertness and dedication too are most required. Planning activities is always a problem because you know you are responsible; If something doing Happens, it can cost you a weekend. This realization ultimately affects innovation – you can’t expect people to come on call every week and then implement the next software / hardware solution that drives the company.

Finally, the hybrid model is essential during the transition to cloud IaaS, so the idea is to make the transition as efficient and cost-effective as possible. With that in mind, here are three steps to get the ball rolling:

  1. Bring all stakeholders into the discussion. Technical leaders, along with CFOs and other business leaders, should map out and explain why every step of cloud migration makes business sense.
  2. Perform a thorough TCO analysis. Analyzing the costs associated with cloud migration requires more diligence than using only the online calculators provided by the major cloud providers.
  3. Create a three year roadmap. Create a plan for growing migration to the cloud based on business priorities and make sure the plan continues to move forward.

Most would agree that migration customer-facing and interior-facing systems are top of mind; This is where you get the “Big Bang” and where ROI is usually generated. Where is it Not at all Built in file system or network devices. That said, if you run out of money or time before you complete the migration of these aging systems, you will be stuck with a sub-optimal solution and the business may suffer.

After all, there is no cookie-cutter solution that works for every business, and these are just some of the issues you need to consider. How you reach the public cloud may look different than a peer or competitor, but the fact is that limiting the amount of time you spend working under a hybrid model will give you the best chance of success.

Michael Bathon is Vice President and Executive Advisor at Rimini Street,


Welcome to the VentureBeat community!

DataDecisionMakers is where experts, including tech people working on data, can share data-related insights and innovations.

If you would like to read about the latest ideas and latest information, best practices and the future of data and data tech, join us at DataDecisionMakers.

You might even consider contributing to your own article!

Read more from DataDecisionMakers

Similar Posts

Leave a Reply

Your email address will not be published.