this post was submitted on 20 Oct 2025
884 points (99.2% liked)
Programmer Humor
27101 readers
817 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
Screw the compute budget, the tripled team size without shipping any more features is a bigger problem here.
I've seen the opposite. "Oh, you moved your app to the cloud and rebuilt it to be full cicd and self healing? Cool. Your team of 15 is now 3."
I'm not sure if you are referring to the same thread.
I'm talking about the effort to build multi region and multi cloud applications, which is incredibly difficult to pull off well. And presents seemingly endless challenges.
Not the effort to move to the cloud.
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.
It's phenomenally expensive from a practical standpoint, it takes an immense amount of engineering and devops effort to make this work for non trivial production applications.
It's egregiously expensive from an engineering standpoint. And most definitely more expensive from a cloud bill standpoint as well.
We're doing this right now with a non trivial production application built for this, and it's incredibly difficult to do right. It affects EVERYTHING, from the ground up. The level of standardization and governance that goes into just making things stable across many teams takes an entire team to make possible.
In my experience using containers has removed requirements for additional engineering cost to deploy between providers because a container is the same wherever it's running, and all the providers will offer container hosting, and most offer cluster private networking.
Deployment is simplified using something like octopus which can deploy to many destinations in a blue-green fashion with easy rollback.
Yes, containers make your application logic work.
That's the lowest hanging fruit on the tree.
Let's talk about persistence logic, fail forwards, data synchronization, and write queues next.
Let's also talk about cloud provider network egress costs.
Let's also talk about specific service dependencies that may not be replicatable across clouds, or even regions.
Oh, also provider specific deployment nuances, I AM differences, networking differences....etc
Containers are nice, but don't really cover things like firewalls, network configuration, identity management, and a whole host of other things, the configuration of which varies between providers.
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!!!!"