0
Continuous Change At Scale
The Human Side of Deployment
jgoulah@etsy.com / @johngoulah
• 500 employees
• 500 employees
• $1B + Gross Sales
• 500 employees
• $1B + Gross Sales
• 200 countries
push code > 30x per day
•

why continuous deploy works
•
•

why continuous deploy works
what pieces need to be in place
•
•
•

why continuous deploy works
what pieces need to be in place
how you can get started
what makes this a success?
minimizes risk
makes integration smoother
engineer happiness
continuous improvement
what pieces need to be in place?
technical pieces
continuous integration
stable trunk
did you “try” your code?
did you “try” your code?
https://github.com/etsy/trylib
monitoring
instrumentation
feature flags
what is a feature flag?
rampups
rampups
https://github.com/etsy/feature
autonomy
culture bits
a tradeoff
trust
eliminate ceremony
deploys are not releases
getting started
dashboards
non-blocking tests
keep it simple
start small
• a config file
• a config file
• a service
• a config file
• a service
• a feature
Thank you
etsy.com/careers
Continuous Change at Scale
Continuous Change at Scale
Continuous Change at Scale
Continuous Change at Scale
Upcoming SlideShare
Loading in...5
×

Continuous Change at Scale

890

Published on

you can find the video of the talk here http://www.youtube.com/watch?v=0QlhnnhYKR0

Published in: Technology, Business
2 Comments
2 Likes
Statistics
Notes
No Downloads
Views
Total Views
890
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
20
Comments
2
Likes
2
Embeds 0
No embeds

No notes for slide

Transcript of "Continuous Change at Scale"

  1. 1. Continuous Change At Scale The Human Side of Deployment jgoulah@etsy.com / @johngoulah
  2. 2. • 500 employees
  3. 3. • 500 employees • $1B + Gross Sales
  4. 4. • 500 employees • $1B + Gross Sales • 200 countries
  5. 5. push code > 30x per day
  6. 6. • why continuous deploy works
  7. 7. • • why continuous deploy works what pieces need to be in place
  8. 8. • • • why continuous deploy works what pieces need to be in place how you can get started
  9. 9. what makes this a success?
  10. 10. minimizes risk
  11. 11. makes integration smoother
  12. 12. engineer happiness
  13. 13. continuous improvement
  14. 14. what pieces need to be in place?
  15. 15. technical pieces
  16. 16. continuous integration
  17. 17. stable trunk
  18. 18. did you “try” your code?
  19. 19. did you “try” your code? https://github.com/etsy/trylib
  20. 20. monitoring
  21. 21. instrumentation
  22. 22. feature flags
  23. 23. what is a feature flag?
  24. 24. rampups
  25. 25. rampups https://github.com/etsy/feature
  26. 26. autonomy
  27. 27. culture bits
  28. 28. a tradeoff
  29. 29. trust
  30. 30. eliminate ceremony
  31. 31. deploys are not releases
  32. 32. getting started
  33. 33. dashboards
  34. 34. non-blocking tests
  35. 35. keep it simple
  36. 36. start small
  37. 37. • a config file
  38. 38. • a config file • a service
  39. 39. • a config file • a service • a feature
  40. 40. Thank you etsy.com/careers
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×