Migrating Edmunds.com to AWS (re:Invent 2013 DMG205)
0 likes858 views
The document outlines a presentation by John Martin on moving the operations of a company founded in 1966 to the cloud, detailing the technology and business case for the transition. Key points include the challenges of moving 30+ applications and 300+ servers, and the approach to minimize changes while leveraging existing tools. The document also highlights future objectives including additional live-traffic testing and a complete move out of the data center over a two-year period.
![[auto-]scaling
Source: http://is.gd/rayzL1](https://image.slidesharecdn.com/2013-131218072602-phpapp01/85/Migrating-Edmunds-com-to-AWS-re-Invent-2013-DMG205-32-320.jpg)
![[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](https://image.slidesharecdn.com/2013-131218072602-phpapp01/85/Migrating-Edmunds-com-to-AWS-re-Invent-2013-DMG205-33-320.jpg)
Migrating Edmunds.com to AWS (re:Invent 2013 DMG205)
- 1. 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.
- 3. Moving Isn’t Easy • A move isn’t easy • Taking something your familiar with elsewhere • How does that work again?
- 4. Today’s Agenda • Technology Overview • The Business Case • The Approach • Challenges • What’s Next?
- 6. John Martin @tekbuddha • 15+ years in .com • 10+ years of Java • Old School Ops • New School Cultures WHO AM I?
- 7. The Company
- 8. The Company • Founded in 1966 • First online in 1994 as a gopher • First website in 1996
- 10. The Environment • 30+ web applications across 300+ hosts. • Java on Redhat Linux • Tomcat, Solr, Coherence, Mongo, ActiveMQ
- 11. The Environment
- 12. The Environment • Chef + Cloudstack/UCS • Perforce, Jenkins, Nexus, Selenium, JMeter • AppDynamics, Splunk, RTview, Zenoss
- 14. The Deployment Pipeline • OSS + Homegrown Tooling • All artifacts flow through the pipeline • Release Cycles: 1 Month > 3 Weeks > 1 Week
- 16. The Business Case • Simple: disaster recovery • Bad business not to evaluate cloud services
- 17. The Approach
- 18. The Approach • How to move 30+ apps and 300+ servers? • Make it run like it already does • Avoid biting off too much at once
- 19. Objectives • Minimize change / leverage existing toolchain • Manage cost • Provide initial design patterns for future builds
- 21. Challenges • A move isn’t easy. • Making the things we were familiar with work elsewhere wasn’t easy Source: http://is.gd/YmewdR
- 23. CloudFormation • Necessary from Day 1 • Familiar concepts • Infrastructure Is Code Source: http://is.gd/rayzL1
- 24. CloudStack
- 25. CloudStack JSON • Different structure, similar logic • Defining single hosts, not groups of services • No definitions of network resources
- 26. CloudFormation
- 27. CloudFormation JSON • Define network and services, not hosts • Live by cf-validate • Automate creation / avoid manual editing
- 29. NFS • Still a core dependency • No great options in EC2 without refactor • Move static content to S3 Source: http://is.gd/rayzL1
- 31. 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
- 33. [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
- 36. What Next? • Additional live-traffic tests • Deployment of internal services • Prepare for full move out of data center Source: http://is.gd/xKdI6E
- 38. 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
- 39. THE BIG MOVE
- 40. 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
- 41. Please give us your feedback on this presentation DMG205 As a thank you, we will select prize winners daily for completed surveys! Thank You