The document discusses continuous delivery practices at Netflix, emphasizing the deployment of microservices without a dedicated operations team, where teams own their code. It outlines strategies to enhance efficiency, including mapping value streams and reducing testing time, alongside addressing cultural aspects and leadership values. Additionally, it mentions various technical components like Spinnaker for cloud infrastructure management and Nebula plugins for packaging.

1. CONTINUOUS DELIVERY AT
MIKE MCGARR
@SONOFGARR
MIKEMCGARR.COM

2. ▸ a bit about Netflix
▸ deploying code at Netflix
▸ applying continuous delivery

3. ▸ a bit about Netflix
▸ deploying code at Netflix
▸ applying continuous delivery

7. microservices

9. no ops team

10. you build it
you own it

11. ▸ a bit about Netflix
▸ deploying code at Netflix
▸ applying continuous delivery

14. IMMUTABLE SERVER PATTERN

15. A SIMPLE MICROSERVICE
▸ Groovy
▸ Spring Boot

18. NEBULA PLUGINS
dependency lock plugin
resolution rules plugin
dependency recommender plugin
lint plugin
metrics plugin
test plugin
publishing plugin
ospackage plugin
http://nebula-plugins.github.io

22. Nebula's ospackage plugin
produces a Debian package

23. unit of deployment

24. BAKING

29. EACH INSTANCE NEEDS
▸ Amazon Machine Image (AMI)
▸ security groups
▸ launch configurations
▸ elastic load balancers
▸ auto-scaling groups

31. SPINNAKER
▸ Cloud infrastructure management
▸ Deployment pipelines
▸ microservice architecture
▸ Java & Groovy Spring Boot microservices

34. ▸ a bit about Netflix
▸ deploying code at Netflix
▸ applying continuous delivery

35. WHERE DO WE
START?

36. 1. FOCUS ON THE
WHOLE

37. VALUE
STREAM
MAPPING

40. FROM 3 MONTHS
TO 16 HOURS

42. 31 - 59 HOURS

44. 2. TESTING

46. PUSH TESTS DOWN

47. confidence

48. 3. FOCUS ON
ENABLEMENT

49. centralized teams

51. AVOID HAND OFFS

52. 4. UNDERSTAND
YOUR CULTURE

53. ▸ What does leadership value?
▸ What constraints do you have?
▸ What are your company values?
▸ What behaviors are rewarded?

56. QUESTIONS?