We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

(Re-)architecting for Continuous Delivery

Formal Metadata

Title
(Re-)architecting for Continuous Delivery
Title of Series
Number of Parts
150
Author
License
CC Attribution - NonCommercial - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Continuous delivery can be considered a cross-functional requirement, rather like testability and maintainability. In the first part of this talk I'll explore the implications of continuous delivery for your systems architecture. The second part will present patterns that successful organizations have used to enable continuous delivery. In the final part, I'll discuss the architectural and organizational obstacles presented by by typical legacy "big ball of mud" systems, and what can be done to incrementally move away from them.