It's demonstrably little more expensive than running more instances on the same provider. I only say -little- because there is a marginal administrative overhead.

[–] rainwall@piefed.social 27 points 1 month ago* (last edited 1 month ago) (5 children)

Only if you engineered your stack using vendor neutral tools, which is not what each cloud provider encourages you to do.

Then the adminstrative overhead of multi-cloud gets phenomenally painful.

[–] felbane@lemmy.world 4 points 1 month ago (4 children)

This is why OpenTofu exists.

[–] Lysergid@lemmy.ml 1 points 1 month ago (1 children)

Infrastructure is there to be used by apps/services. It doesn’t matter how it’s created if infrastructure across providers does not provide same API. You can’t use GCP storage SDK to call AWS s3. Even if API would be same, nothing guarantees consistent behavior. Just like JPA provides API but implementations and DBs behavior are inconsistent

[–] felbane@lemmy.world 2 points 1 month ago

You can use the S3 API to interop with basically every major provider. For most core components there are either interop APIs or libraries that translate into provider-native APIs.

It's 100% doable to build a provider-agnostic stack from the iac all the way up to the application itself.

load more comments (2 replies)

load more comments (8 replies)