Continuous delivery

The approach helps reduce the cost, time,[citation needed] and risk of delivering changes by allowing for more incremental updates to applications in production.

According to Neal Ford, continuous delivery adopts "Bring the pain forward," tackling tough tasks early, fostering automation and swift issue detection.

[3] Continuous delivery treats the commonplace notion of a deployment pipeline[4] as a lean Poka-Yoke:[5] a set of validations through which a piece of software must pass on its way to release.

According to Yan Cui, when it comes to serverless environments, ephemeral resources should be kept together and have their own deployment pipeline to achieve a high cohesion.

However, shared resources that have a long spin-up time and landing zone should have their own separate repository, deployment pipeline and stack.

[10] To practice continuous delivery effectively, software applications have to meet a set of architecturally significant requirements (ASRs) such as deployability, modifiability, and testability.

[12] The original CD book written by Jez Humble and David Farley (2010) popularized the term; however, since its creation the definition has continued to advance and now has a more developed meaning.

[13] Well-known companies that have this approach include Yahoo!,[14] Amazon,[15] Facebook,[16] Google,[17] Paddy Power[1] and Wells Fargo.