CloudFront is the content delivery network (CDN) from Amazon Web Services.
$0.02
Oracle Dyn Managed DNS
Score 8.8 out of 10
Mid-Size Companies (51-1,000 employees)
Oracle Dyn DNS (domain name system) is an infrastructure-as-a-service that is touted by Oracle Dyne as one of the highest performance global networks existent. It is available as a managed DNS with secondary DNS available for more reliable business continuity on higher service tiers.
CloudFronts beats everyone with their free 1 TB monthly bandwidth usage. And if we compare speed and latency of CloudFront with the BunnyCDN and CloudFare, CloudFront is was faster than them. With CloudFront, we get options like signed URL and signed cookies which prevent our …
Have used the IBM Cloud Content Delivery Network for a very short time span like a couple of weeks. Both the setup as well as interactions with other services are a little complicated or not straightforward when compared to AWS. Also, IBM cloud has less number of edge locations …
Cloudfront is one of the oldest CDN with presence in a lot of locations. This really helps in making the content load faster in all the locations globally. Other products have also caught up with this but still AWS has a lot of other services which can be connected with the CDN …
Amazon has always been creative and leading, and I have been using its services for years. They are very reassuring and have fast and responsive support--you can call them from any time zone to respond quickly. High security on servers, open hands on changes, and increasing and …
We use a great set of AWS features and it was easy to implement Amazon CloudFront. It fulfills our needs, and the learning curve was not difficult given the AWS configuration we already have.
Because our products are built and utilize other AWS features, it was easiest to implement Amazon CloudFront based on initial environment configuration. Other CDNs were easier to get started with but required manual intervention to update overtime.
If you are using other AWS services, then no other CDN can compete with AWS CloudFront. Its integration with WAF, Route53, ACM allow it to provide a whole ecosystem for building websites and using a CDN. It gives developers access to inexpensive, pay-as-you-go pricing. …
We ended up selecting CloudFront because we were already using an Amazon stack. To be honest, since we were already in the ecosystem there was little reason to deviate once we saw pricing was comparable.
We went with CloudFront primarily because we have all of our other services with Amazon already. We are using EC2, S3, Elastic Beanstalk, and are very familiar with the interface. It did not disappoint.
CloudFront is well-suited for a particular use case with its native tie-ins to other Amazon/AWS services, like S3. If choosing from a platform-specific CDN, we tend to go with whichever CDN is available for use on that platform (e.g. Google or Azure). In rare cases we might …
Cloudflare is another great CDN service. It comes with a lot of things set up of the box for you, and gives you a basic and reasonable set up straight away. It also has a free-tier for smaller sites. Cloudflare doesn't quite have the same level of configurability, however. …
Amazon CloudFront free Tier allows up to 50 GB of data transfer per month which is not there in any of the above. Amazon CloudFront provides detailed reporting around the most frequently used objects, monitoring and usage charts. Amazon CloudFront is suitable to help you …
As our organization had an ample amount of DNS to manage, it was quite inconvenient when it comes to Amazon Route 53 or any other alternatives as the change propagation time was pretty much high as compared to Oracle Dyn Managed DNS. And when it comes to the huge customer base …
Oracle Dyn Managed DNS is much simpler to use and has no ads. Using other companies, you sometimes have pop-up ads and have difficulty getting to the zone and managing the DNS records. Since Dyn Managed DNS is only DNS, you're in, out, done. No time is wasted trying to …
Name.com also has DNS management but I think Dyn does a much better job. The layout of the website is more intuitive and actually loads and performs much better. Overall if you have a domain name on name.com that you use, I would transfer it to Dyn as its easier to use.
We have been using Dyn since before it was acquired by Oracle and has never failed us. I have used other DNS providers in the past, mostly from the domain registrars, but those have lacked features and availability of certain types of DNS records. In addition, the management …
We selected it for stability. It has a way better UI than UltraDNS. Oracle Dyn has a clear user interface without bloatware, and the actions don't surprise you.
Route 53 - Their main benefit is the integration with the rest of the Amazon Web Services suite, something other …
We actually use both providers, but Dyn is our primary.
In terms of feature set, both companies have very similar offerings. We've found Verisign's UI and documentation to be overall more usable, but Dyn's GeoDNS management is far simpler. Both companies offer an API, and while …
We have not evaluated any alternatives recently. Previously we managed DNS at a registrar, and their lack of options made us realize we needed to find something better.
Amazon CloudFront is best suited when there is a need of speed in serving static and dynanic web contents of a web application. If the content is already in that edge location, CloudFront delivers it immediately. If the content is not currently in that edge location, CloudFront retrieves it from an Amazon S3 bucket or an HTTP server. Amazon CloudFront is not appropriate in case users can tolerate some delays or servers are present near to the location of user. It also Integrates through the W3 Total Cache plugin. Amazon CloudFront Pricing based on bandwidth usage that's the best part of it.
For any company that needs a robust DNS service that can handle high QPS volumes without latency or lag, Oracle Dyn is the best that I have used. I can always rely on the backend infrastructure to ensure that DNS isn't a bottleneck for website performance. I have never had to open a support ticket for any issues and published changes to DNS records are nearly instantaneous across the globe.
Lots of configuration options, which allow for different setups and pricing strategies
Lambda@Edge integration allows for really quite complex behaviours to be executed in the cloud at the edge node itself. This means there are a huge amount of possibilities for shaping and altering traffic close to the viewer.
Simple integration to other AWS services (e.g. S3)
As a relatively experienced engineer, I find the UI to be incredibly obtuse and counter-intuitive. I try and use the API for most things, but for some people that may not be an option.
The user documentation is a bit hard to navigate. DNS in general is pretty simple, so this is a minor gripe, but it's hard to find specific info sometimes.
I give Oracle Dyn Managed DNS's overall usability an 8/10. If you understand DNS then you should have no problem working with the Dyn DNS interface. It takes very little time to learn how to update and manage DNS for your domains. The DYN API is also easy to work with and they provide SDK's for most programming languages.
CloudFront is a good CDN solution. It can be a bit complicated to implement depending on your needs, but AWS tech support is great. You get to avoid a ton of upfront costs by going with CloudFront. It works best in conjunction with other AWS services in your infrastructure. Once you set it up, you won't need to do much to maintain it. It just works.
Haven't had a need to work with the support team and DYN to date. The system has always done what we needed and the support documentation is straightforward and has answered any questions that we have had. They provide updates if there are ever any issues in a timely manner and make sure everyone knows what is going on.
Have used the IBM Cloud Content Delivery Network for a very short time span like a couple of weeks. Both the setup as well as interactions with other services are a little complicated or not straightforward when compared to AWS. Also, IBM cloud has less number of edge locations than AWS Cloudfront.
As our organization had an ample amount of DNS to manage, it was quite inconvenient when it comes to Amazon Route 53 or any other alternatives as the change propagation time was pretty much high as compared to Oracle Dyn Managed DNS. And when it comes to the huge customer base and customer satisfaction, the organization has to be wise at choosing the right tools and the right tool which fitted our requirements was Oracle Dyn managed DNS.