Fastly vs jsDelivr: What are the differences?
Developers describe Fastly as "We're redefining content delivery". Fastly's real-time content delivery network gives you total control over your content, unprecedented access to performance analytics, and the ability to instantly update content in 150 milliseconds. On the other hand, jsDelivr is detailed as "A free Open Source CDN for webmasters and developers". Unlike the competition, jsDelivr uses multiple CDN providers, resulting in the best possible uptime and performance. We currently use MaxCDN, CloudFlare, and KeyCDN.
Fastly and jsDelivr can be categorized as "Content Delivery Network" tools.
Some of the features offered by Fastly are:
- static content delivery
- event-driven content delivery
- Dynamic Site Acceleration (DSA)
On the other hand, jsDelivr provides the following key features:
- Open Source
- Smart Load Balancing
"Real-time updates" is the top reason why over 20 developers like Fastly, while over 7 developers mention "Its fast" as the leading cause for choosing jsDelivr.
jsDelivr is an open source tool with 2.69K GitHub stars and 1.9K GitHub forks. Here's a link to jsDelivr's open source repository on GitHub.
According to the StackShare community, Fastly has a broader approval, being mentioned in 96 company stacks & 11 developers stacks; compared to jsDelivr, which is listed in 7 company stacks and 8 developer stacks.
What is Fastly?
What is jsDelivr?
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 jsDelivr?
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 my SSL cert MaxCDN was expiring on my personal site I decided it was a good time to revamp some things. Since GitHub Services is depreciated I can no longer have #CDN cache purges automated among other things. So I decided on the following: GitHub Pages, Netlify, Let's Encrypt and Jekyll. Staying the same was Bootstrap, jQuery, Grunt & #GoogleFonts.
What's awesome about GitHub Pages is that it has a #CDN (Fastly) built-in and anytime you push to master, it purges the cache instantaneously without you have to do anything special. Netlify is magic, I highly recommend it to anyone using #StaticSiteGenerators.
For the most part, everything went smoothly. The only things I had issues with were the following:
- If you want to point
wwwto GitHub Pages you need to rename the repo to
- If you edit something in the
_config.ymlyou need to restart
bundle exec jekyll sor changes won't show
- I had to disable the Grunt
htmlminmodule. I replaced it with Jekyll layout that compresses HTML for #webperf
Last but certainly not least, I made a donation to Let's Encrypt. If you use their service consider doing it too: https://letsencrypt.org/donate/
In addition to having a great service, a powerful API and a perfect uptime the one thing that's really awesome about Fastly is their support. They respond really fast, are very knowledgeable, and do everything they can to help you with your problem (and that includes 1-to-1 chat on irc, skype/hangout call, etc.). Such a great experience.
Combining the speed and reliability of multiple CDN's (plus additional servers) - this is the future of content distribution
Incredible. Lets us cache dynamic pages. Makes other CDNs feel like unwieldy beasts. Support is second to none.