Continuous Delivery What is Continuous Delivery? Continuous Delivery is the ability to get changes of all types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way. Our goal is to make deployments—whether of a large-scale distributed system, a complex production environment, an embedded system, or an app—predictable, routine affairs that can be performed on demand. We achieve all this by ensuring our code is always in a deployable state, even in the face of teams of thousands of developers making changes on a daily basis. Why continuous delivery? It is often assumed that if we want to deploy software more frequently, we must accept lower levels of stability and reliability in our systems.
|Published (Last):||18 March 2016|
|PDF File Size:||18.29 Mb|
|ePub File Size:||4.43 Mb|
|Price:||Free* [*Free Regsitration Required]|
The biggest problem is the lack of real world examples. Chapters are mostly huge blocks of advice: the advice is good, but not memorable or actionable in the way it is presented. There need to be far more examples of real world systems with both good approaches and bad approaches discussed and compared in detail.
Moreover, the book is very very repetitive. There are many sentences, paragraphs, and even pages that can be skipped because they are obvious or just a rehash of something earlier or both. In short, this is a VERY important - perhaps even required - read for anyone working on medium and large software projects, but this book desperately needs a tldr companion with lots of examples.
Without continuous integration, your software is broken until somebody proves it works, usually during a testing or integration stage. With continuous integration, your software is proven to work assuming a sufficiently comprehensive set of automated tests with every new change—and you know the moment it breaks and can fix it immediately. For the software delivery process, the most important global metric is cycle time.
This is the time between deciding that a feature needs to be implemented and having that feature released to users. Do you do this on a repeatable, reliable basis? To paraphrase, performance is a measure of the time taken to process a single transaction, and can be measured either in isolation or under load.
Throughput is the number of transactions a system can process in a given timespan. It is always limited by some bottleneck in the system. The maximum throughput a system can sustain, for a given workload, while maintaining an acceptable response time for each individual request, is its capacity. Customers are usually interested in throughput or capacity.
When we talk about components, we mean a reasonably large-scale code structure within an application, with a well-defined API, that could potentially be swapped out for another implementation.
A component-based software system is distinguished by the fact that the codebase is divided into discrete pieces that provide behavior through well-defined, limited interactions with other components.
Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation