LLMpediaThe first transparent, open encyclopedia generated by LLMs

Continuous Delivery (book)

Generated by GPT-5-mini
Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Parent: Jenkins (software) Hop 4
Expansion Funnel Raw 78 → Dedup 0 → NER 0 → Enqueued 0
1. Extracted78
2. After dedup0 (None)
3. After NER0 ()
4. Enqueued0 ()
Continuous Delivery (book)
NameContinuous Delivery
CaptionFirst edition cover
AuthorsJez Humble, David Farley
CountryUnited Kingdom
LanguageEnglish
SubjectSoftware development
PublisherAddison-Wesley
Pub date2010
Pages512
Isbn978-0321601919

Continuous Delivery (book) is a technical monograph on software engineering practices that advocates automated, repeatable deployment pipelines to minimize risk and accelerate releases. It synthesizes research from Agile software development, industry practices from companies like Amazon (company), Google and Facebook, and engineering principles rooted in Lean manufacturing and DevOps movements.

Background and Context

The book emerged amid debates following the rise of Agile software development, the popularization of Extreme Programming, and the growth of large-scale web platforms such as Netflix, Etsy and Spotify (service), addressing challenges discussed at conferences like QCon and Velocity Conference. Influences cited include theoretical work from Edsger W. Dijkstra and W. Edwards Deming as well as industrial reports from Gartner and Forrester Research that highlighted bottlenecks in continuous integration practices pioneered at organizations such as ThoughtWorks and Pivotal (company). The context includes regulatory and operational pressures exemplified by incidents involving Knight Capital Group and legal frameworks like the Sarbanes–Oxley Act that shaped enterprise adoption.

Content and Structure

The book is organized into sections covering the deployment pipeline, automated testing, infrastructure management, and organizational patterns, referencing case studies from Amazon Web Services, Heroku, Microsoft, IBM and Oracle Corporation. Chapters integrate engineering examples with workflows used at Google and Facebook and discuss automation tools whose provenance traces to projects like Jenkins (software), Docker (software), Puppet (software), Chef (company), Ansible (software), and Kubernetes. Technical content includes explanations of build artifacts, test harnesses, and release strategies, drawing on system design ideas related to CAP theorem and fault tolerance practices discussed in relation to Amazon S3 outages and resilience work by Netflix, Inc. The structure alternates prescriptive guidance and empirical evaluation, citing patterns that echo principles from Toyota Production System and examples originating at Etsy, Inc. and Mozilla Foundation.

Authors and Contributions

The principal authors, Jez Humble and David Farley, bring backgrounds linking ThoughtWorks consultancy, academia at institutions like University of Cambridge (for Humble) and industrial projects spanning BBC and Siemens AG (for Farley). Contributions also include forewords and endorsements from figures associated with Martin Fowler, Kent Beck, Gene Kim, Nicole Forsgren and J. Paul Reed who have influenced discourse on Continuous integration and DevOps practices. The book consolidates Humble’s work on deployment automation with Farley’s experience in systems engineering and cites collaborative research from teams at Google Research and labs affiliated with MIT and Stanford University.

Reception and Impact

Critical reception included positive reviews in industry publications such as IEEE Software, ACM Queue and journals from O’Reilly Media, and recognition by communities attending DevOpsDays and QCon where practitioners implemented its recommendations. The work influenced curriculum at universities like Carnegie Mellon University and University of California, Berkeley and was cited in reports by McKinsey & Company and Deloitte analyzing software delivery performance. Its principles fed into commercial tooling ecosystems at Atlassian, GitHub, Bitbucket and cloud providers including Google Cloud Platform and Microsoft Azure, and shaped DevOps practices referenced in the State of DevOps Report and remediation strategies following outages at Equifax and Target Corporation.

Editions and Translations

First published by Addison-Wesley in 2010, later printings and a 2014 edition included updates aligning with containerization trends and tools such as Docker and orchestration frameworks like Kubernetes. Translations expanded reach into markets serviced by publishers in countries including Germany, France, Japan, China and Brazil and were used in localized training by consultancies like ThoughtWorks and Accenture. Subsequent editions and companion workshops incorporated material from conferences such as Velocity Conference and DevOpsDays and continued citations in standards discussions at organizations like IEEE and ISO.

Category:Software development books