3 ms·

> orgs realize how easy it is to leave AWS or Azure for something more local Have you ever tried to migrate anything non-trivial on one cloud to another? Vendo

> orgs realize how easy it is to leave AWS or Azure for something more local Have you ever tried to migrate anything non-trivial on one cloud to another? Vendor lock-in is very real. Over in my part of the world, I'm in year three of moving one (1) app off AWS and we'll be lucky if we finish this year. The app isn't even that complicated, but it was built entirely on AWS-only tech (Lambda, DynamoDB, etc) and migrating clients (esp. authentication) to the new backend without downtime or breaking legacy clients is very tricky.

stego-tech 2y ago
> Have you ever tried to migrate anything non-trivial on one cloud to another? Vendor lock-in is very real. Yep! It's very real if you use vendor-exclusive tooling, and it's why I was the perpetual wet blanket in meetings where leaders would push for said tooling over, say, Terraform or Kubernetes. Still, it's easier than you think for most LOB applications out there. It's really just the in-house custom stuff or products that will take longer to move, but make no mistake - the smart players have already started said moves elsewhere in some form. Maybe it's tasking the architects with identifying gaps between cloud vendors, or adding new sprint backlog items to remove proprietary dependencies on AWS/Azure/GCP over the coming FY, or tasking Engineering with a POC for a major application component "just to weigh our options". It's in motion.