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