The book Devops in Practice: Reliable and automated software delivery by Danilo Sato provides a hands-on approach for implementing continuous delivery and DevOps practices.

The rapidly increasing appetite for new product features coupled with the decreased lifetime of products necessitates joining up the cycles of continuous design & delivery into an innovation cycle.

The practice of continuous delivery has become an integral part of contemporary software engineering, and successfully implementing continuous delivery requires some preparation.

For example, many companies find that investing in a continuous integration system is their first starting point, often paired with, or followed by, an investment in automated testing.

Integrating the continuous delivery tool chain To build the most effective continuous delivery pipeline, you have to make sure that all of your smaller pipes feed into your delivery chain in the right ...

It’s important to understand why continuous delivery makes sense and how to align the practice with customer expectations.

Continuous delivery means low-risk deployments Continuous delivery, once processes are in place and regularly used, gives you the option of much faster software development cycles.

Continuous delivery needs a continuous development model (and the associated integration and deployment tooling).

So what comes next? The future of application development depends on using artificial intelligence (AI) within the continuous delivery model.