DevOps

Transcript

1. Exploring the Amazon: Our DevOps Journey Natasha Carlyon natasha.carlyon@greatersum.com @nscarlyon
4. Natasha Carlyon • Software Crafter • https://www.greatersum.com/ • @nscarlyon • http://speakerdeck.com/ • natasha.carlyon@greatersum.com
5. DevOps
6. The Three Ways Flow Fast Feedback Continual Learning & Experimentation
7. The First Way: Flow
8. Customer Request Feature in production, providing value
9. Continuous Delivery,
10. Fear
11. Access to production-like environment on demand
16. Third Parties
18. Pushing to Production
19. Making Work Visible
21. Limit WIP
22. Feature Toggle
23. Canary Release
24. Bottlenecks
25. Understanding your work
26. Questions • When will you use this feature? • Can you give me a specific example? • Ask ‘What’ Questions, not ‘Why’ ◦ What will this feature provide?
27. The Second Way: Fast Feedback
28. Telemetry
29. Dashboards
30. Logs • Debug - helps you debug future issues • Info - user-driven actions • Warn - might become an error • Error - API call failures, internal errors, etc. • FATAL - WAKE ME UP; Region down;
31. Fast & Reliable Automated Testing
33. Unit Tests
34. TDD
35. UI Tests
36. Andon Cord
37. Feedback from others
38. Weekly Demo
39. Users
41. Three or more developers Same Problem Same Time Same Computer Woody Zuill
43. The Third Way: Continual Learning and Experimentation
44. Learning Time
45. Kaizen Blitz
46. Spikes
47. Blameless Post-Mortems
50. What did we learn? Human Error is rarely the cause of failure. The vulnerabilities of the system and the processes in place lead to failure.
51. Resources The DevOps Handbook Accelerate: The Science of Lean Software and DevOps The Phoenix Project nUnit, Cypress, Approvals, Jasmine Making Work Visible @nscarlyon | natasha.carlyon@greatersum.com