Most companies need a better strategy than repatriating to the cloud for problematic applications. These applications hid their inefficiencies while running on-premises because we never saw a bill for resource utilization, including storage, network, compute, etc. Often these applications did not undergo any architectural review when they were created. “It works, doesn’t it?” It was the metric that determined success. I would call something that works but costs five times more money in the cloud than on-premises a failure, but most didn’t.
The compromise approach is to optimize in place. This means doing the bare minimum to get applications and data sets in a state that minimizes resource usage and maximizes optimization when running on a public cloud provider.
Rethink costs
High cloud costs are usually due to incorrect cloud services or tools, faulty application load estimates, and developers who designed applications without understanding where the cloud saves money. You can see this in the intended use of microservices as base architecture. Microservices are a good option for some applications, but they can consume around 70% more cloud resources. Changing the architecture to a more simplistic approach (such as monolithic) may be more cost-effective.
