4 ms·

Why Cloud Migrations Fail

• skywhopper 2y ago
  In my experience: Failure to get buy-in and include relevant architectural and operational experts in the evaluation and planning processes.
• deleted 2y ago
  [deleted]
• kkfx 2y ago
  "cloud" it's just a synonym of "someone else computer", what someone do on someone else computer matter. If for cloud we intend VPS, well, I expect next to zero issues, because someone else computer "origin" and "destination" are essentially the same. When cloud means someone else stack on someone else computer, well, that's not standard, so "migration" could means full-rewrite of an infra built on top of the aforementioned someone else stack, to someone other stack, the use of an "equivalent stack translator", let's say a wine (windows api emulator) for cloud etc etc etc. What managers refuse to learn is simply this "cloud" does not means a specific tech, offered by a handful of vendors.
  • paulddraper 2y ago
    > If for cloud we intend VPS, well, I expect next to zero issues, because someone else computer "origin" and "destination" are essentially the same. Hardly. Cloud is cloud because there's a lot that happens outside the VPS. Autoscaling, monitoring, networking, security, etc.
    • kkfx 2y ago
      As long as that's separate, meaning the "personal part" of the cloud customer is "a common standard" this is not much a migration issue, if you explicitly develop something with $AVendor APIs, well, that's not a common standard, that's something vendor specific and migrate could mean a total re-write.
• CapeTheory 2y ago
  It is simply a lack of skilled staff. The industry has plenty of mediocre people who struggle to follow a playbook, but hardly any people who can write the playbook. It is a common trope that the government is like this, but over the last 5 years I have observed it to be true at every organisation I've encountered.