Alternatives to Akamai logo

Alternatives to Akamai

CloudFlare, Fastly, Google Cloud CDN, Apigee, and Imperva are the most popular alternatives and competitors to Akamai.
1.9K
377
+ 1
0

What is Akamai and what are its top alternatives?

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.
Akamai is a tool in the Content Delivery Network category of a tech stack.

Top Alternatives to Akamai

  • CloudFlare

    CloudFlare

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

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

  • Google Cloud CDN

    Google Cloud CDN

    Google Cloud CDN leverages Google's globally distributed edge caches to accelerate content delivery for websites and applications served out of Google Compute Engine. Cloud CDN lowers network latency, offloads origins, and reduces serving costs. Once you've set up HTTP(S) Load Balancing, simply enable Cloud CDN with a single checkbox. ...

  • Apigee

    Apigee

    API management, design, analytics, and security are at the heart of modern digital architecture. The Apigee intelligent API platform is a complete solution for moving business to the digital world. ...

  • Imperva

    Imperva

    It provides complete cyber security by protecting what really matters most鈥攜our data and applications鈥攚hether on-premises or in the cloud. ...

  • F5

    F5

    It powers apps from development through their entire life cycle, so our customers can deliver differentiated, high-performing, and secure digital experiences. ...

  • Zscaler

    Zscaler

    It is a global cloud-based information security company that provides Internet security, web security, firewalls, sandboxing, SSL inspection, antivirus, vulnerability management and granular control of user activity in cloud computing, mobile and Internet of things environments. ...

  • 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 alternatives & related posts

CloudFlare logo

CloudFlare

66.8K
14.7K
1.7K
The Web Performance & Security Company.
66.8K
14.7K
+ 1
1.7K
PROS OF CLOUDFLARE
  • 421
    Easy setup, great cdn
  • 274
    Free ssl
  • 196
    Easy setup
  • 184
    Security
  • 179
    Ssl
  • 94
    Great cdn
  • 76
    Optimizer
  • 69
    Simple
  • 43
    Great UI
  • 27
    Great js cdn
  • 11
    AutoMinify
  • 11
    DNS Analytics
  • 11
    Apps
  • 11
    HTTP/2 Support
  • 8
    Ipv6
  • 8
    Easy
  • 8
    Rocket Loader
  • 7
    IPv6 "One Click"
  • 6
    SSHFP
  • 6
    Nice DNS
  • 6
    Fantastic CDN service
  • 6
    Cheapest SSL
  • 6
    Amazing performance
  • 6
    API
  • 6
    Free GeoIP
  • 5
    SPDY
  • 5
    DNSSEC
  • 5
    Free and reliable, Faster then anyone else
  • 4
    Asynchronous resource loading
  • 4
    Ip
  • 3
    Performance
  • 3
    Ubuntu
  • 3
    Easy Use
  • 3
    Global Load Balancing
  • 1
    Mtn
  • 1
    Maker
  • 1
    Support for SSHFP records
  • 1
    CDN
CONS OF CLOUDFLARE
  • 1
    No support for SSHFP records

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

Fastly

1K
443
137
We're redefining content delivery.
1K
443
+ 1
137
PROS OF FASTLY
  • 27
    Real-time updates
  • 23
    Fastest CDN
  • 20
    Powerful API
  • 19
    Great support
  • 13
    Great customer support
  • 6
    Custom VCL
  • 6
    Instant Purging
  • 5
    Tag-based Purging
  • 5
    Good pricing
  • 4
    HTTP/2 Support
  • 3
    Best CDN
  • 3
    Image processing on demande (Fastly IO)
  • 3
    Speed & functionality
CONS OF FASTLY
  • 1
    Minimum $50/mo spend

related Fastly posts

Justin Dorfman
Open Source Program Manager at Reblaze | 4 upvotes 路 189K 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
Google Cloud CDN logo

Google Cloud CDN

63
188
2
Low-latency, low-cost content delivery using Google's global network
63
188
+ 1
2
PROS OF GOOGLE CLOUD CDN
  • 2
    Extremely Fast
CONS OF GOOGLE CLOUD CDN
  • 2
    Very expensive not for newbies

related Google Cloud CDN posts

Apigee logo

Apigee

184
527
27
Intelligent and complete API platform
184
527
+ 1
27
PROS OF APIGEE
  • 11
    Highly scalable and secure API Management Platform
  • 5
    Quick jumpstart
  • 5
    Good documentation
  • 3
    Fast and adjustable caching
  • 3
    Easy to use
CONS OF APIGEE
  • 8
    Expensive

related Apigee posts

A Luthra
VP Software Engrg at Reliant | 3 upvotes 路 442K views
Shared insights
on
ApigeeApigeeAmazon API GatewayAmazon API Gateway

Amazon API Gateway vs Apigee. How do they compare as an API Gateway? What is the equivalent functionality, similarities, and differences moving from Apigee API GW to AWS API GW?

See more
Imperva logo

Imperva

5
5
0
Provides complete cyber security by protecting what really matters most
5
5
+ 1
0
PROS OF IMPERVA
    Be the first to leave a pro
    CONS OF IMPERVA
      Be the first to leave a con

      related Imperva posts

      F5 logo

      F5

      18
      17
      0
      Secure application delivery
      18
      17
      + 1
      0
      PROS OF F5
        Be the first to leave a pro
        CONS OF F5
          Be the first to leave a con

          related F5 posts

          Zscaler logo

          Zscaler

          21
          53
          0
          Secure, simplify and transform IT with cloud security platform
          21
          53
          + 1
          0
          PROS OF ZSCALER
            Be the first to leave a pro
            CONS OF ZSCALER
              Be the first to leave a con

              related Zscaler posts

              Amazon CloudFront logo

              Amazon CloudFront

              17.6K
              7.9K
              935
              Content delivery with low latency and high data transfer speeds
              17.6K
              7.9K
              + 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 | 30 upvotes 路 1.5M 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 路 2.4M 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