Continuous Delivery
Reliable Software Releases through Build, Test, and Deployment Automation
by Jez Humble, David Farley · first published 2010
94% recommend6% neutral
Why HN recommends it
Principle-focused primer on deployment pipelines, build automation, testing and releases, still seen as the best treatment of the topic. Suits developers and DevOps newcomers who want fundamentals before choosing tools.
Summarised by Claude from recommending comments
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
Mentions per year
What Hacker News says
Related books
2011–2026Zen of Graphics Programming
Michael Abrash
Recommended by 8 · mentioned by 128 recommend · 12 mention8 recommend · 128 recommend
2009–2025A discipline of programming
Edsger Wybe Dijkstra
Recommended by 16 · mentioned by 3016 recommend · 30 mention16 recommend · 3016 recommend
2013–2026The Phoenix Project
Gene Kim, Kevin Behr, George Spafford
Recommended by 166 · mentioned by 270166 recommend · 270 mention166 recommend · 270166 recommend
2009–2026Patterns of Enterprise Application Architecture
Martin Fowler
Recommended by 34 · mentioned by 7634 recommend · 76 mention34 recommend · 7634 recommend
2010–2025The clean coder
Robert C. Martin
Recommended by 53 · mentioned by 8553 recommend · 85 mention53 recommend · 8553 recommend
2008–2026How Buildings Learn
Stewart Brand
Recommended by 37 · mentioned by 5437 recommend · 54 mention37 recommend · 5437 recommend
2010–2026Drive
Daniel H. Pink
Recommended by 47 · mentioned by 8347 recommend · 83 mention47 recommend · 8347 recommend
2007–2026The reasoned schemer
Daniel P. Friedman
Recommended by 45 · mentioned by 7945 recommend · 79 mention45 recommend · 7945 recommend
If you are specifically interested in this kind of continuous deploy process then "Continuous Delivery[1]" is a decent book on the subject. The IMVU post "Doing The Impossible 50 Times A Day[2]" is another good place to start reading. [1] http://www.amazon.com/gp/product/0321601912 [2] http://timothyfitz.wordpress.com/2009/02/10/continuous-deplo...
on “Deployinator: Etsy's deploy tool open sourced” ↗Yes it's aspirational, and of course you have to do batching when the rate of commits gets too high. Many companies don't actually end up at the end of the spectrum with full continuous delivery; most of the value is captured by building what's needed _to be able to_ if you chose to, and doing say daily or hourly automated deploys. If you're not familiar with the general arguments for why CD…
on “DevOps: An idea so good, no one admits they don’t do it” ↗…books on design patterns, but you should really read the one that started it all. (For extra credit, read A Pattern Language, by Christopher Alexander - a book about urban architecture that inspired it.) Continuous Delivery, by Jez Humble and David Farley. Stop thinking about your program in isolation, and learn how to deploy effectively! Influence: The Psychology of Persuasion, by Robert Cialdini. This is DHH's favorite…
on “Ask HN: What language-agnostic programming books should I read?” ↗…As a ScaleUp CTO, you'll likely need to embrace innovation and growth. This book introduces the principles of lean startup methodology, helping you navigate the challenges of scaling your company. 5. "Continuous Delivery" by Jez Humble and David Farley - Scaling your technology infrastructure while maintaining a robust and efficient development pipeline is crucial. This book delves into the principles and practices…
on “Ask HN: What books would you recommend to newly appointed ScaleUp CTO?” ↗…of resources their way. In no particular order: http://progit.org/book/ http://www.gitready.com/ http://book.git-scm.com/ For more on this kind of stuff and no doubt a better explanation, check out Continuous Delivery by Jez Humble and Dave Farley. Link: http://continuousdelivery.com/
on “Ask HN: practical git process for teams with frequent deploy?” ↗Just started reading "Continuous Delivery" by Jez Humble, et al. Really wish I would have grabbed this years ago, great primer on what (for me) is a confusing topic. http://www.amazon.com/Continuous-Delivery-Deployment-Automat...
on “Ask HN: Which book are you reading these days?” ↗…remove a lot of the burden of independent versioning and keeping track of the version compatibility matrix. For anyone interested in a simpler path I think there is a lot of useful information in the book Continuous Delivery by Jez Humble and Paul Hammond.
on “Ask HN: How do you version control your microservices?” ↗…Bjarne Stroustrup. 2. Operating System Concepts by Silberschatz 3. Compilers by Aho As an agile software developer: 1. eXtreme Programming by Kent Beck 2. Pragmatic Programmer by Hunt and Thomas 3. Continuous Delivery by Jez Humble As an architect: 1. Domain Driven Design by Evans 2. Pattern-Oriented Software Architecture by Buschmann 3. Envisioning Information by Edward Tufte As a CEO: 1. Good To Great by Collins…
on “Ask HN: What three books impacted your career the most?” ↗If you haven't read it already, read Continuous Delivery. https://www.amazon.com/dp/0321601912
on “Show HN: A Bot to Deploy to AWS, Digital Ocean Etc.” ↗For the build/test/integration/deployment cycle, there's "Continuous Delivery" by Humble and Farley: https://smile.amazon.com/Continuous-Delivery-Deployment-Auto... I found that very good for understanding the principles and reasons. Implementing it was a very frustrating experience…
on “Ask HN: DevOps learning resources” ↗…of a principle than a job. that's my opinion though. i've been reading through this book and it does a decent job of covering the principles for CICD, builds, tests releases: https://www.amazon.com/Continuous-Delivery-Deployment-Automa... you'll run across various "thought leaders" in devops and its important to remember that a) each employer treats devops and cicd differently and you'll want to learn their practices…
on “Ask HN: DevOps learning resources” ↗…overdo it and build something which does not agree with reality if you "try to build the whole thing" at once. Building the smallest possible deployment pipeline (a skeleton pipeline, as it's called in the continuous delivery book (from 2010 but still the best thing on the topic out there) [1]). You start covering the most essential needs just so they become useful and usable. Then you go ahead and iterate from there, building…
on “Benefits of Continuous Delivery” ↗…thinking about opportunity costs) Why we sleep (interesting read) Exponential organisations (Re-read after 2 years, worth it) Prisoners of Geography (very interesting view of geopolitics, Putin, et al) Continuous Delivery (great!) Clean Code (must read for any serious programmer) Built to last (picked it back after 1-2 years, cool book) Site Reliability Engineering (didn't quite finish, but good book) Building Microservices…
on “Ask HN: Books you read in 2018?” ↗…on your technology stack, your architecture, your deployment model, your product. You sort of learn the fundamental concepts and then pick out the pieces that fit your use case. Everyone should read Continuous Delivery to start (https://www.amazon.com/gp/product/0321601912/ref=as_li_tl?ie...). It's 10 years old but it's still the canonical reference for how most people should be deploying in the modern age. A book…
on “Show HN: I wrote a book on web application deployment” ↗I find that the practice of "software engineering" has a fuzzy distinction to "computer science." I highly recommend the following books that helped me out on that journey: - Continuous Delivery by Jez Humble and Dave Farley - The Pragmatic Programmer by Andy Hunt and Dave Thomas - A History of Modern Computing by Paul E. Ceruzzi - Version Control with Git by Prem Ponuthorai and Jon Loeliger…
on “Books for Software Engineers in 2023” ↗