Alternatives to EdgeCast logo

Alternatives to EdgeCast

Akamai, CloudFlare, Incapsula, Amazon CloudFront, and MaxCDN are the most popular alternatives and competitors to EdgeCast.
93
22
+ 1
0

What is EdgeCast and what are its top alternatives?

EdgeCast is a content delivery network (CDN) that helps companies accelerate and deliver static and dynamic content to end users around the world. Major customers include Yahoo!, Tumblr, Pinterest, Wordpress, and Imgur. The company has about 4,500 customers (as of June 2012) and carries about 5% of the world’s internet traffic.
EdgeCast is a tool in the Content Delivery Network category of a tech stack.

EdgeCast alternatives & related posts

Akamai logo

Akamai

1.7K
107
0
1.7K
107
+ 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
    EdgeCast logo
    EdgeCast
    CloudFlare logo

    CloudFlare

    51.4K
    3.1K
    1.5K
    51.4K
    3.1K
    + 1
    1.5K
    The Web Performance & Security Company.
    CloudFlare logo
    CloudFlare
    VS
    EdgeCast logo
    EdgeCast

    related CloudFlare posts

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

    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 · 24.9K views
    CloudFlare
    CloudFlare
    Amazon CloudFront
    Amazon CloudFront
    Amazon S3
    Amazon S3

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

    Incapsula

    1.3K
    18
    2
    1.3K
    18
    + 1
    2
    Cloud-based service that makes websites safer, faster and more reliable.
    Incapsula logo
    Incapsula
    VS
    EdgeCast logo
    EdgeCast
    Amazon CloudFront logo

    Amazon CloudFront

    10.6K
    2.8K
    935
    10.6K
    2.8K
    + 1
    935
    Content delivery with low latency and high data transfer speeds
    Amazon CloudFront logo
    Amazon CloudFront
    VS
    EdgeCast logo
    EdgeCast

    related Amazon CloudFront posts

    Julien DeFrance
    Julien DeFrance
    Full Stack Engineering Manager at ValiMail · | 16 upvotes · 263.6K views
    atSmartZipSmartZip
    Amazon DynamoDB
    Amazon DynamoDB
    Ruby
    Ruby
    Node.js
    Node.js
    AWS Lambda
    AWS Lambda
    New Relic
    New Relic
    Amazon Elasticsearch Service
    Amazon Elasticsearch Service
    Elasticsearch
    Elasticsearch
    Superset
    Superset
    Amazon Quicksight
    Amazon Quicksight
    Amazon Redshift
    Amazon Redshift
    Zapier
    Zapier
    Segment
    Segment
    Amazon CloudFront
    Amazon CloudFront
    Memcached
    Memcached
    Amazon ElastiCache
    Amazon ElastiCache
    Amazon RDS for Aurora
    Amazon RDS for Aurora
    MySQL
    MySQL
    Amazon RDS
    Amazon RDS
    Amazon S3
    Amazon S3
    Docker
    Docker
    Capistrano
    Capistrano
    AWS Elastic Beanstalk
    AWS Elastic Beanstalk
    Rails API
    Rails API
    Rails
    Rails
    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
    Russel Werner
    Russel Werner
    Lead Engineer at StackShare · | 15 upvotes · 165.5K views
    atStackShareStackShare
    Redis
    Redis
    CircleCI
    CircleCI
    Webpack
    Webpack
    Amazon CloudFront
    Amazon CloudFront
    Amazon S3
    Amazon S3
    GitHub
    GitHub
    Heroku
    Heroku
    Rails
    Rails
    Node.js
    Node.js
    Apollo
    Apollo
    Glamorous
    Glamorous
    React
    React
    #FrontEndRepoSplit
    #Microservices
    #SSR
    #StackDecisionsLaunch

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

    MaxCDN

    1.5K
    466
    99
    1.5K
    466
    + 1
    99
    Our CDN makes your site load faster!
    MaxCDN logo
    MaxCDN
    VS
    EdgeCast logo
    EdgeCast

    related MaxCDN posts

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

    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 · 5.1K views
    atTrackJSTrackJS
    MaxCDN
    MaxCDN
    Amazon CloudFront
    Amazon CloudFront

    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

    related Fastly posts

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

    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

    related KeyCDN posts

    RMW Web Publishing
    RMW Web Publishing
    Web Development at RMW Web Publishing · | 4 upvotes · 9.9K views
    atWashington BrownWashington Brown
    imgix
    imgix
    CloudFlare
    CloudFlare
    Pingdom
    Pingdom
    KeyCDN
    KeyCDN
    #GoogleInsight
    #WebpageTest

    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…”

    See more
    cdnjs logo

    cdnjs

    66
    59
    10
    66
    59
    + 1
    10
    An open source community driven Javascript CDN
    cdnjs logo
    cdnjs
    VS
    EdgeCast logo
    EdgeCast
    Google Cloud CDN logo

    Google Cloud CDN

    32
    37
    1
    32
    37
    + 1
    1
    Low-latency, low-cost content delivery using Google's global network
    Google Cloud CDN logo
    Google Cloud CDN
    VS
    EdgeCast logo
    EdgeCast
    CacheFly logo

    CacheFly

    15
    6
    0
    15
    6
    + 1
    0
    A leading content delivery network provider based in Chicago, IL
      Be the first to leave a pro
      CacheFly logo
      CacheFly
      VS
      EdgeCast logo
      EdgeCast
      Azure CDN logo

      Azure CDN

      13
      5
      0
      13
      5
      + 1
      0
      A global CDN solution for delivering high-bandwidth content
        Be the first to leave a pro
        Azure CDN logo
        Azure CDN
        VS
        EdgeCast logo
        EdgeCast
        CDNify logo

        CDNify

        12
        11
        5
        12
        11
        + 1
        5
        Content Delivery Network for tech startups, digital agencies & developers
        CDNify logo
        CDNify
        VS
        EdgeCast logo
        EdgeCast
        CDN77.com logo

        CDN77.com

        8
        6
        0
        8
        6
        + 1
        0
        Fast, transparent and flexible content delivery provider
          Be the first to leave a pro
          CDN77.com logo
          CDN77.com
          VS
          EdgeCast logo
          EdgeCast
          Cloudflare CDN logo

          Cloudflare CDN

          6
          3
          0
          6
          3
          + 1
          0
          Ultra-fast static and dynamic content delivery
            Be the first to leave a pro
            Cloudflare CDN logo
            Cloudflare CDN
            VS
            EdgeCast logo
            EdgeCast
            BunnyCDN logo

            BunnyCDN

            5
            1
            0
            5
            1
            + 1
            0
            A super cheap, but lightning fast CDN to speed up your website.
              Be the first to leave a pro
              BunnyCDN logo
              BunnyCDN
              VS
              EdgeCast logo
              EdgeCast
              Peer5 logo

              Peer5

              3
              17
              0
              3
              17
              + 1
              0
              Serverless CDN
                Be the first to leave a pro
                Peer5 logo
                Peer5
                VS
                EdgeCast logo
                EdgeCast
                ClouDNS logo

                ClouDNS

                3
                0
                0
                3
                0
                + 1
                0
                Makes your DNS faster and secure with Global Anycast DNS Network
                  Be the first to leave a pro
                  ClouDNS logo
                  ClouDNS
                  VS
                  EdgeCast logo
                  EdgeCast
                  Level 3 CDN logo

                  Level 3 CDN

                  3
                  5
                  0
                  3
                  5
                  + 1
                  0
                  Level 3’s CDN helps you succeed by leveraging our network scalability, global footprint and proven customer service.
                    Be the first to leave a pro
                    Level 3 CDN logo
                    Level 3 CDN
                    VS
                    EdgeCast logo
                    EdgeCast
                    CDNetworks logo

                    CDNetworks

                    3
                    1
                    0
                    3
                    1
                    + 1
                    0
                    A full-service content delivery network which provides technology
                      Be the first to leave a pro
                      CDNetworks logo
                      CDNetworks
                      VS
                      EdgeCast logo
                      EdgeCast