Astricon - Realities of Global Infrastructure in the Cloud


Published on

Talk by Cory von Wallenstein from Dyn at Astricon in Atlanta, GA on the realities of global infrastructure in the cloud.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Astricon - Realities of Global Infrastructure in the Cloud

  1. 1. Global Infrastructure in the Cloud Cory von Wallenstein Chief Technology Officer, Dyn Inc. @cvonwallenstein @cvonwallenstein from @DynInc
  2. 2. “Wired people should know something about wires”- Neal Stephenson, quoted in Andrew Blum’s TED Talk What is the Internet, Really?
  3. 3.
  4. 4.
  5. 5.
  6. 6.
  7. 7.
  8. 8. Going Global in the Cloud• Never been easier• Never been more affordable• Why should or shouldn’t you?• If so, how? @cvonwallenstein from @DynInc
  9. 9. A Word on Costs and Value• Unlikely to save you raw dollars• Likely to spend the same or more• But here’s what you gain: – Flexibility (can’t really screw this up) – Performance (many caveats here) – Reliability (if you do it right) – Efficiency (if your team embraces it)• Are those worthwhile to you? @cvonwallenstein from @DynInc
  10. 10. Why go from 1 to N? @cvonwallenstein from @DynInc
  11. 11. Reason 1: Disaster Recovery
  12. 12. Reason 1: Disaster Recovery Speed of light 299,792.458 km/second Theoretical RTT ~40ms Real RTT ~90ms
  13. 13. Reason 1: Disaster Recovery • Things don’t work as well at 90ms RTT latency as they do at 9ms RTT latency • Where can you go to get out of the way of a disaster but not create latency headaches?
  14. 14. Reason 1: Disaster Recovery “A frying squirrel took out half of our Santa Clara data center two years back,” - Mike Christian, Yahoo
  15. 15. Reason 1: Disaster Recovery “Squirrel chews account for a whopping 17% of our damages so far this year! But let me add that it is down from 28% just last year and it continues to decrease since we added cable guards to our plant.”, Fred Lawler, Level(3)
  16. 16. Reason 2: Get closer to users
  17. 17. Reason 2: Get closer to users
  18. 18. Reason 3: “Sorry, we’re full”
  19. 19. How: Figure out who and where• Figure out what your motivations are – Disaster recovery – Get closer to users – Future scaling• Take a latency inventory of your apps – To end users – To other dependencies• Get out the maps! Fire up traceroute! – EC2: US East (Northern Virginia), US West (Oregon), US West (Northern California), EU (Ireland), Asia Pacific (Singapore), Asia Pacific (Tokyo), South America (Sao Paulo), and GovCloud. @cvonwallenstein from @DynInc
  20. 20. How: Deploy and manage w/• sanity Software defined datacenters – Fancy term for “I defined the architecture in code instead of Microsoft Visio”• Configuration management – Orchestrate the cloud APIs, and the config of systems – Chef – Puppet – CFEngine, and more• Huge loss if you don’t take advantage of this @cvonwallenstein from @DynInc
  21. 21. How: Coordinating global traffic• What’s the app? – Application agnostic, like DNS Global Server Load Balancing • Fancy term for “DNS servers monitor your servers and change DNS answers when events are detected” – Application specific, like DUNDi • Decentralized coordination and fault tolerance• Avoid SPOFs like the plague – Keep it simple, keep it scalable @cvonwallenstein from @DynInc
  22. 22. What can you expect?• Flexibility – Deploy new servers in new locations in hours instead of weeks• Performance – If horizontally scalable on commodity hardware, you win. Else, be careful. – If closer to users and site-to-site latency not an issue or data is distributed/eventually consistent, you win. Else, be careful. @cvonwallenstein from @DynInc
  23. 23. What can you expect? • Reliability – If you understand “regions” and “availability zones”, you win. Else, be careful.
  24. 24. What can you expect?• Efficiency – Automation – More instrumentation -> reduced MTTD – More scalable – Most important: More focus on what delivers your business core competitive advantage. @cvonwallenstein from @DynInc
  25. 25. Thank you (and we’re hiring!) VP Technical Operations, Director of EngineeringDirector of Security, Network Engineers, Software Engineers, System Engineers, System Administrators (and more!)Reach out to me:,, @cvonwallenstein