908
duh-dum.
(sopuli.xyz)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 20 Oct 2025
908 points (100.0% liked)
Programmer Humor
27101 readers
1333 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
If you properly divide your instances between providers and regions and use load balancing which uses a corum of 3 availability model then it can be zero downtime pretty fairly guaranteed.
People be cheap and easy tho, so 🤷♂️
Yup. And I think I'll add:
What do you mean we've blown our yearly budget in the first month.
Dividing between providers is not what people would be doing if the resilience of cloud services were as is being memed about.
Doing so is phenomenally expensive.
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.
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.
This is why OpenTofu exists.
Yeah, Terraform or it's FOSS fork would be ideal, but many of these infrastructures are setup by devs, using the "immediately in front of them" tools that each cloud presents. Decoupling everything back to neutral is the same nightmare as migrating any stack to any other stack.
Definitely. I go through that same nightmare every time I have to onboard some new acquisition whose devops was the startup cfo's nephew.
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
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.
The administrative overhead and the overhead of engineering everything to with multiple vendors is what is massive
Also requires AWS to do the same thing which they sometimes don’t …
"But we have our load balacing with 3 different AWS buckets!!!!"