Alternatives to ClouDNS logo

Alternatives to ClouDNS

CloudFlare, Amazon CloudFront, Amazon Route 53, DNS Made Easy, and Google Cloud DNS are the most popular alternatives and competitors to ClouDNS.
13
35
+ 1
0

What is ClouDNS and what are its top alternatives?

It is the biggest European provider of global managed DNS services, including GeoDNS, Anycast DNS and DDoS protected DNS. It also offers Domain names and SSL Certificates,
ClouDNS is a tool in the Content Delivery Network category of a tech stack.
ClouDNS is an open source tool with GitHub stars and GitHub forks. Here’s a link to ClouDNS's open source repository on GitHub

Top Alternatives to ClouDNS

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

  • Amazon Route 53
    Amazon Route 53

    Amazon Route 53 is designed to give developers and businesses an extremely reliable and cost effective way to route end users to Internet applications by translating human readable names like www.example.com into the numeric IP addresses like 192.0.2.1 that computers use to connect to each other. Route 53 effectively connects user requests to infrastructure running in Amazon Web Services (AWS) – such as an Amazon Elastic Compute Cloud (Amazon EC2) instance, an Amazon Elastic Load Balancer, or an Amazon Simple Storage Service (Amazon S3) bucket – and can also be used to route users to infrastructure outside of AWS. ...

  • DNS Made Easy
    DNS Made Easy

    DNS Made Easy is a subsidiary of Tiggee LLC, and is a world leader in providing global IP Anycast enterprise DNS services. DNS Made Easy is currently ranked the fastest provider for 8 consecutive months and the most reliable provider. ...

  • Google Cloud DNS
    Google Cloud DNS

    Use Google's infrastructure for production quality, high volume DNS serving. Your users will have reliable, low-latency access to Google's infrastructure from anywhere in the world using our network of Anycast name servers. ...

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

  • Dyn
    Dyn

    An all-in-one Managed DNS service for your registered domain names. Dyn DNS is the perfect solution for your domain name’s DNS needs, whether it is for personal or business use. It gives you complete control over your DNS zone and its associated DNS records, complete with a simple DNS management web interface. ...

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

ClouDNS alternatives & related posts

CloudFlare logo

CloudFlare

70.6K
17.7K
1.8K
The Web Performance & Security Company.
70.6K
17.7K
+ 1
1.8K
PROS OF CLOUDFLARE
  • 421
    Easy setup, great cdn
  • 274
    Free ssl
  • 199
    Easy setup
  • 188
    Security
  • 180
    Ssl
  • 97
    Great cdn
  • 77
    Optimizer
  • 71
    Simple
  • 44
    Great UI
  • 28
    Great js cdn
  • 12
    HTTP/2 Support
  • 12
    Apps
  • 12
    DNS Analytics
  • 12
    AutoMinify
  • 9
    Rocket Loader
  • 9
    Ipv6
  • 9
    Easy
  • 8
    IPv6 "One Click"
  • 7
    Amazing performance
  • 7
    API
  • 7
    Cheapest SSL
  • 7
    Fantastic CDN service
  • 7
    Nice DNS
  • 7
    SSHFP
  • 7
    Free GeoIP
  • 6
    DNSSEC
  • 6
    Free and reliable, Faster then anyone else
  • 6
    SPDY
  • 5
    Asynchronous resource loading
  • 4
    Global Load Balancing
  • 4
    Ubuntu
  • 4
    Easy Use
  • 4
    Performance
  • 2
    Support for SSHFP records
  • 2
    CDN
  • 1
    Registrar
  • 1
    HTTPS3/Quic
  • 1
    Web3
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

19.4K
9.1K
935
Content delivery with low latency and high data transfer speeds
19.4K
9.1K
+ 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.6M 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.5M 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
Amazon Route 53 logo

Amazon Route 53

12.3K
7.7K
678
A highly available and scalable Domain Name System (DNS) web service.
12.3K
7.7K
+ 1
678
PROS OF AMAZON ROUTE 53
  • 185
    High-availability
  • 148
    Simple
  • 103
    Backed by amazon
  • 76
    Fast
  • 54
    Auhtoritive dns servers are spread over different tlds
  • 29
    One stop solution for all our cloud needs
  • 26
    Easy setup and monitoring
  • 20
    Low-latency
  • 17
    Flexible
  • 15
    Secure
  • 3
    API available
  • 1
    Dynamically setup new clients
  • 1
    Easily add client DNS entries.
CONS OF AMAZON ROUTE 53
  • 2
    SLOW
  • 2
    Geo-based routing only works with AWS zones
  • 1
    Restrictive rate limit

related Amazon Route 53 posts

Ganesa Vijayakumar
Full Stack Coder | Technical Lead · | 19 upvotes · 3M views

I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

As per my work experience and knowledge, I have chosen the followings stacks to this mission.

UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

Happy Coding! Suggestions are welcome! :)

Thanks, Ganesa

See more
Deep Shah
Software Engineer at Amazon · | 6 upvotes · 245.9K views

I only know Java and so thinking of building a web application in the following order. I need some help on what alternatives I can choose. Open to replace components, services, or infrastructure.

  • Frontend: AngularJS, Bootstrap
  • Web Framework: Spring Boot
  • Database: Amazon DynamoDB
  • Authentication: Auth0
  • Deployment: Amazon EC2 Container Service
  • Local Testing: Docker
  • Marketing: Mailchimp (Separately Export from Auth0)
  • Website Domain: GoDaddy
  • Routing: Amazon Route 53

PS: Open to exploring options of going completely native ( AWS Lambda, AWS Security but have to learn all)

See more
DNS Made Easy logo

DNS Made Easy

2.6K
65
20
DNS performance, reliability, and security have never been easier.
2.6K
65
+ 1
20
PROS OF DNS MADE EASY
  • 10
    Speed
  • 5
    Anycast
  • 2
    Mature
  • 2
    Low Cost
  • 1
    Extremely Easy Interface
CONS OF DNS MADE EASY
    Be the first to leave a con

    related DNS Made Easy posts

    Google Cloud DNS logo

    Google Cloud DNS

    2.4K
    556
    44
    Reliable, resilient, low-latency DNS serving from Google’s worldwide network of Anycast DNS servers
    2.4K
    556
    + 1
    44
    PROS OF GOOGLE CLOUD DNS
    • 10
      Backed by Google
    • 7
      High-availability
    • 6
      Reliable
    • 5
      High volume
    • 4
      Anycast DNS servers
    • 4
      Inexpensive
    • 4
      High-Performance
    • 4
      Low-latency
    CONS OF GOOGLE CLOUD DNS
    • 3
      Lack of privacy
    • 2
      Backed by Google

    related Google Cloud DNS posts

    Akamai logo

    Akamai

    1.9K
    410
    0
    The leading platform for cloud, mobile, media and security across any device, anywhere.
    1.9K
    410
    + 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

        Dyn logo

        Dyn

        1.7K
        104
        24
        Managed DNS, Outsourced DNS & Anycast DNS
        1.7K
        104
        + 1
        24
        PROS OF DYN
        • 6
          API
        • 5
          Managed DNS
        • 5
          Web interface
        • 4
          Security
        • 3
          Customer Service Access
        • 1
          Fast
        CONS OF DYN
          Be the first to leave a con

          related Dyn posts

          MaxCDN logo

          MaxCDN

          1.6K
          548
          99
          Our CDN makes your site load faster!
          1.6K
          548
          + 1
          99
          PROS OF MAXCDN
          • 47
            Easy setup
          • 32
            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 · 202.4K 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