3. MULTIPLE OPTIONS FOR SERVICING A USER:
2 or more servers
... datacenters
... CDNs
TRAFFIC MANAGEMENT
DATA DRIVEN DNS @nsoneinc
4. MULTIPLE OPTIONS FOR SERVICING A USER:
2 or more servers
... datacenters
... CDNs
GOAL: SEND USER TO THE “BEST” OPTION
TRAFFIC MANAGEMENT
DATA DRIVEN DNS @nsoneinc
5. MULTIPLE OPTIONS FOR SERVICING A USER:
2 or more servers
... datacenters
... CDNs
GOAL: SEND USER TO THE “BEST” OPTION
“BEST”:
Fastest / most responsive
Up
Cheapest
… any biz objective, really
TRAFFIC MANAGEMENT
DATA DRIVEN DNS @nsoneinc
6. MULTIPLE OPTIONS FOR SERVICING A USER:
2 or more servers
... datacenters
... CDNs
GOAL: SEND USER TO THE “BEST” OPTION
“BEST”:
Fastest / most responsive
Up
Cheapest
… any biz objective, really
TRAFFIC MANAGEMENT (of course, there’s more to “traffic management”)
DATA DRIVEN DNS @nsoneinc
9. DNS IS BORING.
BUT
DISTRIBUTED APPLICATIONS ARE EASIER THAN EVER.
(traffic management is more important than ever)
DATA DRIVEN DNS @nsoneinc
10. DNS IS BORING.
BUT
DISTRIBUTED APPLICATIONS ARE EASIER THAN EVER.
(traffic management is more important than ever)
SO
DNS IS KIND OF EXCITING AGAIN. YAY.
(because dns lookup is a decent time to make traffic management decisions)
DATA DRIVEN DNS @nsoneinc
11. WHY IS DNS LOOKUP A GOOD TIME TO
DO TRAFFIC MANAGEMENT?
DATA DRIVEN DNS @nsoneinc
12. WHY IS DNS LOOKUP A GOOD TIME TO
DO TRAFFIC MANAGEMENT?
1. APP ENTRYPOINT
DATA DRIVEN DNS @nsoneinc
13. WHY IS DNS LOOKUP A GOOD TIME TO
DO TRAFFIC MANAGEMENT?
1. APP ENTRYPOINT
2. REALTIME STATE
Your systems
The network
Etc.
DATA DRIVEN DNS @nsoneinc
14. WHY IS DNS LOOKUP A GOOD TIME TO
DO TRAFFIC MANAGEMENT?
1. APP ENTRYPOINT
2. REALTIME STATE
3. HIGH FREQUENCY
Get to make “decisions” often
Can have impact faster than TTL in
some key scenarios (load shedding)
DATA DRIVEN DNS @nsoneinc
15. WHY IS DNS LOOKUP A GOOD TIME TO
DO TRAFFIC MANAGEMENT?
1. APP ENTRYPOINT
2. REALTIME STATE
3. HIGH FREQUENCY
4. GRANULAR
Per resolver
Or per /24 (edns-client-subnet)
DATA DRIVEN DNS @nsoneinc
16. WHY IS DNS LOOKUP A GOOD TIME TO
DO TRAFFIC MANAGEMENT?
1. APP ENTRYPOINT
2. REALTIME STATE
3. HIGH FREQUENCY
4. GRANULAR
5. LOW LATENCY
Anycasting: decisions at the edge
Caching: reuse decisions
DATA DRIVEN DNS @nsoneinc
19. DATA DRIVEN DNS @nsoneinc
WHAT DOES IT MEAN TO DO
DATA DRIVEN TRAFFIC MANAGEMENT?
20. DATA DRIVEN DNS @nsoneinc
UNDERSTAND WHAT WE’RE
TRYING TO OPTIMIZE
21. DATA DRIVEN DNS @nsoneinc
UNDERSTAND WHAT WE’RE
TRYING TO OPTIMIZE
response times
throughput
infrastructure load
cost
…
22. DATA DRIVEN DNS @nsoneinc
UNDERSTAND WHAT WE’RE
TRYING TO OPTIMIZE
response times
throughput
infrastructure load
cost
…
MAKE ROUTING DECISIONS USING
FIRST ORDER INFORMATION
23. DATA DRIVEN DNS @nsoneinc
UNDERSTAND WHAT WE’RE
TRYING TO OPTIMIZE
response times
throughput
infrastructure load
cost
…
MAKE ROUTING DECISIONS USING
FIRST ORDER INFORMATION
eyeball metrics
application load metrics
$/usage metrics
accurate geo/network/resolver data
...
24. DATA DRIVEN
DNS STATE
CONFIGURATION
STATIC & DYNAMIC
LIVE METRICS
DATA FEEDS
DATA DRIVEN DNS @nsoneinc
25. DATA DRIVEN DNS @nsoneinc
WHAT DOES THIS LOOK LIKE IN PRACTICE?
26. DATA DRIVEN DNS @nsoneinc
DATA
SOURCES
APP
application metrics
perf
load
...
27. DATA DRIVEN DNS @nsoneinc
DATA
SOURCES
APP
MONITORING
server, system, network
upness
perf/QoS
...
28. DATA DRIVEN DNS @nsoneinc
DATA
SOURCES
APP
MONITORING
TOOLS
portals/manual
biz logic/automation
...
29. DATA DRIVEN DNS @nsoneinc
DATA
SOURCES
APP
MONITORING
TOOLS
GATHERERS
routing/network metrics
geoip intelligence
resolver modeling & intelligence
eyeball metrics / RUM
...
30. DATA DRIVEN DNS @nsoneinc
APP
MONITORING
TOOLS
GATHERERS
INGEST
DATA
SOURCES
31. DATA DRIVEN DNS @nsoneinc
APP
MONITORING
TOOLS
GATHERERS
INGEST
COMPILE
CLASSIFY
NORMALIZE
AGGREGATE
...
DATA
SOURCES
32. DATA DRIVEN DNS @nsoneinc
APP
MONITORING
TOOLS
GATHERERS
COMPILE
CLASSIFY
NORMALIZE
AGGREGATE
INGEST PUBLISH
...
DNS
EDGES
DATA
SOURCES
33. DATA DRIVEN DNS @nsoneinc
APP
MONITORING
TOOLS
GATHERERS
COMPILE
CLASSIFY
NORMALIZE
AGGREGATE
INGEST PUBLISH
...
DNS
EDGES
QUERIES
DATA
SOURCES
46. WHAT MATTERS MORE IN DYNAMIC DNS?
HOW FAST YOU SPIT OUT AN ANSWER?
OR THAT IT’S THE RIGHT ANSWER?
DATA DRIVEN DNS @nsoneinc
47. WHAT MATTERS MORE IN DYNAMIC DNS?
HOW FAST YOU SPIT OUT AN ANSWER?
OR THAT IT’S THE RIGHT ANSWER?
90-98% OF DNS QUERIES ARE
ANSWERED FROM CACHE
(for high volume records)
DATA DRIVEN DNS @nsoneinc
48. WHAT MATTERS MORE IN DYNAMIC DNS?
HOW FAST YOU SPIT OUT AN ANSWER?
OR THAT IT’S THE RIGHT ANSWER?
90-98% OF DNS QUERIES ARE
ANSWERED FROM CACHE
(for high volume records)
YOU’D BETTER MAKE SURE THE
RIGHT ANSWER IS CACHED
DATA DRIVEN DNS @nsoneinc
49. DATA DRIVEN DNS @nsoneinc
ANYCASTING: More POPs is better, right?
40+
50+
?
<10
10+
15+
30+
15+
20+
54. WHERE ARE THE RESOLVERS?
24h, sample ~0.5% NSONE queries CC /32s >10Q
US 95k 12k
BR 9k 1.3k
GB 7k 900
RU 6k 1.4k
JP 6k 800
CA 6k 800
DE 5k 600
CN 3k 700
AU 3k 400
DATA DRIVEN DNS @nsoneinc