this post was submitted on 22 Jun 2024
726 points (98.7% liked)

Programmer Humor

19587 readers
2162 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

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] xtapa@discuss.tchncs.de 1 points 4 months ago (1 children)

We got our own platform based on kubernetes and cncf stuff and we don't have to care anymore about the metal underneath. AWS? OTC? Azure? Thats just a target parameter, platform does the rest. It's great.

[–] widerporst@feddit.de 1 points 4 months ago (2 children)

How often do you switch cloud providers that this is even a real rather than a hypothetical benefit? (Compared to the cost of dealing with a much more complicated stack.)

[–] xtapa@discuss.tchncs.de 4 points 4 months ago

It's not about switching, it's about hosting our services on different platforms at the same time.

[–] bamboo@lemmy.blahaj.zone 2 points 4 months ago

I manage a stack like this, we have dedicated hardware running a steady state of backend processing, but scale into AWS if there's a surge in realtime processing needed and we don't have the hardware. We also had an outage in our on prem datacenter once which was expensive for us (I assume an insurance claim was made), but scaling to AWS was almost automatic, and the impact was minimal for a full datacenter outage.

If we wanted to optimize even more, I'm sure we could scale into Azure depending on server costs when spot pricing is higher in AWS. The moral of the story is to not get too locked into any one provider and utilize some of the abstraction layers so that AWS, Azure, etc are just targets that you can shop around for by default, without having to scramble.