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.
|Published (Last):||16 September 2012|
|PDF File Size:||16.6 Mb|
|ePub File Size:||17.92 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 Technology By now, many of us are aware of the wide adoption of continuous delivery within companies that treat software development as a strategic capability that provides competitive advantage. Amazon is on record as making changes to production every Facebook releases to production twice a day. Many Google services see releases multiple times a week, and almost everything in Google is developed on mainline. Still, many managers and executives remain unconvinced as to the benefits, and would like to know more about the economic drivers behind CD. Continuous Delivery reduces waste and makes releases boring One of the main uses of continuous delivery is to ensure we are building functionality that really delivers the expected customer value. This approach created hundreds of millions of dollars of value for Amazon, and saved similar amounts through reducing the opportunity cost of building features that were not in fact valuable even if delivered on time, on budget, and at high quality.
Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation
He showed me around his project and one of the interesting aspects of his highly disciplined team was the fact that they deployed their software into production every night. I see plenty of project stories and they almost all involve a determined shortening of that cycle. Dave and Jez have been part of that sea-change, actively involved in projects that have built a culture of frequent, reliable deliveries. They and our colleagues have taken organizations that struggled to deploy software once a year, into the world of Continuous Delivery, where releasing becomes routine. The foundation for the approach, at least for the development team, is Continuous Integration CI. CI keeps a development team in sync with each other, removing the delays due to integration issues. A couple of years ago Paul Duvall wrote the book on CI within this series.