I often fantasize about moving a bunch of my company's crap off of ECS/EKS and onto a managed colo with just old-school ansible deployments. I've even spec'd out some bare metal from our local colocation facility and the servers they offer are so ridiculously powerful and CHEAP. We could run our entire production system in a half-rack for about 10% of what we pay AWS. But alas, nobody will ever go for it and I'm left…
I had to look it up - Ansible's initial release was just over 11 years ago. Calling it "old-school" sure took me by surprise, though I suppose that is a long time in the tech world. To me, old school is doing everything via Bash or even by hand.
Ahrefs saved $400m in 3 years by not going to the cloud
41–50 of 166 posts
Re: Ahrefs saved $400m in 3 years by not going to the cloud
#42Earlier quoted context omitted.
A significant number of "cloud migrations" involve moving an application running on Linux on a server to running on Linux on a VPS for similar or higher cost. Not even using ANY of the "features" of the cloud, just treating it like a server. But then they can say "cloud" and everyone's happy.
Ah yes, the "actual" way to use cloud is to undergo a major re-write of your application such that it is inextricably tied into the proprietary PaaS options of your cloud provider. Cloud is amazing for highly variable loads. I also see it as a bit of a luxury service for ops types (like me) - I don't have to go to a DC and manage hardware or deal with a DCops crew, so that's nice, but you probably wouldn't buy luxury…
Some can do it, some require you to basically image the entire machine onto a new one, some can't handle it at all.
Re: Ahrefs saved $400m in 3 years by not going to the cloud
#43I recently heard from a senior IT person that the company for which he works could save many millions by moving a certain application from a hairball of micro-services at AWS to a much simpler architecture on colocated servers... but the company's management doesn't want to hear any of it. In fact, management wants IT to move every legacy application that's not yet on the cloud to the cloud, specifically to AWS, beca…
From a biz perspective, that can be a bad move and signals that you're not in growth phase but in cutting costs to preserve profits. Using cloud derisks you for future costs because it's managed for you, and then you allocate capex towards making better features. Doing it locally means having a team of IT admins/professionals you normally only need a few of which also incurs a lot of cost and risk.
Similarly, “easy” scalability doesn’t necessarily make up for COGS when scaling up. If I can flip the autoscale switch while I grow to $1bn ARR and pay $750M/yr to the cloud, I’m not doing nearly as well as if I hire ten FTEs and pay $150M in combined capex and opex over two years.
(And if my COGS is 75% of the list price, it’s hard to give discounts, pay for sales, etc)
Re: Ahrefs saved $400m in 3 years by not going to the cloud
#44I feel this is comparing apple and pears. For sure AWS is more expensive, however, you looking at a markup of 50%, at most 100%.
Re: Ahrefs saved $400m in 3 years by not going to the cloud
#45I recently heard from a senior IT person that the company for which he works could save many millions by moving a certain application from a hairball of micro-services at AWS to a much simpler architecture on colocated servers... but the company's management doesn't want to hear any of it. In fact, management wants IT to move every legacy application that's not yet on the cloud to the cloud, specifically to AWS, beca…
A significant number of "cloud migrations" involve moving an application running on Linux on a server to running on Linux on a VPS for similar or higher cost. Not even using ANY of the "features" of the cloud, just treating it like a server. But then they can say "cloud" and everyone's happy.
Re: Ahrefs saved $400m in 3 years by not going to the cloud
#46Earlier quoted context omitted.
despite what everyone thinks that doing things locally is cheaper, if you're running a business and allocating money towards headcount and benefits plus additional risk of maintaining team it rarely makes sense. HN is full of people who run a hobby server and think that a fortune 500 should manage its own PostGres
You still need headcount to manage systems on AWS. And not really fewer then if you would run them locally. Source: managed systems locally, am now managing systems on AWS
Re: Ahrefs saved $400m in 3 years by not going to the cloud
#47Earlier quoted context omitted.
You still need headcount to manage systems on AWS. And not really fewer then if you would run them locally. Source: managed systems locally, am now managing systems on AWS
Surely the cloud managed solution reduces the amount of custom magic that I have to put into place to keep things running. Everything is standardized & documented. There is a huge community to turn to if help is needed. And very less work is required if I get hit by a bus and someone else is now the owner of the huge system that I previously owned.
Also, all of your points apply to non-cloud systems too.
Re: Ahrefs saved $400m in 3 years by not going to the cloud
#48I recently heard from a senior IT person that the company for which he works could save many millions by moving a certain application from a hairball of micro-services at AWS to a much simpler architecture on colocated servers... but the company's management doesn't want to hear any of it. In fact, management wants IT to move every legacy application that's not yet on the cloud to the cloud, specifically to AWS, beca…
Everyone looked at me like an alien speaking a different language, lol. Then was politely dismissed, even though I'm experienced in running hardware.
AWS, GCP, Azure, really managed to expertly pull off the greatest heist of all time. They're useful for sure, but somehow they've gotten everyone to drink this potent marketing kool-aid that if you're not using them then you're not serious about success. So cringe.
Re: Ahrefs saved $400m in 3 years by not going to the cloud
#49I recently heard from a senior IT person that the company for which he works could save many millions by moving a certain application from a hairball of micro-services at AWS to a much simpler architecture on colocated servers... but the company's management doesn't want to hear any of it. In fact, management wants IT to move every legacy application that's not yet on the cloud to the cloud, specifically to AWS, beca…
Which part would actually saving them the money? - rearchitecting/simplifying, or changing where it runs? There would need to be an apples-to-apples comparison to be meaningful.
That said, I don't believe everything needs to be in the cloud - but maintaining data-centers are also very expensive, and need to be accounted for very differently.
Re: Ahrefs saved $400m in 3 years by not going to the cloud
#50Earlier quoted context omitted.
So let us know what is wrong and how a proper TCO calculation looks like. What's missing?
Anything that you have to do "extra" compared to managing the hardware yourself. E.g. this article is missing even basic stuff like the (prorated) salary costs of employees buying, installing and servicing the hardware.