AWS egress prices are so insanely high that for bandwidth heavy apps I've had consulting clients where we cut their hosting costs by 90 percent by moving them off AWS. That's extreme, but their bandwidth costs are easily 5x-50x that of alternatives, so it doesn't take much egress before it dominates the cost.
Re:Unbundling AWS
by ignoramous on Sunday December 01, 2019 @04:20PM
(#21677855)
If you don't mind me asking, which cloud provider did you move your client to? Or, moved them on-premise, you mean?
Depends on their need; I tended to move them to managed hosting, which used to reduce their hosting costs massively and reduce their devops costs. Hetzner for anyone with most traffic in Europe. DigitalOcean in some cases. Sometimes we just put caching proxies (external to AWS) in front of EC2.
I've managed racks for customers too, but managed hosting at Hetzner is now usually cost-effective vs. colo-hosting in London where I am. Since they also offer cloud services (though pretty basic) now, there's the option of mixing and matching.
Amazon consistently charges for egress only. Ingress is free.
This is not true for inter-az bandwidth.
https://www.lastweekinaws.com/blog/aws-cross-az-data-transfe...
Live and learn, that seems to be the exception. That sounds like it might be an accident though?
Re:Unbundling AWS
by slovenlyrobot on Sunday December 01, 2019 @08:49PM
(#21679265)
Their inter-AZ pricing is certainly no accident. I'm betting for a large chunk of custs it nets them something on a par with egress
2) Contemporary site/app development renders the latency of individual requests irrelevant. The whole page is going to boop and bounce around for 20 seconds anyway, why make a big deal about it?
The web is a measurably worse experience now than it was 10 years ago (maybe even 5), so it's ironic that Goodhart's Law has led so many astray toward measuring smaller and smaller trees within a growing forest. "Well but we have to get the request for number of friends below 10ms" while the other 400 requests on the page are dilly-dallying and experiencing their own latencies. Then the CSS gets applied.