Chapter 10. Continuous Deployment Patterns and Antipatterns
Learn from the mistakes of others. You can’t live long enough to make them all yourself.
Eleanor Roosevelt
In this chapter, we will give you the patterns for continuous deployment that you need to be successful with implementing DevOps best practices in your organization. It is important to understand the rationale for continuous updates to be able to convince others in your organization about the change needed to improve your deployment process.
We will also give you plenty of antipatterns from companies that have failed to adopt continuous update best practices. It is good to learn from the failures of others, and plenty of recent examples exist in the high technology industry of what not to do and the consequences of ignoring best practices.
After completing this chapter, you will be armed with knowledge of seven best practices of continuous updates that you can start using today in order to join the top 26% of DevOps “Elite Performers” of the software industry.
Why Everyone Needs Continuous Updates
Continuous updates are no longer an optional part of a software development but are a best practice to be adopted by any major project. Planning for continuous delivery of updates is just as important as the functional requirements of the project and requires a high level of automation to execute on reliably.
It was not always this way. Historically, software was delivered on a much lower ...
Get DevOps Tools for Java Developers now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
