From the course: Succeeding in DevOps

Setting the stage for DevOps

From the course: Succeeding in DevOps

Setting the stage for DevOps

- Historically, many established software companies followed the same blueprint for software development. Software engineers were hired to build a product, which they did by writing code. Then once that code was considered complete, it would be handed over to a team of operations folks who were responsible for packaging that code into a state where it could be used by customers. These two groups had clashing missions, with software engineers wanting to build new features as quickly as possible and operations engineers wanting to keep systems stable. This led to a pattern where software engineers would metaphorically throw code over the wall to operations. And when operations encountered problems, they would throw it back over that same wall, causing delays in software delivery and poor product quality. However, a new set of practices and roles has emerged to speed up software delivery and reduced the friction between development and operations. This solution is known as DevOps.

Contents