Alternatives to jsDelivr logo

Alternatives to jsDelivr

cdnjs, CloudFlare, Statically, Amazon CloudFront, and Akamai are the most popular alternatives and competitors to jsDelivr.
41
52
+ 1
43

What is jsDelivr and what are its top alternatives?

Unlike the competition, jsDelivr uses multiple CDN providers, resulting in the best possible uptime and performance. We currently use MaxCDN, CloudFlare, and KeyCDN.
jsDelivr is a tool in the Content Delivery Network category of a tech stack.
jsDelivr is an open source tool with 3.1K GitHub stars and 1.9K GitHub forks. Here鈥檚 a link to jsDelivr's open source repository on GitHub

jsDelivr alternatives & related posts

cdnjs logo

cdnjs

70
67
10
70
67
+ 1
10
An open source community driven Javascript CDN
cdnjs logo
cdnjs
VS
jsDelivr logo
jsDelivr
CloudFlare logo

CloudFlare

55.1K
6.3K
1.5K
55.1K
6.3K
+ 1
1.5K
The Web Performance & Security Company.
CloudFlare logo
CloudFlare
VS
jsDelivr logo
jsDelivr

related CloudFlare posts

Johnny Bell
Johnny Bell
Senior Software Engineer at StackShare | 11 upvotes 153K views
GitHub
GitHub
Netlify
Netlify
Amazon S3
Amazon S3
Buddy
Buddy
Amazon CloudFront
Amazon CloudFront
CloudFlare
CloudFlare
Code Climate
Code Climate
#Devops
#Webpack
#Git
#Gzip

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.

One of the issues I had with Netlify was I wanted to gzip my JavaScript files, I had this setup in my #Webpack file, however Netlify didn't offer an easy way to set this.

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 content-encoding of the JavaScript files. - Buddy is also free if you only have a few pipelines, so I didn't need to pay anything 馃馃徎.

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 code smells, issues, and 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.

See more
Johnny Bell
Johnny Bell
Senior Software Engineer at StackShare | 7 upvotes 80.4K views
Amazon S3
Amazon S3
Amazon CloudFront
Amazon CloudFront
CloudFlare
CloudFlare

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.

See more
Statically logo

Statically

3
7
0
3
7
+ 1
0
A free CDN for Git repositories, WordPress, images and more
    Be the first to leave a pro
    Statically logo
    Statically
    VS
    jsDelivr logo
    jsDelivr
    Amazon CloudFront logo

    Amazon CloudFront

    12.6K
    4.5K
    935
    12.6K
    4.5K
    + 1
    935
    Content delivery with low latency and high data transfer speeds
    Amazon CloudFront logo
    Amazon CloudFront
    VS
    jsDelivr logo
    jsDelivr

    related Amazon CloudFront posts

    Russel Werner
    Russel Werner
    Lead Engineer at StackShare | 27 upvotes 767.5K views
    atStackShareStackShare
    React
    React
    Glamorous
    Glamorous
    Apollo
    Apollo
    Node.js
    Node.js
    Rails
    Rails
    Heroku
    Heroku
    GitHub
    GitHub
    Amazon S3
    Amazon S3
    Amazon CloudFront
    Amazon CloudFront
    Webpack
    Webpack
    CircleCI
    CircleCI
    Redis
    Redis
    #StackDecisionsLaunch
    #SSR
    #Microservices
    #FrontEndRepoSplit

    StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

    Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

    #StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

    See more
    Julien DeFrance
    Julien DeFrance
    Principal Software Engineer at Tophatter | 16 upvotes 1.3M views
    atSmartZipSmartZip
    Rails
    Rails
    Rails API
    Rails API
    AWS Elastic Beanstalk
    AWS Elastic Beanstalk
    Capistrano
    Capistrano
    Docker
    Docker
    Amazon S3
    Amazon S3
    Amazon RDS
    Amazon RDS
    MySQL
    MySQL
    Amazon RDS for Aurora
    Amazon RDS for Aurora
    Amazon ElastiCache
    Amazon ElastiCache
    Memcached
    Memcached
    Amazon CloudFront
    Amazon CloudFront
    Segment
    Segment
    Zapier
    Zapier
    Amazon Redshift
    Amazon Redshift
    Amazon Quicksight
    Amazon Quicksight
    Superset
    Superset
    Elasticsearch
    Elasticsearch
    Amazon Elasticsearch Service
    Amazon Elasticsearch Service
    New Relic
    New Relic
    AWS Lambda
    AWS Lambda
    Node.js
    Node.js
    Ruby
    Ruby
    Amazon DynamoDB
    Amazon DynamoDB
    Algolia
    Algolia

    Back in 2014, I was given an opportunity to re-architect SmartZip Analytics platform, and flagship product: SmartTargeting. This is a SaaS software helping real estate professionals keeping up with their prospects and leads in a given neighborhood/territory, finding out (thanks to predictive analytics) who's the most likely to list/sell their home, and running cross-channel marketing automation against them: direct mail, online ads, email... The company also does provide Data APIs to Enterprise customers.

    I had inherited years and years of technical debt and I knew things had to change radically. The first enabler to this was to make use of the cloud and go with AWS, so we would stop re-inventing the wheel, and build around managed/scalable services.

    For the SaaS product, we kept on working with Rails as this was what my team had the most knowledge in. We've however broken up the monolith and decoupled the front-end application from the backend thanks to the use of Rails API so we'd get independently scalable micro-services from now on.

    Our various applications could now be deployed using AWS Elastic Beanstalk so we wouldn't waste any more efforts writing time-consuming Capistrano deployment scripts for instance. Combined with Docker so our application would run within its own container, independently from the underlying host configuration.

    Storage-wise, we went with Amazon S3 and ditched any pre-existing local or network storage people used to deal with in our legacy systems. On the database side: Amazon RDS / MySQL initially. Ultimately migrated to Amazon RDS for Aurora / MySQL when it got released. Once again, here you need a managed service your cloud provider handles for you.

    Future improvements / technology decisions included:

    Caching: Amazon ElastiCache / Memcached CDN: Amazon CloudFront Systems Integration: Segment / Zapier Data-warehousing: Amazon Redshift BI: Amazon Quicksight / Superset Search: Elasticsearch / Amazon Elasticsearch Service / Algolia Monitoring: New Relic

    As our usage grows, patterns changed, and/or our business needs evolved, my role as Engineering Manager then Director of Engineering was also to ensure my team kept on learning and innovating, while delivering on business value.

    One of these innovations was to get ourselves into Serverless : Adopting AWS Lambda was a big step forward. At the time, only available for Node.js (Not Ruby ) but a great way to handle cost efficiency, unpredictable traffic, sudden bursts of traffic... Ultimately you want the whole chain of services involved in a call to be serverless, and that's when we've started leveraging Amazon DynamoDB on these projects so they'd be fully scalable.

    See more
    Akamai logo

    Akamai

    1.8K
    239
    0
    1.8K
    239
    + 1
    0
    The leading platform for cloud, mobile, media and security across any device, anywhere.
      Be the first to leave a pro
      Akamai logo
      Akamai
      VS
      jsDelivr logo
      jsDelivr
      MaxCDN logo

      MaxCDN

      1.6K
      524
      99
      1.6K
      524
      + 1
      99
      Our CDN makes your site load faster!
      MaxCDN logo
      MaxCDN
      VS
      jsDelivr logo
      jsDelivr

      related MaxCDN posts

      Justin Dorfman
      Justin Dorfman
      Developer Evangelist at StackShare | 4 upvotes 109.3K views
      MaxCDN
      MaxCDN
      GitHub Pages
      GitHub Pages
      Netlify
      Netlify
      Let's Encrypt
      Let's Encrypt
      Jekyll
      Jekyll
      Bootstrap
      Bootstrap
      jQuery
      jQuery
      Grunt
      Grunt
      Fastly
      Fastly
      #CDN
      #GoogleFonts
      #StaticSiteGenerators
      #Webperf

      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 www to GitHub Pages you need to rename the repo to www
      • If you edit something in the _config.yml you need to restart bundle exec jekyll s or changes won't show
      • I had to disable the Grunt htmlmin module. 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/

      See more
      Todd Gardner
      Todd Gardner
      President at TrackJS | 3 upvotes 30.6K views
      atTrackJSTrackJS
      Amazon CloudFront
      Amazon CloudFront
      MaxCDN
      MaxCDN

      We migrated the hosting of our CDN, which is used to serve the JavaScript Error collection agent, from Amazon CloudFront to MaxCDN. During our test, we found MaxCDN to be more reliable and less expensive for serving he file.

      The reports and controls were also considerably better.

      See more
      Incapsula logo

      Incapsula

      1.3K
      44
      2
      1.3K
      44
      + 1
      2
      Cloud-based service that makes websites safer, faster and more reliable.
      Incapsula logo
      Incapsula
      VS
      jsDelivr logo
      jsDelivr

      related Fastly posts

      Justin Dorfman
      Justin Dorfman
      Developer Evangelist at StackShare | 4 upvotes 109.3K views
      MaxCDN
      MaxCDN
      GitHub Pages
      GitHub Pages
      Netlify
      Netlify
      Let's Encrypt
      Let's Encrypt
      Jekyll
      Jekyll
      Bootstrap
      Bootstrap
      jQuery
      jQuery
      Grunt
      Grunt
      Fastly
      Fastly
      #CDN
      #GoogleFonts
      #StaticSiteGenerators
      #Webperf

      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 www to GitHub Pages you need to rename the repo to www
      • If you edit something in the _config.yml you need to restart bundle exec jekyll s or changes won't show
      • I had to disable the Grunt htmlmin module. 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/

      See more