Re:Saving on egress switching from AWS to Hetzner
by hughrr on Tuesday January 25, 2022 @03:03AM
(#30069380)
We didn’t find that.
What we did find is our operational expenditure over three years tripled. So basically capital expenditure.
I’m not sure how they warped that into self congratulatory success.
The people complaining now complain that it turns out the promise of total automation was a lie. None of it is very robust and all of it is painful.
Re:Saving on egress switching from AWS to Hetzner
by d1sxeyes on Tuesday January 25, 2022 @09:40AM
(#30072247)
From a personal project perspective, I've maintained a few VPSes for quite a while now, but now I run them as a Docker Swarm, and deploy containers onto them - or better, I use serverless.
From a maintenance perspective, it's brilliant. Over time, cruft accumulates on my VPSes however disciplined I intend to be when I spin one up. Now, I no longer have to remember all of the ugly hacks I had to implement to get a particular new app I wanted to try out working, I just deploy and it's done.
Then you get into serverless and suddenly they can’t log into production anymore, and they have to instrument their code, and work within finite resources - all that stuff they ignored in college about manipulating datasets larger then core memory are suddenly relevant.
When we did our transition to serverless we found that the people who complained the loudest about their traditional servers being mysteriously corrupted were actually the same that had obtained admin rights “so they could work faster” and were going into the servers and blowing away configuration files, altering permissions, and making other changes. Once there was no more ssh and no more root privileges our outages dropped two thirds. Today it’s mostly third party outages impacting us and people deploying untested code to production.