The DevOps Handbook - The Technical Practices of Flow

Deployment Pipeline

The deployment pipeline is the backbone of effective DevOps practices. Alan Underwood and Joe Zack discuss how continuous delivery minimizes risks associated with deploying changes by automating the process and ensuring that the trunk is always deployable 1. They highlight Google's transformation, where automation turned one of their least productive teams into one of the most productive, thanks to increased confidence and streamlined processes 2.

The trunk should always be deployable. Always.

--- Joe Zack

This approach allows developers to integrate and test their code frequently, catching issues early and maintaining a steady flow of updates.

   

Trunk-based Development

Trunk-based development emphasizes frequent integration of small changes into the main branch to reduce integration issues. Joe Zack explains that this method scales not just systems, but also teams and their capabilities 3. By committing code to the trunk daily, developers ensure that their changes are quickly tested and integrated, fostering a culture of continuous improvement 4.

DevOps is really a way about scaling the people and the work that you're doing.

--- Joe Zack

This practice helps maintain a deployable state, making it easier to identify and fix issues promptly.

   

Immutable Infrastructure

Immutable infrastructure treats servers as disposable resources, rebuilt rather than repaired. Joe Zack notes that this approach enhances team productivity by ensuring that changes are documented and reproducible 5. This method also facilitates horizontal scaling, as infrastructure can be easily replicated 6.

Treat servers like cattle instead of pets.

--- Alan Underwood

By committing infrastructure configurations to source control, teams can automate deployments and maintain consistency across environments.