Ahrefs Saved US$400M in 3 Years by Not Going to the Cloud (2023)
1–10 of 66 posts
Re: Ahrefs Saved US$400M in 3 Years by Not Going to the Cloud (2023)
#2...in the worst way imaginable
Doing a direct lift and shift with 1:1 replacement of instances is, intentionally, prohibitibely expensive, so you stop and think.
Re: Ahrefs Saved US$400M in 3 Years by Not Going to the Cloud (2023)
#3Re: Ahrefs Saved US$400M in 3 Years by Not Going to the Cloud (2023)
#4Hybrid approach is best in cases like this. Use the cloud for client facing interfaces and rent dedicated servers for the spiders.
edit: even better, build your own data center instead of renting.
Re: Ahrefs Saved US$400M in 3 Years by Not Going to the Cloud (2023)
#5>by not going to the cloud ...in the worst way imaginable Doing a direct lift and shift with 1:1 replacement of instances is, intentionally, prohibitibely expensive, so you stop and think .
Re: Ahrefs Saved US$400M in 3 Years by Not Going to the Cloud (2023)
#6Re: Ahrefs Saved US$400M in 3 Years by Not Going to the Cloud (2023)
#7Re: Ahrefs Saved US$400M in 3 Years by Not Going to the Cloud (2023)
#8Re: Ahrefs Saved US$400M in 3 Years by Not Going to the Cloud (2023)
#9There are no permission issues or ACLs.
There’s no need to auto scale and the traffic is very predictable.
There is no serious need to orchestrate deployments. I imagine it’s mostly just workers reading URLs from a queue and crawling a page. So very easy to deploy new servers.
This is just an edge case scenario specifically great for self hosting.
Re: Ahrefs Saved US$400M in 3 Years by Not Going to the Cloud (2023)
#10>by not going to the cloud ...in the worst way imaginable Doing a direct lift and shift with 1:1 replacement of instances is, intentionally, prohibitibely expensive, so you stop and think .