What Is DevOps?

DevOps is an approach to software development management that joins software development and information technology operations into a single delivery process, supported by automation, shared measurement, and shared responsibility for systems in production. The name is a contraction of development and operations, and it emerged around 2009 from practitioner conferences that argued the traditional handoff between the team writing code and the team running it was the main source of delay and outage risk. Practitioners often summarize the scope with the initialism CAMS: culture, automation, measurement, and sharing.

DevOps is best understood as a set of practices and an organizational arrangement rather than a tool category or a job title, although vendors and job listings routinely use it as both. It overlaps with agile software development, which it extends past the point of code completion, and with site reliability engineering, which addresses much the same problem from an operations starting point.

Continuous Integration and Delivery

The technical backbone of DevOps is a pipeline that takes a code change from a developer's working copy to production with minimal manual intervention. Continuous integration requires developers to merge small changes into a shared trunk frequently, with an automated build and test suite run on every commit so that integration defects surface within minutes rather than at the end of a release cycle. Continuous delivery builds on that foundation to keep the trunk in a permanently releasable state, with deployment to production reduced to a decision rather than a project. Research from the DevOps Research and Assessment program on continuous delivery treats continuous integration as one necessary capability among several, alongside trunk-based development, test automation, and deployment automation. The distinction between continuous delivery and continuous deployment matters in regulated settings: the former makes release possible at any time, the latter makes it automatic.

Infrastructure Automation and Observability

Treating servers, networks, and configuration as versioned artifacts is what makes repeatable deployment possible. Infrastructure as code expresses environment definitions in declarative files held in the same version control system as the application, so that a staging environment and a production environment differ by parameters rather than by accumulated manual changes. Containers and orchestration platforms narrow the gap between developer machine and production runtime. On the operations side, structured logging, metrics, and distributed tracing supply the feedback that makes rapid change safe, since a short mean time to recovery depends on being able to see what changed and what broke. Architectural coupling constrains all of this, and an empirical study of architectural design issues in DevOps documents how monolithic dependencies and shared databases limit how independently teams can deploy.

Measurement and Organizational Practice

DevOps programs are usually assessed through four delivery performance measures: deployment frequency, lead time for changes, change failure rate, and time to restore service. These are deliberately outcome-oriented, since counting tool adoption or pipeline runs does not indicate whether the delivery process improved. The cultural component is equally load-bearing and harder to instrument: blameless postmortems, shared on-call responsibility, and the removal of approval gates that add delay without reducing risk. Surveys of practice in the engineering literature, including work presented at IEEE conferences on continuous and integrated software development using DevOps, consistently report that organizational structure, rather than tooling, is the binding constraint.

Applications

DevOps practices are applied in a range of settings, including:

• Cloud-native web and mobile service delivery
• Enterprise application modernization and legacy migration
• Regulated software delivery under audit and compliance requirements, often termed DevSecOps
• Machine learning model deployment and lifecycle management
• Embedded and automotive software release management
• Telecommunications network function deployment
• Scientific and high-performance computing workflow automation