Which cloud workloads are right for repatriation?

This post was originally published on Info World

Cloud repatriation may be a sensitive and polarizing topic for some, but it really should be just another architectural option.

When I say that some workloads should return to the data center, I am not pushing back on cloud computing. This is about merely finding more optimized platforms for certain types of applications and data sets based on changes on technology and market. The objective is to bring more value back to the business.

To determine when repatriation makes sense, we need to think about basic concepts that architects should be considering anyway as they look for opportunities to provide better cost-optimized platforms for some workloads.

Look at the monthly costs and values of each platform. This is the primary reason we either stay put on the cloud or move back to the enterprise data center. Typically the workload has already been on the cloud for some time, so we have a good understanding of the costs, talent needed, and other less-quantifiable benefits of cloud, such as agility and scalability. You would think that these are relatively easy calculations to make, but it becomes complex quickly. Some benefits are often overlooked and architects make mistakes that cost the business millions.

All costs and benefits

Read the rest of this post, which was originally published on Info World.

Previous Post

Microsoft CEO gushes about AI as he prepares to ax 10,000 jobs

Next Post

Gartner Lowers 2023 Worldwide IT Spending Forecast to 2.4% Growth