Routing Your Traffic Globally to Meet Customer Needs
March 29, 2018
Routing Your Traffic Globally to Meet Customer Needs
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with Oracle Dyn Managed DNS
We use Traffic Director to ensure that visitors to our website are routed to the servers that will provide them with the best experience. As we scale out globally we want to ensure that all of our users are able to access our services as quickly an smoothly as possible. In addition, some countries have regulatory requirements that we treat traffic or data from their citizens differently. We can use Traffic Director to ensure that all of those rules are followed. Lastly, when something does go awry with our technical infrastructure, Traffic Director quickly detects this and sends users to the next best (and available) endpoint.
- Responds quickly to changes in the health of your infrastructure
- Very fast and completely transparent to the end user
- Geographical segmentation of traffic can be done down to the specific country/state level
- API allows settings to be changed quickly with remote automation
- Learning your way around the configuration can be difficult at first. It is one of those things where there are so many knobs you can turn that it is overwhelming and takes time to figure out where each setting is that you want to modify.
- Misconfigured & failing health checks can be difficult to debug. The output that is provided to show you why a health check fails can be misleading in some cases or just too vague in others.
- No way to replicate the configuration to another provider. If you want to have a secondary DNS provider for redundancy, there is no way to automate the syncing of Traffic Director configuration. Normal DNS records can be as they are in a standard format, but there is no standard format for what Traffic Director does.
- Dyn Traffic Director has allowed us to quickly respond to changes in our infrastructure in a cost effective manner.
- When we have needed to quickly scale into a new global area to meet customer needs, Traffic Director has allowed us to smoothly shift around our traffic to keep things running. Later, if the demand subsides we can shift everything back to how it was before. This has made it so we can respond to global needs quickly.
AWS Route 53 did not allow us to be specific enough in how we segment global traffic. It only allows you to select continents or large segments of the world. Also, we currently host all of our infrastructure with AWS and felt if something were to go wrong there, we should be able to quickly change our DNS to point somewhere else if needed.