Alternatives to cdnjs logo

Alternatives to cdnjs

jsDelivr, npm, MaxCDN, CloudFlare, and Amazon CloudFront are the most popular alternatives and competitors to cdnjs.
99
112
+ 1
11

What is cdnjs and what are its top alternatives?

Everyone loves the Google CDN? Even Microsoft runs their own CDN. The problem is, they only host the most popular libraries. We host it all - JavaScript, CSS, SWF, images, etc! Powered by CloudFlare.
cdnjs is a tool in the Content Delivery Network category of a tech stack.
cdnjs is an open source tool with 10.1K GitHub stars and 4.5K GitHub forks. Here’s a link to cdnjs's open source repository on GitHub

Top Alternatives to cdnjs

  • jsDelivr
    jsDelivr

    jsDelivr is a free CDN for open source developers, with advanced features for javascript projects with access to NPM and Github It uses multiple CDN providers, resulting in the best possible uptime and performance. ...

  • npm
    npm

    npm is the command-line interface to the npm ecosystem. It is battle-tested, surprisingly flexible, and used by hundreds of thousands of JavaScript developers every day. ...

  • MaxCDN
    MaxCDN

    The MaxCDN Content Delivery Network efficiently delivers your site’s static file through hundreds of servers instead of slogging through a single host. This "smart route" technology distributes your content to your visitors via the city closest to them. ...

  • CloudFlare
    CloudFlare

    Cloudflare speeds up and protects millions of websites, APIs, SaaS services, and other properties connected to the Internet. ...

  • Amazon CloudFront
    Amazon CloudFront

    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
    Akamai

    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. ...

  • Incapsula
    Incapsula

    Through an application-aware, global content delivery network (CDN), Incapsula provides any website and web application with best-of-breed security, DDoS protection, load balancing and failover solutions. ...

  • Fastly
    Fastly

    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. ...

cdnjs alternatives & related posts

jsDelivr logo

jsDelivr

96
112
50
A free Open Source CDN for webmasters and developers with full JS ESM support
96
112
+ 1
50
PROS OF JSDELIVR
  • 9
    Its fast
  • 8
    Diverse POPs and support
  • 8
    Free
  • 7
    Many packages available
  • 6
    Load multiple files with single HTTP request
  • 3
    Auto-minification by changing url extension to .min.js
  • 3
    View pkg download statistics per week/month/year
  • 3
    Can add OSS packages I use
  • 2
    Worked in China
  • 1
    Easy setup, great cdn
CONS OF JSDELIVR
    Be the first to leave a con

    related jsDelivr posts

    npm logo

    npm

    131.5K
    78.8K
    1.6K
    The package manager for JavaScript.
    131.5K
    78.8K
    + 1
    1.6K
    PROS OF NPM
    • 647
      Best package management system for javascript
    • 382
      Open-source
    • 327
      Great community
    • 148
      More packages than rubygems, pypi, or packagist
    • 112
      Nice people matter
    • 6
      As fast as yarn but really free of facebook
    • 6
      Audit feature
    • 4
      Good following
    • 1
      Super fast
    • 1
      Stability
    CONS OF NPM
    • 5
      Problems with lockfiles
    • 5
      Bad at package versioning and being deterministic
    • 3
      Node-gyp takes forever
    • 1
      Super slow

    related npm posts

    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 27 upvotes · 4.7M views

    Our whole Node.js backend stack consists of the following tools:

    • Lerna as a tool for multi package and multi repository management
    • npm as package manager
    • NestJS as Node.js framework
    • TypeScript as programming language
    • ExpressJS as web server
    • Swagger UI for visualizing and interacting with the API’s resources
    • Postman as a tool for API development
    • TypeORM as object relational mapping layer
    • JSON Web Token for access token management

    The main reason we have chosen Node.js over PHP is related to the following artifacts:

    • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
    • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
    • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
    • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
    See more
    Johnny Bell

    So when starting a new project you generally have your go to tools to get your site up and running locally, and some scripts to build out a production version of your site. Create React App is great for that, however for my projects I feel as though there is to much bloat in Create React App and if I use it, then I'm tied to React, which I love but if I want to switch it up to Vue or something I want that flexibility.

    So to start everything up and running I clone my personal Webpack boilerplate - This is still in Webpack 3, and does need some updating but gets the job done for now. So given the name of the repo you may have guessed that yes I am using Webpack as my bundler I use Webpack because it is so powerful, and even though it has a steep learning curve once you get it, its amazing.

    The next thing I do is make sure my machine has Node.js configured and the right version installed then run Yarn. I decided to use Yarn because when I was building out this project npm had some shortcomings such as no .lock file. I could probably move from Yarn to npm but I don't really see any point really.

    I use Babel to transpile all of my #ES6 to #ES5 so the browser can read it, I love Babel and to be honest haven't looked up any other transpilers because Babel is amazing.

    Finally when developing I have Prettier setup to make sure all my code is clean and uniform across all my JS files, and ESLint to make sure I catch any errors or code that could be optimized.

    I'm really happy with this stack for my local env setup, and I'll probably stick with it for a while.

    See more
    MaxCDN logo

    MaxCDN

    1.6K
    553
    100
    Our CDN makes your site load faster!
    1.6K
    553
    + 1
    100
    PROS OF MAXCDN
    • 47
      Easy setup
    • 33
      Speed to my clients
    • 15
      Great service & Customer Support
    • 5
      Shared and Affordable SSL
    CONS OF MAXCDN
      Be the first to leave a con

      related MaxCDN posts

      Justin Dorfman
      Open Source Program Manager at Reblaze · | 4 upvotes · 233.9K views

      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

      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
      CloudFlare logo

      CloudFlare

      75.8K
      21.9K
      1.8K
      The Web Performance & Security Company.
      75.8K
      21.9K
      + 1
      1.8K
      PROS OF CLOUDFLARE
      • 423
        Easy setup, great cdn
      • 277
        Free ssl
      • 199
        Easy setup
      • 190
        Security
      • 180
        Ssl
      • 98
        Great cdn
      • 77
        Optimizer
      • 71
        Simple
      • 44
        Great UI
      • 28
        Great js cdn
      • 12
        Apps
      • 12
        HTTP/2 Support
      • 12
        DNS Analytics
      • 12
        AutoMinify
      • 9
        Rocket Loader
      • 9
        Ipv6
      • 9
        Easy
      • 8
        IPv6 "One Click"
      • 8
        Fantastic CDN service
      • 7
        DNSSEC
      • 7
        Nice DNS
      • 7
        SSHFP
      • 7
        Free GeoIP
      • 7
        Amazing performance
      • 7
        API
      • 7
        Cheapest SSL
      • 6
        SPDY
      • 6
        Free and reliable, Faster then anyone else
      • 5
        Ubuntu
      • 5
        Asynchronous resource loading
      • 4
        Global Load Balancing
      • 4
        Performance
      • 4
        Easy Use
      • 3
        CDN
      • 2
        Registrar
      • 2
        Support for SSHFP records
      • 1
        Web3
      • 1
        Прохси
      • 1
        HTTPS3/Quic
      CONS OF CLOUDFLARE
      • 2
        No support for SSHFP records
      • 2
        Expensive when you exceed their fair usage limits

      related CloudFlare posts

      Johnny Bell

      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

      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
      Amazon CloudFront logo

      Amazon CloudFront

      21.2K
      10.5K
      935
      Content delivery with low latency and high data transfer speeds
      21.2K
      10.5K
      + 1
      935
      PROS OF AMAZON CLOUDFRONT
      • 245
        Fast
      • 166
        Cdn
      • 157
        Compatible with other aws services
      • 125
        Simple
      • 108
        Global
      • 41
        Cheap
      • 36
        Cost-effective
      • 27
        Reliable
      • 19
        One stop solution
      • 9
        Elastic
      • 1
        Object store
      • 1
        HTTP/2 Support
      CONS OF AMAZON CLOUDFRONT
      • 3
        UI could use some work
      • 1
        Invalidations take so long

      related Amazon CloudFront posts

      Russel Werner
      Lead Engineer at StackShare · | 32 upvotes · 1.9M views

      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
      Principal Software Engineer at Tophatter · | 16 upvotes · 3.1M views

      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.9K
      432
      0
      The leading platform for cloud, mobile, media and security across any device, anywhere.
      1.9K
      432
      + 1
      0
      PROS OF AKAMAI
        Be the first to leave a pro
        CONS OF AKAMAI
          Be the first to leave a con

          related Akamai posts

          Incapsula logo

          Incapsula

          1.3K
          72
          5
          Cloud-based service that makes websites safer, faster and more reliable.
          1.3K
          72
          + 1
          5
          PROS OF INCAPSULA
          • 5
            Best of them
          CONS OF INCAPSULA
            Be the first to leave a con

            related Incapsula posts

            Fastly logo

            Fastly

            1.1K
            501
            153
            We're redefining content delivery.
            1.1K
            501
            + 1
            153
            PROS OF FASTLY
            • 28
              Real-time updates
            • 26
              Fastest CDN
            • 22
              Powerful API
            • 20
              Great support
            • 14
              Great customer support
            • 7
              Instant Purging
            • 7
              Custom VCL
            • 6
              Good pricing
            • 6
              Tag-based Purging
            • 5
              HTTP/2 Support
            • 4
              Speed & functionality
            • 4
              Image processing on demande (Fastly IO)
            • 4
              Best CDN
            CONS OF FASTLY
            • 1
              Minimum $50/mo spend

            related Fastly posts

            Justin Dorfman
            Open Source Program Manager at Reblaze · | 4 upvotes · 233.9K views

            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