In the ever-evolving world of technology, businesses are constantly looking for ways to optimize their operations and reduce costs. One such journey we embarked on was moving our infrastructure from Amazon Web Services (AWS) to a bare-metal solution. This transition not only provided us with more control over our resources
To the surprise of no one. Cloud services are convenient and easily scalable - Which makes it cost effective for a lot of work loads. But for all work loads? Of course not!
They barely touched on the time and money spent managing bare metal. I’d imagine that 230k a year is gonna get a big ol dent in it when their assumption of “modern servers make maintenance needs much lower” turns out to be false.
All for not hosting in AWS but I want to see one of these articles put out actual numbers about what it looks like to run. I want the we are two years into this and have learned X, Y, and Z post. And one that isn’t written by DHH
Also, it’s just super easy to waste money in the cloud. That convenience and scalability is a huge double-edged sword. Even if you try to be careful, analyze pricing structures, estimate your spend, optimize your utilization, etc. (which a lot of orgs and engineers don’t), you can get one thing wrong and end up spending way more than you expected anyway.
Given that, even as someone who likes using the cloud a lot more than my prior experiences with on-prem, I can see why a lot of companies would decide to throw their hands up and switch to on-prem anyway. However, I also feel like a lot of orgs could probably find a happier medium if they invested the time to understand, track, and optimize their cloud usage more effectively.
To the surprise of no one. Cloud services are convenient and easily scalable - Which makes it cost effective for a lot of work loads. But for all work loads? Of course not!
“We saved $xxx by buying our own car instead of paying taxi every time.”.
They barely touched on the time and money spent managing bare metal. I’d imagine that 230k a year is gonna get a big ol dent in it when their assumption of “modern servers make maintenance needs much lower” turns out to be false.
All for not hosting in AWS but I want to see one of these articles put out actual numbers about what it looks like to run. I want the we are two years into this and have learned X, Y, and Z post. And one that isn’t written by DHH
Also, it’s just super easy to waste money in the cloud. That convenience and scalability is a huge double-edged sword. Even if you try to be careful, analyze pricing structures, estimate your spend, optimize your utilization, etc. (which a lot of orgs and engineers don’t), you can get one thing wrong and end up spending way more than you expected anyway.
Given that, even as someone who likes using the cloud a lot more than my prior experiences with on-prem, I can see why a lot of companies would decide to throw their hands up and switch to on-prem anyway. However, I also feel like a lot of orgs could probably find a happier medium if they invested the time to understand, track, and optimize their cloud usage more effectively.