Amazon CloudFront vs KeyCDN: What are the differences?
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; KeyCDN: A CDN crafted with ease and simplicity in mind - speed up your website. KeyCDN is a superfast Content Delivery Network with best prices on the market. This CDN allows you to accelerate any kind of content.
Amazon CloudFront and KeyCDN can be primarily classified as "Content Delivery Network" tools.
Some of the features offered by Amazon CloudFront are:
- Fast- Using a network of edge locations around the world, Amazon CloudFront caches copies of your static content close to viewers, lowering latency when they download your objects and giving you the high, sustained data transfer rates needed to deliver large popular objects to end users at scale.
- Simple- A single API call lets you get started distributing content from your Amazon S3 bucket or Amazon EC2 instance or other origin server through the Amazon CloudFront network.
- Designed for use with other Amazon Web Services Amazon CloudFront is designed for use with other Amazon Web Services, including Amazon S3, where you can durably store the definitive versions of your static files, and Amazon EC2, where you can run your application server for dynamically generated content.
On the other hand, KeyCDN provides the following key features:
- HTTP/2 support
- Free automated Let's Encrypt SSL
- Pay-as-you-go pricing
"Fast" is the top reason why over 245 developers like Amazon CloudFront, while over 39 developers mention "Pay-as-you-go" as the leading cause for choosing KeyCDN.
According to the StackShare community, Amazon CloudFront has a broader approval, being mentioned in 3387 company stacks & 621 developers stacks; compared to KeyCDN, which is listed in 34 company stacks and 12 developer stacks.
What is Amazon CloudFront?
What is KeyCDN?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using KeyCDN?
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
When I first built my portfolio I used GitHub for the source control and deployed directly to Netlify on a push to master. This was a perfect setup, I didn't need any knowledge about #DevOps or anything, it was all just done for me.
Over the weekend I decided I wanted to know more about how #DevOps worked so I decided to switch from Netlify to Amazon S3. Instead of creating any #Git Webhooks I decided to use Buddy for my pipeline and to run commands. Buddy is a fantastic tool, very easy to setup builds, copying the files to my Amazon S3 bucket, then running some #AWS console commands to set the
When I made these changes I also wanted to monitor my code, and make sure I was keeping up with the best practices so I implemented Code Climate to look over my code and tell me where there
other issues I've been super happy with it so far, on the free tier so its also free.
I did plan on using Amazon CloudFront for my SSL and cacheing, however it was overly complex to setup and it costs money. So I decided to go with the free tier of CloudFlare and it is amazing, best choice I've made for caching / SSL in a long time.
I recently moved my portfolio to Amazon S3 and I needed a new way to cache and SSL my site as Amazon S3 does not come with this right out of the box. I tried Amazon CloudFront as I was already on Amazon S3 I thought this would be super easy and straight forward to setup... It was not, I was unable to get this working even though I followed all the online steps and even reached out for help to Amazon.
I'd used CloudFlare in the past, and thought let me see if I can set up CloudFlare on an Amazon S3 bucket. The setup for this was so basic and easy... I had it setup with caching and SSL within 5 minutes, and it was 100% free.
Platform Update: we’ve been using the Performance Test tool provided by KeyCDN for a long time in combination with Pingdom's similar tool and the #WebpageTest and #GoogleInsight - we decided to test out KeyCDN for static asset hosting. The results for the endpoints were superfast - almost 200% faster than CloudFlare in some tests and 370% faster than imgix . So we’ve moved Washington Brown from imgix for hosting theme images, to KeyCDN for hosting all images and static assets (Font, CSS & JS). There’s a few things that we like about “Key” apart from saving $6 a month on the monthly minimum spend ($4 vs $10 for imgix). Key allow for a custom CNAME (no more advertising imgix.com in domain requests and possible SEO improvements - and easier to swap to another host down the track). Key allows JPEG/WebP image requests based on clients ‘accept’ http headers - imgix required a ?auto=format query string on each image resource request - which can break some caches. Key allows for explicitly denying cookies to be set on a zone/domain; cookies are a big strain on limited upload bandwidth so to be able to force these off is great - Cloudflare adds a cookie to every header… for “performance reasons”… but remember “if you’re getting a product something for free…”
Yesterday we moved away from using CloudFlare towards Amazon Route 53 for a few reasons. Although CloudFlare is a great platform, once you reach almost a 100% AWS Service integration, it makes it hard to still use CloudFlare in the stack. Also being able to use Aliases for DNS makes it faster because instead of doing a CNAME and an A record lookup, you will be able to receive the A records from the end services directly. We always loved working with CloudFlare , especially for DNS as we already used Amazon CloudFront for CDN. But having everything within AWS makes it "cleaner" when deploying automatically using AWS CloudFormation. All that aside, the main reason for moving towards Amazon Route 53 for DNS is the ability to do geolocation and latency based DNS responses. Doing this outside the AWS console would increase the complexity.
Using it with my webforum (9000 Users/Month / 600.000 Requests) Easy to integrate with existing documentations for all big applications, free ssl support with let's encrypt or own certificate. Ability to use own domain (like cdn.yourdomain.org). You only pay for that what you're really using (pay as you go).
Using KeyCDN already a little bit more then one year, i love it. Loadspeed improved heavily (without: 2,5-4s | with (0,5-1,2s).
Support is very fast and helpful in any situation.
And the most important thing: cheaper then others. while being much faster.
I can only recommend everyone to use KeyCDN.
But please keep this in mind, unused credits will expire after one year if there wasn't a payment for more than a year but you can retain them with any payment for another year before the expiry.
KeyCDN is a simple-to-use and reliable solution to decrease page load times around the world. In particular, I enjoy the simplicity of the dashboard provided, the CMS integration documentation, custom sub-domain configuration, and Let's Encrypt support.
As an individual user, I use KeyCDN for a variety of different personal projects, some of which may experience high traffic at peak times. I have never once had an issue with the KeyCDN service and it has served me well over the past year.
My one and only issue with KeyCDN is that there is a minimum purchase requirement and that the credits purchased will expire after one year. Still, one could rationalize KeyCDN as a yearly subscription service this way and it would still be a good deal for those who need a reliable CDN provider.
Turned out to be the best CDN of the ones we tried (including CloudFront, CacheFly, and MaxCDN). It's by far the best modern, well designed, and easy to use interface. It seems to have every feature we could need, including SPDY support (which CloudFront still lacks), an API that allows easy free cache invalidation, HTTPS SNI, and real-time logging.
It didn't seem to be very fast at first and we almost stopped using them, but it turns out they have an odd quirk where they don't cache pages that don't set a Content-Length header (which PHP pages normally don't). Once we set up a work-around for that issue, it worked very well. Hopefully that's an issue they can fix on their end eventually.
The ability to fine tune the configuration of each zone to a specific business goal. The robust set of features available at no extra cost such as: HTTP2, Custom SSL, GZip Compression, HLS optimisation. Quick addition of latest technologies such as the Brotli compression algorithm. Still have one minus, is limit of 5 zones only. Very recommend to use
I was using MaxCdn for a few years and found it too expensive for my low traffic wordpress sites. Then I found KeyCDN and found all the same features and benefits for half the price. I have been pretty happy using KeyCDN and switching over to them has been painless.
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.