Continuous Deployment at Lean LA

1. CONTINUOUS DEPLOYMENT Brett G. Durrett,VP Engineering & Operations, IMVU - @bdurrett 1

2. Destination site Chat and Games with Avatars Revenue over $40 million annually Profitable Engineering staff > 50 people 2

3. NO STAGING CLUSTER NO QA REVIEW COMMIT CODE TO LIVE IN PRODUCTION 3

5. DEVELOP RELEASE PRAY FOR CUSTOMERS 5

6. DEVELOP RELEASE ITERATE LEARN 6

9. WAY EASIER TO FIND REGRESSIONS IN SMALL LESS THAN 30 LINES OF BATCHES OF COMMITS CODE TO INVESTIGATE VS. 9

10. FAST RESPONSE TIMES 10

11. 11

12. DON’T TAKE MY WORD FOR IT… Reducing batch size… reduces cycle time reduces variability in flow accelerates feedback reduces risk reduces overhead Large batches… reduce efficiency inherently lower motivation and energy cause exponential cost and schedule growth lead to even larger batches The entire batch is limited by its worst element Chapter 5 – Reducing Batch Size

13. Local tests pass, Rollback engineer commits (Blocks) code No Lots and lots of Metrics Yes Code deployed to tests run good? all servers All tests Yes Code deployed to Metrics No pass? % of servers still good? No Yes Revert commit Win! (Blocks)

15. COD E HE RE!

19. CONTINUOUS INTEGRATION

20. 20

24. CLUSTER IMMUNE SYSTEM 24

25. IS IT IMPORTANT TO YOUR BUSINESS? MONITOR IT SYSTEM PERFORMANCE BUSINESS PERFORMANCE

31. 31

32. COMMIT TO MAKING FORWARD PROGRESS NEW PRODUCT ESTABLISHED PRODUCT START WITH SANDBOX START WITH PRODUCTION JUST PUSH! AUTOMATE DEPLOYS IDEAL TIME FOR FAILURES!!! BUILD CONFIDENCE 32

33. EXPECT SOME HURDLES

35. BUILD ISOLATION! FASTER TEST RUNS BUY HARDWARE SORT TESTS BY SPEED DEPENDENCY INJECTION AND… THE HYPOTHESIS BUILDER!

37. The Trickier Bits •  Catching issues that fail slowly –  SELECT * FROM growing_table WHERE 1 •  Some cri9cal areas cause hard lock-‐ups –  MySQL –  Memcached •  Lack of test coverage of older code –  Not an issue if you start with test coverage •  Outsourcing 37

38. BUILD SYSTEMS ARE CRITICAL BUSINESS FUNCTIONS RUN THEM THAT WAY!

40. COD E HE RE!

41. $experiment = array( ‘name’ -> ‘LeanLA’, 'initial_rollout' => '0', 'branches' => array( 'Enhanced' => 0.5, // can specify multiple weighted branches ) ); // Helper function for readability function user_should_see_test_feature( $uid = NULL ) { return get_branch_for_customer( $uid, $experiment ) ) == 'Enhanced'; // assigns customer if first time called } // The experiment branch if( user_should_see_test_feature( $uid ) ) { // behavior for experiment } else { // control behavior } 41

42. CLOSE EXPERIMENTS CONTROL PARTICIPANTS 42

43. UNDESIRED RESULT DESIRED RESULT NO STATISTICAL SIGNIFICANCE 43

44. THE “PERFECT” SPRINT Work Remaining Sprint Start Planned Sprint End

45. REALITY STRIKES When releases happen every 15 minutes, this can be arbitrary Outstanding Issues Incomplete Features Tech Review Refactoring Work Remaining Drop or push Sprint Start Planned Sprint End

46. END THE SPRINT WHEN WORK IS DONE Work Remaining Overage Sprint Start Sprint End Goal Sprint End

47. DEVELOP RELEASE RELEASE ITERATE ITERATE LEARN LEARN 47

48. EMPOWERED! 48

49. Thank You! Any Ques9ons? BreH G. DurreH IMVU recognized as: bdurreH@imvu.com Inc. 500 TwiHer: @bdurreH http://bit.ly/dv52wK Red Herring 100: Tweet this talk! http://bit.ly/bbz5Ex Best Place to Work: http://bit.ly/aAVdp8 @bdurreH (and we're hiring) http://www.imvu.com/jobs 49

50. Thank You! •  The amazing engineers at IMVU that make this possible •  Patrick Vlaskovitz, Joe Zulli and Peter Mauro for invi9ng me to speak at LeanLA •  Avesta Rasouli and CoLoX for hos9ng and providing a great workspace •  John Overmeyer, Single Lane Traﬃc Photo: hHp://www.ﬂickr.com/photos/onebigchickenman/4869442019/ 50

Continuous Deployment at Lean LA

Recomendados

Recomendados

Más contenido relacionado

Similar a Continuous Deployment at Lean LA

Similar a Continuous Deployment at Lean LA (20)

Más de Brett Durrett

Más de Brett Durrett (6)

Último

Último (20)

Continuous Deployment at Lean LA