The Software Development Process at Amazon

Transcription

1 The Software Development Process at Amazon Jonathan Weiss Managing Director Amazon Web Services Germany GmbH AWS OpsWorks, AWS Resource Groups, AWS Systems Manager

2 Amazon is hundreds of different businesses AWS did over 1,430 major feature releases in 2017 No signs of slowing down

3 The Software Development Lifecycle delivery pipeline build test release developer s plan feedback loop monitor customer s

4 Ten Lessons Learned 1. Microservices 2. DevOps Teams 3. Self-Service Tools 4. Continuous Delivery 5. Pessimistic ments 6. Automated Testing 7. Optimize ECT Loop 8. Monitor Everything 9. Measure Everything 10. Listen to Customers

5 Ten Lessons Learned 1. Microservices 2. DevOps Teams 3. Self-Service Tools 4. Continuous Delivery 5. Pessimistic ments 6. Automated Testing 7. Optimize ECT Loop 8. Monitor Everything 9. Measure Everything 10. Listen to Customers

6 Let s go back 15 years ago

7

8 Monolith development lifecycle build test release developer s app delivery pipeline

9 Service-Oriented Architecture (SOA) Single-purpose Primitive Connected w/ APIs Highly decoupled Microservices

10 Ten Lessons Learned 1. Microservices 2. DevOps Teams 3. Self-Service Tools 4. Continuous Delivery 5. Pessimistic ments 6. Automated Testing 7. Optimize ECT Loop 8. Monitor Everything 9. Measure Everything 10. Listen to Customers

11 Two-pizza teams Decentralized Agility Autonomy Accountability Ownership DevOps

12 Missing Tools??? developer s services delivery pipeline

13 Ten Lessons Learned 1. Microservices 2. DevOps Teams 3. Self-Service Tools 4. Continuous Delivery 5. Pessimistic ments 6. Automated Testing 7. Optimize ECT Loop 8. Monitor Everything 9. Measure Everything 10. Listen to Customers

14 Self-service Technology-agnostic Encourage best practices Single-purpose services Two-pizza teams Decentralized Agility Autonomy Accountability Ownership DevOps

15 ment service No downtime deployments Health tracking Versioned artifacts and rollbacks

16 Ten Lessons Learned 1. Microservices 2. DevOps Teams 3. Self-Service Tools 4. Continuous Delivery 5. Pessimistic ments 6. Automated Testing 7. Optimize ECT Loop 8. Monitor Everything 9. Measure Everything 10. Listen to Customers

17 Pipelines Continuous delivery Automated release process Faster & more reliable releases Adopted by virtually all teams

18 Microsservice development lifecycle build test release build test release build test release build test release build test release developer s services delivery pipelines build test release

19 Thousands of teams x Microservice architecture x Continuous delivery x Multiple environments = millions of deployments

20 Ten Lessons Learned 1. Microservices 2. DevOps Teams 3. Self-Service Tools 4. Continuous Delivery 5. Pessimistic ments 6. Automated Testing 7. Optimize ECT Loop 8. Monitor Everything 9. Measure Everything 10. Listen to Customers

21 Release Pipelines Source Build Staging Production Pull Source Code Run Build and Unit Tests to Staging Environment to Production Environment

22 Release Pipelines Source Build Staging Production Pull Source Code Run Build and Unit Tests to Staging Environment to One Box to 1 st AZ to One Box to 1 st AZ to 2 nd AZ to 2 nd AZ to 3 rd AZ to 3 rd AZ

23 Ten Lessons Learned 1. Microservices 2. DevOps Teams 3. Self-Service Tools 4. Continuous Delivery 5. Pessimistic ments 6. Automated Testing 7. Optimize ECT Loop 8. Monitor Everything 9. Measure Everything 10. Listen to Customers

24 Release Pipelines Source Build Staging Production Pull Source Code Run Build and Unit Tests to Staging Environment to One Box to 1 st AZ to One Box to 1 st AZ to 2 nd AZ to 2 nd AZ to 3 rd AZ to 3 rd AZ

25 Release Pipelines Source Build Staging Production Pull Source Code Run Build and Unit Tests to Staging Environment to One Box to 1 st AZ to One Box to 1 st AZ Functional Tests to 2 nd AZ to 2 nd AZ Load / Perf Tests Other Tests to 3 rd AZ to 3 rd AZ

26 Release Pipelines Source Build beta gamma Production Pull Source Code Run Build and Unit Tests to Staging Environment to Staging Environment to One Box to 1 st AZ to One Box to 1 st AZ Functional Tests Integration Tests to 2 nd AZ to 2 nd AZ Other Tests Load / Perf Tests Other Tests to 3 rd AZ to 3 rd AZ

27 Ten Lessons Learned 1. Microservices 2. DevOps Teams 3. Self-Service Tools 4. Continuous Delivery 5. Pessimistic ments 6. Automated Testing 7. Optimize ECT Loop 8. Monitor Everything 9. Measure Everything 10. Listen to Customers

28 The Edit-Compile-Test Loop

29 The Edit-Compile-Test Loop ECT Loop

30 The Edit-Compile-Test Loop ECT Loop Code Review

31 The Edit-Compile-Test Loop ECT Loop Staging Code Review

32 The Edit-Compile-Test Loop ECT Loop Production Staging Code Review

33 Catching Problems in the Development Lifecycle ECT Code Review Staging Production Ideal Place Great Place Good Place Last Resort

34 Ten Lessons Learned 1. Microservices 2. DevOps Teams 3. Self-Service Tools 4. Continuous Delivery 5. Pessimistic ments 6. Automated Testing 7. Optimize ECT Loop 8. Monitor Everything 9. Measure Everything 10. Listen to Customers

35 The Software Development Lifecycle delivery pipeline build test release developer s plan feedback loop monitor customer s

36 Ops Culture Ops Meetings Ops Dashboards resource monitoring application monitoring canary monitoring client-side monitoring order drop rate

37 Ten Lessons Learned 1. Microservices 2. DevOps Teams 3. Self-Service Tools 4. Continuous Delivery 5. Pessimistic ments 6. Automated Testing 7. Optimize ECT Loop 8. Monitor Everything 9. Measure Everything 10. Listen to Customers

38 Data Culture WBR Meetings Metrics Decks feature adoption segment growth funnel analysis cost structure

39 Ten Lessons Learned 1. Microservices 2. DevOps Teams 3. Self-Service Tools 4. Continuous Delivery 5. Pessimistic ments 6. Automated Testing 7. Optimize ECT Loop 8. Monitor Everything 9. Measure Everything 10. Listen to Customers

40 Listen It's easy to be right if you just listen to customers. 1. Ask them want they want 2. Get feedback on what you build 3. Course correct if need to

41 Wenger Swiss Army Knife Giant Feature vs. Need

42 Ten Lessons Learned Working Backwards description by Werner Vogels, Amazon CTO

43 Ten Lessons Learned 1. Microservices 2. DevOps Teams 3. Self-Service Tools 4. Continuous Delivery 5. Pessimistic ments 6. Automated Testing 7. Optimize ECT Loop 8. Monitor Everything 9. Measure Everything 10. Listen to Customers

44 Thank you

45 Two reminders: Please complete the session survey in the summit mobile app. AWS DevDay with Chef in Berlin on June 12 th -