DevOps Architecture Part I

Dive into the intersection of the architect's role and the engineering practices at the heart of continuous delivery, covering continuous integration, deployment pipelines and how to structure them (including automating architecture governance), and best practices and anti-patterns. Learn concrete engineering practices, such as automated machine provisioning, release strategies, and how feature toggles offer better continuous delivery than branches. You'll learn about migrating and evolving architectures, particularly how to understand enough about your architecture to restructure it. You'll leave with the knowledge and tools to immediately put these ideas into practice in your own projects.

Yesterday's best practice is tomorrow's anti-pattern. Everything in software continues to shift and move including architecture, a painful lesson developers who build logically sound but operationally cumbersome architectures quickly learn. Continuous delivery—a process for automating the production readiness of your application every time a change occurs to code, infrastructure, or configuration—enables you to better address these shifts head-on.

The difference between continuous integration and continuous delivery
The difference between continuous delivery and continuous deployment
How to structure deployment pipeline stages
The role of DevOps in continuous delivery
Continuous delivery release strategies and tools
How to restructure architectures
How to evolve architectures via fitness functions