A 20 minute talk I gave as part of the "Code as Craft: Moving Fast at Scale" Etsy micro-conference

1. Continuous Deployment
kellan@etsy.com, @kellan,
VP of Engineering
Thursday, March 17, 2011

2. What? => Why? => How?
Thursday, March 17, 2011

3. What is it?
Thursday, March 17, 2011

4. Small, frequent changes.
To production.
Thursday, March 17, 2011

5. Small Frequent
Small, frequent changes.
To production.
Thursday, March 17, 2011

6. A collection of techniques
to avoid SUCKING.
Thursday, March 17, 2011

7. Why do we do it?
Thursday, March 17, 2011

8. Agility: Always Be Shipping
Thursday, March 17, 2011

9. MTTD / MTTR
Thursday, March 17, 2011

10. 4 change related “incidents” in 2010
Thursday, March 17, 2011

11. time to detect: <15 minutes
time to resolve: ~216,000 minutes
Deep Water Horizon
Thursday, March 17, 2011

12. mean time to detect:
< 5 minutes
mean time to resolve:
MMTR: 4.5 minutes
MTTD: <5 minutes 4.5 minutes
Thursday, March 17, 2011

13. Encourages Experimentation
Thursday, March 17, 2011

14. 1%
Thursday, March 17, 2011

15. Optimize for Developer Happiness
Thursday, March 17, 2011

16. DevOps
Thursday, March 17, 2011

17. Scales Trust and Risk
Thursday, March 17, 2011

18. How do we do it?
Thursday, March 17, 2011

19. Work in trunk,
branch in code.
Thursday, March 17, 2011

20. “All existing revision control systems were
built by people who build installed
software”
- Paul Hammond,
Always Ship Trunk, Velocity 2010
Thursday, March 17, 2011

21. if ($cfg[‘awesome_new_search’]) {
# new hotness
$rsp = do_solr();
} else {
config flags
# boring old stuff
$rsp = do_grep();
}
Thursday, March 17, 2011

22. one install, multiple versions.
Thursday, March 17, 2011

23. Keep it simple.
Thursday, March 17, 2011

24. One button deploy
Thursday, March 17, 2011

25. Operability Review
Thursday, March 17, 2011

26. Communication
Thursday, March 17, 2011

27. Graph Everything!
Thursday, March 17, 2011

28. FAQ:
Schemas?
Testing and continuous integration?
QA?
Thursday, March 17, 2011

29. /trunk/, config flags, 1B deploy, what
could go wrong?, IRC, graphs
Thursday, March 17, 2011