forcing businesses to move away from existing cloud infrastructure could trigger expensive software redevelopment projects, with code rewriting and re-architecting accounting for 69 percent of its estimated costs.
~70% of it just to move to another hosting provider? hmmmm
Depends on how deeply the firms have gotten locked into specific cloud provider services. It’s possible to do things in a cloud-agnostic way (for example, Terraform-- ugh), but those implementations are suboptimal, and just as they used to say about Java’s much-touted OS independence, it’s “write once, debug everywhere.”
I’m convinced that it’s better to optimize for the cloud service you’re running on, and take the one-time hit if you move somewhere else. And I don’t believe there’s much rearchitecting involved: it’ll be lower-level stuff, mainly IaC and other config. If you have to recode, you probably did it wrong the first time.
The main issue with switching is the services. On AWS we use KMS, SQS, DynamoDB. On hertzner we’d have to run an instance with software for that ourselves and then rewrite systems and do migrations etc. That’s the expense.
Also KMS has no alternate because it’s not just software. It’s a HSM. So where do we store the master keys on Hetzner?
Don’t get me wrong, I’d love to do it, not up to me unfortunately.
If people are migrating to a platform, usually development takes place to add features to fill gaps and make the platform more attractive. 10-15 years ago we didn’t have well developed cloud computing but it was built by adding features that sucked people in. That can be done again if there is demand.
~70% of it just to move to another hosting provider? hmmmm
Depends on how deeply the firms have gotten locked into specific cloud provider services. It’s possible to do things in a cloud-agnostic way (for example, Terraform-- ugh), but those implementations are suboptimal, and just as they used to say about Java’s much-touted OS independence, it’s “write once, debug everywhere.”
I’m convinced that it’s better to optimize for the cloud service you’re running on, and take the one-time hit if you move somewhere else. And I don’t believe there’s much rearchitecting involved: it’ll be lower-level stuff, mainly IaC and other config. If you have to recode, you probably did it wrong the first time.
From my software development standpoint that could actually be. AWS and azure have a hefty user lock in that could cost a lot to migrate out of
Yeah, going from AWS to Hetzner will require doubling your SRE/platform/infra/whatever-you-call-them staff, clearly.
We’re on AWS at work. I use Hetzner personally.
The main issue with switching is the services. On AWS we use KMS, SQS, DynamoDB. On hertzner we’d have to run an instance with software for that ourselves and then rewrite systems and do migrations etc. That’s the expense.
Also KMS has no alternate because it’s not just software. It’s a HSM. So where do we store the master keys on Hetzner?
Don’t get me wrong, I’d love to do it, not up to me unfortunately.
If people are migrating to a platform, usually development takes place to add features to fill gaps and make the platform more attractive. 10-15 years ago we didn’t have well developed cloud computing but it was built by adding features that sucked people in. That can be done again if there is demand.