Hacker News Reader

Comment by string | Hacker News Reader

Good and clear explanation. This is a risk you take when you use a CDN, I still think the benefits outweigh the occasional downtime. I'm a big fan of BunnyCDN, they've saved me a lot of money over the past few years.

I'm sure I'd be fuming if I worked at some multi-million dollar company but as someone that mainly works for smaller businesses it's not the end of the world, I suspect most of my clients haven't even noticed yet.

View on HN

TIL about BunnyCDN. I had been paying $0.08 per GB on AWS Cloudfront whereas BunnyCDN is only $0.01 per GB. Can you comment on you experience with them ? Are the APIs comprehensive e.g. cache invalidation ? do they support cookie base authorization ? Any support Geo-Fencing?

I’m using them quite extensively (except the Stream video feature). APIs are good, traffic can be restricted or rerouted based on Geo. Not sure what cookie based auth would do in a CDN but if it’s on the origin it passes through. For authenticating URLs there is a signing scheme you can use.

Can this allow me to route x.mydomain.com (more than one wildcard and top level) to x.a.run.app (Google Cloud Run)? Cloud Run (and the Django app behind it) won't approve domain mapping for Mumbai yet so I am looking for transparent domain rewriting. Cloudflare allows it but its kinda expensive.

https://cloud.google.com/run/docs/locations#domains

As the docs say, you can use a LB with this. It'll be 18 dollars a month, though.

I noticed another user has already commented, sounds like they've had more experience with the things you're interested in than I have, for FWIW, the APIs have been sufficient for my use cases and you can definitely purge a pullzone's cache with them.

My primary use has been for serving image assets, switched over from Cloudfront and have seen probably a >80% cost reduction, and no noticeable performance reduction, but as I mentioned I'm operating at a scale where milliseconds of difference don't mean much.

Think the answer is yes to all three questions, depending on the specifics. They've got a nice setup, about ~40+ edge locations compared to Cloudfront's ~200+, but the advantage is they're massively cheaper for very small increase in latency. They also have the ~5 region high-volume tier which is something like another order of magnitude cheaper.

The feature set is pretty full, no edge functions, but there is a rule engine you can run on the edge. Fast config updates, nice console and works well enough for most of my projects.

They also have a nice integrated storage solution that's way easier to configure than S3 + Cloudfront, and lots of origin shielding options.

First time using a CDN improved our site [1] performance by a huge amount, thanks to BunnyCDN. Really easy to setup, great dashboard. The image optimizer for a flat rate works really really well. Only missing option is to rotate images, which I opened a feature request for with them.

You can see our CDN usage inspecting the URLs to the product images. Size attributes are added to the URL and Bunny automatically resizes and compresses the images on the fly.

[1] https://www.airsoftbazaar.nl

>AWS Cloudfront

AWS Cloudfront is neither the fastest or cheapest, in both bulk and small file transfer. I cant think of a single technical reason it is better. Fastly, Akamai, Limelight, Cloudflare or even good old EdgeCast. They all have their strong point in some of their niche services or domain.

Any reason for using AWS Cloudfront Enterprise purchase reason? Or are there some technical superiority I am not seeing?

Reply on news.ycombinator.com