How did the evolution of application development lead to DevSecOps?
The first commercial applications were characterized by a monolithic architecture, and their target runtime environment was mostly desktop. The code was developed in isolation, most integration and deployment steps were done manually, and the development and operations teams were separated from each other. In those circumstances, however, this was not a significant problem - the low frequency of releases did not create pressure in terms of speed of implementation, while the priority was software stability. Progressive technological development and growing market requirements, however, increased the pressure to introduce more frequent modifications to the application. The above conditions forced profound changes in the software production process, including the organization, tools used and corporate culture. As a result, a consistent and transparent DevOps methodology was created, the intention of which was to use the best practices to face the new reality.
The DevOps methodology is based on close cooperation of all people working on application development. The proposed integration of development, operational and testing teams is intended to break down organizational silos. A similar emphasis is placed on the team culture, according to which everyone is equally responsible for the quality and safety of the final product. While DevOps does not refer to specific technologies used in software production, their use facilitates the entire process. CI/CD tools, monitoring, configuration and version management or test automation are elements without which it is difficult to imagine a modern application development process.