Want to avoid Cloud repatriation? Here's how...

If you've been reading our Blog posts and materials on our site, you'll know that we're big proponents of doing your homework before you make big decisions.  You certainly gather information and pricing before you purchase a car or a home, so why would it be any different with major decisions with your IT infrastructure?  Those IT infrastructure decisions deserve the same attention as your personal ones.

Right now, when you have new workloads, or are looking to modernize your existing workloads, the options that you have are 1) keep doing what you're doing, which usually means staying with the familiar 3-Tier infrastructure; 2) looking at hyper-converged infrastructure like Nutanix; 3) moving to one of the Public Cloud vendors' infrastructures; or 4) doing nothing.  You know, sometimes option 4 is the best option, but that's not what this post is about.

Most of you have been encouraged/told by your management that you need to "move to the Cloud".  That's often uttered by upper management without any consultation with the folks who actually run the IT environment.  In other words, you're told to move to the Cloud regardless of whether that's the right move.

Man, that's very short sighted, isn't it?  Unless you're certain that it's the BEST place for your workloads, why would you think that's where you should put the workloads?  Remember, you do your homework with your personal decisions, so it's important that you do it now.

We've been doing this long enough to tell you that you're certainly not going to spend less in the Public Cloud; your costs are going to rise.  And, with some exceptions, you're not going to be getting better results in the Public Cloud.  Remember, you understand your IT environment better than your upper management, so it's important that you help educated them.

We've heard users say that if the Public Cloud doesn't work well for them after going there, they'll "repatriate" the workload back to your own data center.  Let's call BS on that right now...the people who wanted you to go to the Cloud are going to do all they can to prove that their decision was right.  Damn the facts...they're going to make sure that everyone thinks they did the right thing.

But here's the thing; they usually don't have the facts to back up that claim.  So, everyone's going to look bad, including, possibly, you.  You're going to have your workloads running in someone else's data center at a higher cost than you were doing it before or could do it now.  Wouldn't it be better to avoid the whole mess?

That's where we come in.  We've developed a tool that can help you evaluate where your workloads should run to benefit the organization BEST.  It's simple, but by using our tool, you'll be doing the important homework we've referenced above.  This way, if it runs out the Public Cloud is the best place for your workload (by workload) you'll be able to defend the decision and likely not have to repatriate it in the future. 

The key here is that the best way to avoid having to repatriate a workload is to never have it go to the Public Cloud unless you can prove that's the best place for it.

Contact us...we know what we're doing, and can help.  Tim Joyce 925-324-1582 and [email protected].

---