Akamai vs Fastly

• Very advanced compression algorithms and a global content delivery network.
• Sophisticated security features.
• On-demand network scalability.
• Great dashboard and real-time reporting

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

• Cost. Akamai is an enterprise level product and the cost can be pretty expensive for smaller organizations.
• Activations can take a while and therefore if you are doing a lot of testing on different scenarios you may spend hours waiting for activations to take effect. However this may not be an issue with Akamai itself but the fact that rules need to be propagated to all edge servers.

Read full review

• Speed up delivery of content and improved user experience for users coming to our website
• Save cost as we do not need as many back end servers to run our web instance because majority of load is being handled by Akamai servers

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