Samenvatting
The world of system development is changing at a rapid pace. Development (Dev) and Operations (Ops) are being integrated more and more so that solutions can be offered to customers faster and with better quality. The question is how within this new view of DevOps there is room for Agile architecture. This book provides an answer to this question by giving many examples of architectural principles and models that give direction to the design and operation of a DevOps organization. Throughout the book an explanation is given as much as possible per paragraph based on an imaginary Assuritas company. This book consists of various parts, which makes the book modular. So, it does not have to be read from A to Z. After the brief outline of the case company an explanation of how to construct the DevOps organization from an architectural perspective is given. The DevOps service management is then discussed. Both aspects are made clear on the basis of the case company. After explaining how the Dev and Ops roles can be integrated, two useful assessment tools to determine the maturity of DevOps are described. The book concludes with a case in which the choice for an Agile documentation is made based on architectural principles and models. This work on DevOps architecture is an indispensable tool in the design and implementation of a DevOps service organization.
The world of system development is changing at a rapid pace. Development (Dev) and Operations (Ops) are being integrated more and more so that solutions can be offered to customers faster and with better quality. The question is how within this new view of DevOps there is room for Agile architecture. This book provides an answer to this question by giving many examples of architectural principles and models that give direction to the design and operation of a DevOps organization. Throughout the book an explanation is given as much as possible per paragraph based on an imaginary Assuritas company. This book consists of various parts, which makes the book modular. So, it does not have to be read from A to Z. After the brief outline of the case company an explanation of how to construct the DevOps organization from an architectural perspective is given. The DevOps service management is then discussed. Both aspects are made clear on the basis of the case company. After explaining how the Dev and Ops roles can be integrated, two useful assessment tools to determine the maturity of DevOps are described. The book concludes with a case in which the choice for an Agile documentation is made based on architectural principles and models. This work on DevOps architecture is an indispensable tool in the design and implementation of a DevOps service organization.
Thuiswinkel Waarborg