"Lift and shift" isn't just an Azure-specific phrase. Many people use it pejoratively, and point to it as an anti-pattern, and something to avoid.
Similar terminology is "forklift"... been hearing that one for well over a decade.
Migrations are oftentimes an opportunity to revisit scaling, configuration, build and deployment pipelines, platform primitives, etc. Every migration I've been involved in has a (probably necessary) tension between getting the job done efficiently, while not repeating all the mistakes of the past.
“Lift and shift” came into the conversation once we started talking about how we were paying too much for AWS. The obvious stuff was things like less bin packing, and bandwidth for third party services, like telemetry dashboards.
And it’s not just the service fees. I blanche to think of the opportunity costs we accrued by focusing for that long on infrastructure to the exclusion of new product and features. It’s truly breathtaking.
And then there’s the burnout, and the ruffled feathers.
Definitely. We migrated to a new telemetry vendor and I'm pretty sure it'll take 10 years for us to recoup the cost savings in man power and opportunity cost.
They were worried the old vendor might go under. My own track record with predicting company failures is pretty bad, so I suspect they'll still be around ten years from now.
Similar terminology is "forklift"... been hearing that one for well over a decade.
Migrations are oftentimes an opportunity to revisit scaling, configuration, build and deployment pipelines, platform primitives, etc. Every migration I've been involved in has a (probably necessary) tension between getting the job done efficiently, while not repeating all the mistakes of the past.