Fastly Edge Cloud Platform vs. IBM Cloud Content Delivery Network

The service is really well-suited for pretty much any site that is primarily display-driven (that is, mostly GET requests). The network is able to handle massive volumes of traffic and their POPs have spread out pretty much anywhere that it's easy to get them (so basically everywhere but China and Russia). My team witnessed several large-scale attack attempts on some high-profile websites (attacks in the 10s of millions of requests per second) that were mitigated before ever coming back to the actual application; in one case we didn't realize the attack had happened until we looked at the logs the next day. Because it's a cache store option, the default configuration does not cache POST responses, and it can be difficult to set up things like authenticated paywalls as a result.

Incentivized

The IBM Cloud Content Delivery Network is well suited for web applications that have a distributed worldwide audience. Modern web sites load a lot of assets, such as javascript and css, that can be sped up significantly with it.

Incentivized

• Very performant and fast -- major companies have drastically reduced page load times with Fastly's edge technology.
• Support for many types of media, including video.
• Image add-on makes serving and manipulating images very simple.

Incentivized

• WAF is hard to configure.
• No comprehensive rate limiting without a pricey upgrade.
• Account access controls are extremely limited.

Incentivized

It’s the fastest and most configurable.

Incentivized

• Fastly dramatically reduces load times for clients all over the world thanks to their global system of POPs.
• Fastly is a cost-effective choice when a highly-performant CDN is required and makes it simple to support data that is quickly invalidated.

Incentivized

• It has reduced load on our servers so we can reallocate server resources to our web app
• IBM Cloud Content Delivery Network has sped up response times for our app and made customers happier

Incentivized