This document discusses the evolution of DevOps practices and platforms. It describes how organizations like Amazon and Netflix built platforms to enable continuous delivery of software through automation. These platforms allowed for high velocity software development while keeping promises around availability, reliability and security. The document advocates that organizations adopt cloud native principles of using simple, automated patterns and tooling to build platforms that help teams keep promises around delivering features quickly at scale.
41. devops
• developers and operations can
and should work together
• system administration evolving to
look more like software
development
• evolving together as global
community sharing solutions
49. ‘devops actualized’ represent patterns
that emerged in high performing
organizations that deliver highly available
applications continuously at scale
55. Amazon, a bookstore in Seattle, deploys
code to production every 11 seconds…
1 second
56. –Werner Vogels, CTO Amazon
“The traditional model is that you take your software to the wall
that separates development and operations, and throw it over
and then forget about it. Not at Amazon. You build it, you run it.
This brings developers into contact with the day-to-day
operation of their software. It also brings them into day-to-day
contact with the customer. This customer feedback loop is
essential for improving the quality of the service.”
58. Netflix Lessons
• Speed wins in the marketplace
• Remove friction from product development
• High trust, low process, no hand-offs between teams
• Freedom and responsibility culture
• Don’t do your own undifferentiated heavy lifting
• use simple patterns automated by tooling
• self service cloud makes impossible things instant
61. Netflix Lessons
• Speed wins in the marketplace
• Remove friction from product development
• High trust, low process, no hand-offs between teams
• Freedom and responsibility culture
• Don’t do your own undifferentiated heavy lifting
• use simple patterns automated by tooling
• self service cloud makes impossible things instant
62. Netflix built a platform to enable
self service deployment
63. Netflix built a platform to deploy
and operate microservices
64. Netflix built a platform to
continuously deliver software
65. Netflix built a platform that could
protect itself from failure
66. What Netflix did not do is build a platform
for general ad-hoc automation…
73. need to manage a large distributed system
• deployment
• configuration changes
• updates/upgrades - minimal downtime
• health checks and remediation
• scale out/scale in
• across multiple IaaS
75. Now that we have a tool chain for
release engineering, deployment,
and lifecycle management of large-
scale distributed services…
What should we do with it?
79. • role based access to resources
• run code on demand
• coordinate cross service
configurations
• route public requests
• read and write persistent data
• add and remove resources
• record internal and external
events
• isolate resources and failures
• measure performance/health
• detect and determine failure
(plan & provoke failure)
• recover failures
• work tomorrow
What problems does it solve?
94. no one originally set out to do devops,
continuous delivery, microservices, or
platforms these were natural consequences
don’t fixate on the words, fixate on the outcomes
95. if you want to align people in your
organization, think about the
interfaces, look at the promises they
make and keep with each other.
96. Use tools and simple
patterns to make doing the
right thing the easy thing