dyn roadshow: cory von wallenstein & eric rosenberry talk scalability & availability

Scalability and Availability

in the Real WorldPortland, OR – October 1, 2013

Cory von WallensteinChief Technologist,

Dyn [email protected]

@cvwdyn

Eric RosenberryPrincipal Infrastructure Architect,

iovation [email protected]

@eprosenx

http://www.linkedin.com/company/dyn

http://www.facebook.com/Dyn

http://twitter.com/dyninc

http://www.youtube.com/dyninc

Pg. 2 Scalability and Availability in the Real World -- @cvwdyn & @eprosenx

What do we care about?

• Achieving high(er) availability

• Flexibility to change infrastructure without

downtime

• Ability to expand infrastructure beyond current 4

walls

• Disaster resilience

• Performance






How can we do it? Go active/active.

• The Iovation Technical Story• Going from one datacenter/cloud region to five• Application architectures and data replication

• How Dyn Helped• Global load balancing & traffic management via DNS





Scalability and Availability Fighting Fraud Non-Stop

Eric Rosenberry

Principal Infrastructure Architect

[email protected]

@eprosenx

5© 2012 iovation Inc.

What iovation Does

Recognize devices connecting to websites

Understands how these devices are related to each other

Block devices that are known to be associated with fraud or abuse and flag anomalies


Driving Factors• Successful Product

But ran into capacity limits scaling vertically Vertically scaling became cost prohibitive Unable to add features due to compute capacity limits

• Availability As we entered new markets, customers demanded higher

levels of availability Taking monthly downtimes for maintenance and code

upgrades no longer possible

• Disaster Preparedness We were operating out of a single datacenter which

represented risk to the business


Design Criteria• Scalability

System must be able to scale horizontally by adding more nodes

• Availability Code deployments do not require taking any real time

services down Real time services must continue functioning through the

loss of a datacenter PLUS the simultaneous loss of a single server in another datacenter

Serving datacenters must be geographically disparate

• Financial Must be based on commodity x86 hardware, running on

open source software, without depending on SAN’s


Service Oriented Architecture

Consumer Facing

Subscriber Facing

Internal Service

Real-time

Asynchronous

Web Service APIs

Device Recognition

Service

Association & Reputation

Service

Business Rules Service

Admin Console UI Reporting

Message Bus

Web Device Print Distribution

GeoService

VelocityService

Analytics

WWW Internet

iovationsubscribers

consumers


Datacenter Types• Primary Data Processing

Real-time customer requests are sent to these facilities Every piece of the real-time system is N+1 redundant

• Data Storage Each datacenter that is designated for data storage has one

copy of all key data elements Storage nodes do not have storage level redundancy (the

redundancy is across-datacenters)

• Content Delivery These datacenters deliver content to our customers end users

computers Are N+1 redundant such that individual failures do not cause

the loss of the entire node


Network Design

BB1

AMS

MIA

10g

20g

10gInternet

consumers

Content Delivery

#3

Data StoragePDX

MIAData StorageSEA

iovationsubscribers

Data Storage

Content Delivery

Data Processing

Subscriber Queries

Private Network

Content Downloads


Portland to Seattle

http://www.zayo.com/sites/default/files/images/Zayo-US-Network-EXTERNAL-11-1-2012.kmz


How does Iovation use Dyn?

•API Interface• Active/Active between two sites

•Admin Console• Active/Active between two sites

•Content Distribution• GSLB among four sites






• DNS cache poisoning, DNSSEC and general DNS security






Anatomy of a HTTP connection






How does DNS loadbalancing work?






Simple active/passive example

• Primary location assumes 100% traffic

• In event of disaster, swing 100% of traffic to

a standby location• Could be a “we’ll be back soon” or “status” page• Could be a backup copy of your app

• We call this Active Failover






Active/Active Load Balancing

(Global Server Load Balancing, GSLB)

(Hot/Hot Load Balancing)

(High Availability Load Balancing)






Traffic management with

Dyn Traffic Director






Dyn Traffic Director

• Fast Anycast network enables low TTLs

• Monitor endpoints for health

• Globally load balance among 7 regions

• Use Anycast to gauge “where is the user?”






Favor performance over network topology?

• Real-time monitoring of endpoints

• Always serve the fastest endpoint for each

user, regardless of network topology

• That’s real-time traffic management with

Dyn’s Traffic Director






Favor geopolitical boundaries above all?

• Per query lookup on source address

• Geopolitical IP mapping database

• State by state and country by country

granularity

• That’s geo traffic management with Dyn’s

Traffic Director






Traffic Management Recap

• Active/Passive with health checks• Dyn Active Failover

• Active/Active with health checks• 7 global regions by network topology -> Dyn Traffic

Director• Add in real-time latency measurement -> Dyn Traffic

Director with real-time traffic management• Add in geopolitical granularity -> Dyn Traffic Director

with geo traffic management






Dyn Delivers Internet Performance

•Traffic management and managed

DNS

•Message management and email

delivery

•Remote access and domain services





Pg. 35 Presentation Title (edit from Slide Master) @twitterhandle

Scalability and Availabilityin the Real World

Cory von WallensteinChief Technologist,

Dyn [email protected]

@cvwdyn

Eric RosenberryPrincipal Infrastructure Architect,

iovation [email protected]

@eprosenx

Thank You!





dyn roadshow: cory von wallenstein & eric rosenberry talk scalability & availability

Technology