Migrating Edmunds.com to AWS (re:Invent 2013 DMG205)
Upcoming SlideShare
Loading in...5

Migrating Edmunds.com to AWS (re:Invent 2013 DMG205)



Taking a stack composed of 30 web applications and their service dependencies to the cloud is no easy feat. Do you take the entirety of the stack or go the hybrid path? How transparent should the end ...

Taking a stack composed of 30 web applications and their service dependencies to the cloud is no easy feat. Do you take the entirety of the stack or go the hybrid path? How transparent should the end result be to your technology teams? Does it look exactly the same in the cloud as it does in your data center? These are not rhetorical questions; they were very real for those tasked with the challenge of taking Edmunds.com to the AWS Cloud. This talk addresses these questions and many more, examining the challenges, successes, and lessons learned as the team took their first steps out of their own data centers.

Accompanying video is available on YouTube: http://youtu.be/itbNET2dc3c



Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    Migrating Edmunds.com to AWS (re:Invent 2013 DMG205) Migrating Edmunds.com to AWS (re:Invent 2013 DMG205) Presentation Transcript

    • Edmunds.com on AWS John Martin November 14, 2013 © 2013 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified, or distributed in whole or in part without the express consent of Amazon.com, Inc.
    • Moving isn’t easy
    • Moving Isn’t Easy • A move isn’t easy • Taking something your familiar with elsewhere • How does that work again?
    • Today’s Agenda • Technology Overview • The Business Case • The Approach • Challenges • What’s Next?
    • John Martin @tekbuddha WHO AM I?
    • John Martin @tekbuddha • 15+ years in .com • 10+ years of Java • Old School Ops • New School Cultures WHO AM I?
    • The Company
    • The Company • Founded in 1966 • First online in 1994 as a gopher • First website in 1996
    • The Environment
    • The Environment • 30+ web applications across 300+ hosts. • Java on Redhat Linux • Tomcat, Solr, Coherence, Mongo, ActiveMQ
    • The Environment
    • The Environment • Chef + Cloudstack/UCS • Perforce, Jenkins, Nexus, Selenium, JMeter • AppDynamics, Splunk, RTview, Zenoss
    • The Deployment Pipeline
    • The Deployment Pipeline • OSS + Homegrown Tooling • All artifacts flow through the pipeline • Release Cycles: 1 Month > 3 Weeks > 1 Week
    • The Business Case
    • The Business Case • Simple: disaster recovery • Bad business not to evaluate cloud services
    • The Approach
    • The Approach • How to move 30+ apps and 300+ servers? • Make it run like it already does • Avoid biting off too much at once
    • Objectives • Minimize change / leverage existing toolchain • Manage cost • Provide initial design patterns for future builds
    • Challenges Source: http://is.gd/YmewdR
    • Challenges • A move isn’t easy. • Making the things we were familiar with work elsewhere wasn’t easy Source: http://is.gd/YmewdR
    • CloudFormation Source: http://is.gd/rayzL1
    • CloudFormation • Necessary from Day 1 • Familiar concepts • Infrastructure Is Code Source: http://is.gd/rayzL1
    • CloudStack
    • CloudStack JSON • Different structure, similar logic • Defining single hosts, not groups of services • No definitions of network resources
    • CloudFormation
    • CloudFormation JSON • Define network and services, not hosts • Live by cf-validate • Automate creation / avoid manual editing
    • NFS Source: http://is.gd/rayzL1
    • NFS • Still a core dependency • No great options in EC2 without refactor • Move static content to S3 Source: http://is.gd/rayzL1
    • Load Balancing Source: http://is.gd/rayzL1
    • Load Balancing • No physical load balancers • ELBs, HAproxy, and Chef were the key • Learn how Public/Private ELBs work with VPC Source: http://is.gd/rayzL1
    • [auto-]scaling Source: http://is.gd/rayzL1
    • [auto-]scaling • Worked but can leave behind a mess • Tooling must be prepared for ephermal nodes • Helped survive outages in US-EAST Source: http://is.gd/rayzL1
    • Testing… 1! 2! 3!
    • WHAT’S NEXT? Source: http://is.gd/xKdI6E
    • What Next? • Additional live-traffic tests • Deployment of internal services • Prepare for full move out of data center Source: http://is.gd/xKdI6E
    • REFACTOR Source: http://is.gd/D8bVaC
    • Refactor • Greater adoption of SOA principles • Full refactor of data pipelines (in and out) • Refactor for fragility of cloud environments Source: http://is.gd/D8bVaC
    • The Big Move • Work thus far completed by a small team • The Big Move will be all hands on deck • A two year goal to be fully cloud-based
    • Please give us your feedback on this presentation DMG205 As a thank you, we will select prize winners daily for completed surveys! Thank You