5 ms·
We didn't go with Rackspace/Akamai specifically because they don't have a custom origin pull - pushing your assets somewhere else is at the very least a pain, a
by dminor 15y ago
We didn't go with Rackspace/Akamai specifically because they don't have a custom origin pull - pushing your assets somewhere else is at the very least a pain, and if you have images or video that is dynamically sized based on the URL it's pretty much a nonstarter.
We looked at Cloudfront but they don't have an Australian distribution point. In the end we went with EdgeCast (via GoGrid).
Originally we were with Voxel, but they've had a couple network issues in the past month (result of DDoS attacks I think).
- TomGullen 15y agoEdgecast was one I looked at but more expensive than other options for a site our site, are they better than other CDN's?
- dminor 15y agoThey are cheaper through resellers like GoGrid. I believe it is competitive with Cloudfront. As far as speed, they were among the best as far as we were able to test. There are lots of variables involved though that make it kind of hard to compare - how long things stay in the cache at the edge vs. your traffic patterns, etc.
- shingen 15y agoYep, it can be a big annoyance to say the least. I'm using Rackspace in this case because I only need to constantly export the same 5,000 to 10,000 data files. My individual embed file sizes are in the low KBs, so AWS was going to murder me on the per transaction costs (low file size, high volume).
- mikescar 15y ago> I only need to constantly export the same 5,000 to 10,000 data files. The same data for most of them, or do they all change? You might could hash the file contents, add some part of the hash to your deployed file name, and then use that hash to refer to the changed files.