Akamai vs Amazon CloudFront: What are the differences?
What is Akamai? The leading platform for cloud, mobile, media and security across any device, anywhere. If you've ever shopped online, downloaded music, watched a web video or connected to work remotely, you've probably used Akamai's cloud platform. Akamai helps businesses connect the hyperconnected, empowering them to transform and reinvent their business online. We remove the complexities of technology, so you can focus on driving your business faster forward.
What is Amazon CloudFront? Content delivery with low latency and high data transfer speeds. Amazon CloudFront can be used to deliver your entire website, including dynamic, static, streaming, and interactive content using a global network of edge locations. Requests for your content are automatically routed to the nearest edge location, so content is delivered with the best possible performance.
Akamai and Amazon CloudFront can be categorized as "Content Delivery Network" tools.
According to the StackShare community, Amazon CloudFront has a broader approval, being mentioned in 3387 company stacks & 621 developers stacks; compared to Akamai, which is listed in 92 company stacks and 15 developer stacks.
What is Akamai?
What is Amazon CloudFront?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Akamai?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Akamai?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
I love CloudFront. All my assets are hosted by them, and they cut page load time in half, and my average bill is around $0.15/month. They're good, fast, and cheap — pick three!
We chose CloudFront mostly because it’s incredibly popular. But also because it’s the recommended CDN for Heroku, which means there shouldn’t be any problems using them together. Rails makes it really easy to drop in a CDN reference for your app so that when your assets get compiled, they’re shipped off to the CDN and then deployed with your app.
So anytime we push to Heroku, we’re pushing up to CloudFront (if the assets don’t already exist). One major issue we still haven’t been able to solve involves Fonts. Has anyone actually been able to get fonts served up through CloudFront using Rails 4 and Heroku? Literally spent hours researching this and can’t find any solutions. We ended up just referencing a CDN for all the font libraries.
We have a separate distribution for each environment, since I don’t think it’s possible to use the same distribution for the multiple domains.
I use CloudFront to front the static website at zerotoherojs.com that I host in an s3 bucket.
This way, I don’t have to worry about scalability or performance, as I’ll know that the content will be delivered to the users as fast as possible from the closest edge location.
Parked in front of an nginx instance that serves all of our static assets. Performance and reliability have been excellent, and the header pass-through rules are wonderful. Price is affordable, as well.
In my opinion, the best Content Delivery Network for the money. This, along with other services from AWS's ecosystem make this the easy choice for CDN. Fast, simple and cheap.
We use this because it's a CDN that sits in front of our static resources hosted in S3. It makes it so that users in other countries can have quick access to our portal.