Akamai vs Fastly

• Edge caching with Akamai's CDN tools allow for offloading repetitive work from more expensive application servers
• Akamai's DDOS protection services are amongst the most robust in the industry

Read full review

• You can put your site behind Fastly and then selectively cache only some of the endpoints. You can modify the responses returned by stripping cookies or other personalization headers.
• You can deliver images, and based on the user agent being Chrome, decide to serve, for example, a WEBP image format instead of PNG or JPG.

Read full review

• The user interface can be daunting and confusing to new users
• The pricing tiers are often not competitive with standard CDN service offerings from other companies

Read full review

• Positive - Akamai vastly reduced the number of content delivery servers needed here, saving money, hardware and management overheads.
• Negative - I don't think it's a "cheap" option, but also, you get what you pay for and for such a powerful product you don't expect it to be free.
• Positive - some of the support we have had has been really good.

Read full review

• While I was at Wanelo we were able to put Fastly in front of the growing web app, and selectively cache end points to improve stability and performance. In the meantime we rewrote the app completely in Ruby. We wouldn’t have been able to do that without Fastly.

Read full review