Introduction
Lucoa«DevOps practices in software engineering»
INTRODUCTION
Traditionally, the development team roughly divided into developers — people who knew how to write code, and administrators — who works with systems, networks, databases and know the infrastructure.
So, the administrators were interested in keeping processes stable to minimize the chance of software conflicts, while developers mostly cared about new features, new versions, and bug fixes. The developers and operations were isolated of each other, which resulted in a lack of cooperation and communication between development and operations teams. Eventually, the software could not be delivered at a desired fast pace.
There is currently a core, chronic conflict that exists in almost every IT organization. It is so powerful that it practically pre-ordains horrible outcomes, if not abject failure. It happens in both large and small organizations, for-profit and non-profit, and across every type of industry. In fact, this destructive pattern is the root cause of one of the biggest problems IT production face. But, if it can be vanquished, then the whole world has the potential to generate more economic value than in the previous 30 years.
Current software engineering markets need new techniques of development software which can solve the trouble of continuous release. DevOps is the practice of operations and development engineers participating together in the entire service lifecycle, from design through the development process to production support. DevOps is also characterized by operations staff making use many of the same techniques as developers for their systems work. The planned result of the following work is to answer the question: how can DevOps practices solve the trouble of continuous release?