Cloud repatriation is becoming increasingly common as organizations repatriate workloads or applications from public clouds to in-house or other locations. Repatriation is usually due to technical misfires or perceived cost inefficiencies associated with fast-growing public cloud consumption. However, repatriation should not be considered a failure, but rather a tactical lever for workload placement that can be used as part of an organization’s multicloud-by-design strategy.
Workload distribution has grown more rampant due to the pandemic forcing employees to work remotely or split time between home and corporate offices, resulting in a mixed bag of on-premises and off-premises computing scenarios. Multicloud-by-design enables application workloads to be placed intentionally, based on a variety of factors including cost efficiency, performance optimization, latency, security, compliance, and governance. Organizations need to consider rebalancing their portfolios and evaluate whether assets are best served running on-premises or in public clouds, colos, or the edge.