What is Amazon CloudFront?
What is CloudFlare?
Want advice about which of these to choose?Ask the StackShare community!
What tools integrate with Amazon CloudFront?
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.
I first wore my first domain cloudflare IE "https://rifqiarief.tk" until now can still be visited, I am really grateful to the cloudflare, thanks to rare to my website down cloudflare, before my website is down so often, because I'm wearing a great resource, and dilimit by my hosting party "be advised, I wear free hosting:D" now thanks to him, to my website really stable, unless it's really my full server connection my server, run faster, regardless of my location in Indonesia, unfortunately the cloudflare doesn't have a datacenter in Indonesia, if you don't believe me, please visit my website "https://rifqiarief.tk"
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.
Cloudflare sits in front of the entire site providing HTTP2 and HTTPS, which is particularly important due the large number of SVG images for the headings that need to be send down to the browser in parallel. Cloudflare also manages the DNS for DKIM TXT records, a dynamic root ALIAS record to the Heroku application, and GeoIP country headers.
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.
We use CloudFlare to protect our network from breaches as well as to reduce bandwidth on the servers themselves and therefore freeing up the bandwidth for our other projects. We also use CloudFlare for instant DNS propagation across the internet where possible.
We love the free SSL and extensive CDN network. DDoS protection is a plus. Great premium features for rapidly growing projects. Cloudflare has helped us forget about silly things like asset minification and email obfuscation.
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 CF for DNS hosting, since their AnyCast DNS provides the best latency in the business, and they support DNSSEC + IPv6. We don't use the CDN or website optimizations.
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.
lots of good stuff available for free that you don't even think about it, default configuration saves you weeks of work, painless https setup, good to kickstart projects