Home >

Bass, Len et al. DevOps. A Software Architect's Perspective

Posted on April 4, 2014

Definitions

DevOps

DevOps is a set of practices intended to reduce the time between committing a change to a system and the change being placed into normal production, while ensuring high quality. (Len et al., 2015, p. 4)

DevOps Roles

Team structure as suggested by (Len et al., 2015, pp. 15–32):

• Service Owner: the role responsible for outside coordination and the prioritisation of work items for the team and provides the team with information both from the clients of the team’s service and about services provided to the team. This role also communicates the vision for the service.

• Reliability Engineer: the role responsible for monitoring the service in the time period immediately subsequent to the deployment. This role is also the point of contact with the service during its execution. He or she performs short-term analysis to diagnose, mitigate, and repair a problem when it arises—usually with the assistance of automated tools.

Quotes

Why DevOps

“DevOps, in many ways, is a response to the problem of slow releases.” (Len et al., 2015, p. 7)

Reference

@book{bass2015,
author = {Bass Len and Weber Ingo and Zhu Liming},
title = {{DevOps: A Software Architect's Perspective}},
year = {2015},
isbn = {0134049845, 9780134049847},
edition = {1st},
}