| Part of a series on |
| Software development |
|---|
DevOps is the integration and automation of software development and information technology operations.[a] DevOps encompasses the tasks necessary for software development and can lead to both shortening development time and improving the development life cycle.[1] According to American software architect Neal Ford, DevOps, particularly through continuous delivery, employs the "bring the pain forward" principle by tackling challenging tasks early, fostering automation, and enabling swift issue detection.[2]
Although debated,[b][c][d][e] DevOps is generally characterized by three key principles: shared ownership, workflow automation, and rapid feedback. From an academic perspective, Len Bass, Ingo Weber, and Liming Zhu—three computer science researchers from the CSIRO and the Software Engineering Institute—defined DevOps as "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".[6] However, the term is used in multiple contexts. At its most successful, DevOps is a combination of specific practices, culture change, and tools.[7]
History
Proposals to combine software development methodologies with deployment and operations concepts first appeared in the late 80s and early 90s.[8]
In 2009, the first DevOps Days conference was held in Ghent, Belgium. The conference was founded by Belgian IT consultant and practitioner Patrick Debois.[9][10] The conference has now spread to other countries.[11]
In 2012, the first "State of DevOps" report was published by Alanna Brown at Puppet Labs.[12][13][non-primary source needed]
In 2016, the DORA metrics for throughput (deployment frequency, lead time for changes), and stability (mean time to recover, change failure rate) were published in that year's State of DevOps report.[12] However, the research methodology and metrics were criticized by some experts.[14][15][16] In response to these criticisms, the 2023 State of DevOps report[17] published changes that updated the stability metric "mean time to recover" to "failed deployment recovery time" acknowledging the confusion the previous metric had caused.[18]
The 2024 report restructured the metrics framework by moving failed deployment recovery time from stability to throughput and introducing a new "rework rate" metric measuring the proportion of unplanned deployments made to fix user-visible issues.[19] In 2025, DORA moved away from sorting teams into performance tiers and instead introduced seven team archetypes that combine delivery metrics with human factors like burnout, friction, and perceived value.[20]
Relevant metrics
DevOps Research and Assessment (DORA) has developed a set of metrics which are intended to measure software development efficiency and reliability. These metrics include:[21][22]
- Deployment Frequency: Time between code deployments.
- Mean Lead Time for Changes: Time between code commit and deployment.
- Change Failure Rate: Percentage of deployments causing production issues.
- Failed Deployment Recovery Time (formerly Mean Time to Recover)
- Reliability: Measures operational performance by focusing on availability and adherence to user expectations.
Relationship to other approaches
Many of the ideas fundamental to DevOps are similar to other well-known practices, such as Lean and Deming's Plan-Do-Check-Act cycle, The Toyota Way, and the Agile approach of breaking down components and batch sizes.[23] Contrary to the "top-down" prescriptive approach and rigid framework of ITIL in the 1990s, DevOps is "bottom-up" and flexible, having been created by software engineers for their own needs.[24]
Agile
The motivations for what has become modern DevOps and several standard DevOps practices such as automated build and test, continuous integration, and continuous delivery originated in the Agile world, which informally dates to the 1990s and formally to 2001. Agile development teams using methods such as extreme programming couldn't "satisfy the customer through early and continuous delivery of valuable software"[25] unless they took responsibility for operations and infrastructure for their applications, automating much of that work. Because Scrum emerged as the dominant Agile framework in the early 2000s and it omitted the engineering practices that were part of many Agile teams, the momentum to automate operations and infrastructure functions splintered from Agile and expanded into what has become modern DevOps. Today, DevOps focuses on deploying methodology-agnostic, developed software.
ArchOps
ArchOps starts from software architecture artifacts instead of source code for operational deployment, as opposed to DevOps.[26] ArchOps holds that architectural models are first-class entities in software development, deployment, and operations.
Continuous Integration and Delivery (CI/CD)
CI/CD is as critical to DevOps success as automation.[27] Additionally, improved collaboration and communication between and within teams helps them achieve faster time to market with reduced risks.[28]
Database DevOps
Database DevOps applies DevOps and CI/CD principles directly to database development and operations. Integrating schema changes, migrations, reference data, and other data-layer updates into the same version-controlled and automated pipelines used for application code enables more reliable deployments. This approach also enables improved coordination between application and data changes.[29][30]
Typical database DevOps practices include placing database schema definitions under version control, applying automated tests (such as unit tests or migration validation) to database changes, and deploying those changes through CI/CD pipelines. These practices reduce what is commonly referred to as "schema drift" between development and production systems and lower the risk of deployment failures.[31][32]
Mobile DevOps
Mobile DevOps is a methodology that applies DevOps' principles to the development of mobile applications. Traditional DevOps focuses on streamlining the general software development process, but mobile development has unique challenges that require a tailored approach.[33] Mobile DevOps is not simply a branch of DevOps specific to mobile app development, but rather an extension and reinterpretation of the DevOps philosophy tailored to mobile's specific requirements.
Site Reliability Engineering
In 2003, Google developed site reliability engineering (SRE), an approach for releasing new features continuously into large-scale, high-availability systems while maintaining a high-quality end-user experience.[34] While SRE predates the development of DevOps, they are generally viewed as being related to each other. Some of the original authors of the discipline consider SRE as an implementation of DevOps.[35]
Toyota Production System, Lean Thinking, Kaizen
The Toyota Production System (TPS), inspired lean thinking with its focus on continuous improvement, kaizen, flow, and small batches. The andon cord principle of creating fast feedback, swarming, and solving problems stems from TPS.[36][37]
DevSecOps, Shifting Security Left
As its name implies, DevSecOps integrates DevOps within security practices. Contrary to a traditional centralized security team model, each delivery team is empowered to factor the correct security controls into their software delivery. Teams perform tests and implement security practices earlier in the development lifecycle, hence the term "shift left". Security is tested in three main areas: static, software composition, and dynamic.
Checking software statically via static application security testing (SAST) is white-box testing with special focus on security. Depending on the programming language, different tools are needed to do such static code analysis. The software composition is analyzed, especially libraries, and the version of each component is checked against vulnerability lists published by CERT and other expert groups. When giving software to clients, library licenses and their match to the license of the software distributed are in focus, especially copyleft licenses.
In dynamic testing, also called black-box testing, software is tested without knowing its inner functions. In DevSecOps this practice may be referred to as dynamic application security testing (DAST) or penetration testing. The goal is early detection of defects including cross-site scripting and SQL injection vulnerabilities.
Often, detected defects from static and dynamic testing are triaged and categorized under taxonomies like the Common Weakness Enumeration (CWE), maintained by the Mitre Corporation. This facilitates the prioritization of security bug fixes and also allows frequently recurring weaknesses to be fixed with recommended mitigations. As of 2025, CWE maintained its own list of frequently-occurring weaknesses, the CWE Top 25.[38] In addition, organizations like Open Worldwide Application Security Project (OWASP) maintain lists of industry-wide frequently recurring software weaknesses.[39]
DevSecOps has also been described as a cultural shift involving a holistic approach to producing secure software by integrating security education, security by design, and security automation.[40]
Culture
DevOps initiatives can change how a company's operations, developers, and testers collaborate during development and delivery processes.[41][42]
DevOps attempts to support consistency, reliability, and efficiency within an organization. This is usually enabled by a shared code repository or version control.[43] Many organizations use version control to facilitate DevOps automation technologies like virtual machines, containerization (or OS-level virtualization), and CI/CD,[44] with the Git version control system and the GitHub platform referenced as examples.
GitOps
GitOps evolved from DevOps. It takes its name from the popular version control system Git, and the specific state of deployment configuration is also version-controlled. Configuration changes can be managed using code review practices, and can be rolled back using version-controlling. Essentially, all of the changes to a code are tracked, bookmarked, and making any updates to the history can be made easier. As explained by Red Hat, "visibility to change means the ability to trace and reproduce issues quickly, improving overall security."[45]
DataOps
DataOps is a set of practices, processes and technologies that combines an integrated and process-oriented perspective on data with automation and methods from agile software engineering to improve quality, speed, and collaboration and promote a culture of continuous improvement in the area of data analytics.[46] While DataOps began as a set of best practices, it has now matured to become a new and independent approach to data analytics.[47] DataOps applies to the entire data lifecycle[48] from data preparation to reporting, and recognizes the interconnected nature of the data analytics team and information technology operations.[49]
DataOps incorporates the Agile methodology to shorten the cycle time of analytics development in alignment with business goals. [48]
DevOps focuses on continuous delivery by leveraging on-demand IT resources and by automating test and deployment of software. This merging of software development and IT operations has improved velocity, quality, predictability and scale of software engineering and deployment. Borrowing methods from DevOps, DataOps seeks to bring these same improvements to data analytics.[49]
DataOps utilizes statistical process control (SPC) to monitor and control the data analytics pipeline. With SPC in place, the data flowing through an operational system is constantly monitored and verified. If an anomaly occurs, the data analytics team can be notified with an automated alert.[50]
DataOps is not tied to a particular technology, architecture, tool, language or framework. Collaboration, orchestration, quality, security, access and ease of use are important principles in DataOps workflows.[51]
History
DataOps was first introduced by InformationWeek contributing editor Lenny Liebmann in a blog post on the IBM Big Data & Analytics Hub titled "3 reasons why DataOps is essential for big data success" on June 19, 2014.[52] The term DataOps was later popularized by Andy Palmer of Tamr and Steph Locke.[53][49] DataOps is a moniker for "Data Operations."[48] 2017 was a significant year for DataOps, with significant ecosystem development, analyst coverage, increased keyword searches, surveys, publications, and open source projects.[54] Gartner placed DataOps on the Hype Cycle for Data Management in 2018.[55]
Goals and philosophy
The total world data volume is forecast to grow at a rate of 32% CAGR to 180 Zettabytes by 2025 (Source: IDC).[51] DataOps seeks to provide the tools, processes, and organizational structures to accommodate this significant increase in data.[51] Automation streamlines data preboarding, ingestion, and the management of large integrated databases, freeing the data team to develop new analytics in a more efficient and effective way.[56][49] DataOps seeks to increase velocity, reliability, and quality of data analytics.[57] It emphasizes communication, collaboration, integration, automation, measurement and cooperation between data scientists, analysts, data/ETL (extract, transform, load) engineers, information technology (IT), and quality assurance/governance.
See also
- AIOps – Artificial intelligence in IT operations
- DevOps toolchain – Tools for software development
- Infrastructure as code – Data center management method
- Lean software development – Use of lean manufacturing principles in software development
- List of build automation software
- Platform engineering - The practice of building and running self-service internal tooling and infrastructure
- Site reliability engineering – Use of software engineering practices for IT
- Value stream – Principle in economics
- Twelve-Factor App methodology – Software methodology
Notes
- ↑ a portmanteau of development operations
- ↑ Dyck et al. (2015) "To our knowledge, there is no uniform definition for the terms release engineering and DevOps. As a consequence, many people use their own definitions or rely on others, which results in confusion about those terms."[3]
- ↑ Jabbari et al. (2016) "The research results of this study showed the need for a definition as individual studies do not consistently define DevOps."[4]
- ↑ Erich et al. (2017) "We noticed that there are various gaps in the study of DevOps: There is no consensus of what concepts DevOps covers, nor how DevOps is defined."[5]
- ↑ Erich et al. (2017) "We discovered that there exists little agreement about the characteristics of DevOps in the academic literature."[5]
References
- ↑ Courtemanche, Meredith; Mell, Emily; Gills, Alexander S. "What Is DevOps? The Ultimate Guide". TechTarget. Retrieved 2023-01-22.
- ↑ Building Evolutionary Architectures: Automated Software Governance. ISBN 978-1-4920-9754-9.
- ↑ Dyck, Andrej; Penners, Ralf; Lichter, Horst (2015-05-19). "Towards Definitions for Release Engineering and DevOps". 2015 IEEE/ACM 3rd International Workshop on Release Engineering. IEEE. p. 3. doi:10.1109/RELENG.2015.10. ISBN 978-1-4673-7070-7. S2CID 4659735.
- ↑ Jabbari, Ramtin; bin Ali, Nauman; Petersen, Kai; Tanveer, Binish (May 2016). "What is DevOps?: A Systematic Mapping Study on Definitions and Practices". Proceedings of the 2016 Scientific Workshop. Association for Computing Machinery.
- 1 2 Erich, F.M.A.; Amrit, C.; Daneva, M. (June 2017). "A Qualitative Study of DevOps Usage in Practice" (PDF). Journal of Software: Evolution and Process. 29 (6) e1885. doi:10.1002/smr.1885. S2CID 35914007.
- ↑ Bass, Len; Weber, Ingo; Zhu, Liming (2015). DevOps: A Software Architect's Perspective. Addison-Wesley. ISBN 978-0-13-404984-7.
- ↑ Muñoz, Mirna; Negrete Rodríguez, Mario (2021-04-01). "A guidance to implement or reinforce a DevOps approach in organizations: A case study". Journal of Software: Evolution and Process. 36 (3). Wiley. doi:10.1002/smr.2342.
- ↑ Chapman, M., Gatti, N: A model of a service life cycle, Proceedings of TINA '93, pp. I-205–I-215, Sep., 1993.
- ↑ Mezak, Steve (25 January 2018). "The Origins of DevOps: What's in a Name?". devops.com. Retrieved 6 May 2019.
- ↑ Debois, Patrick (9 October 2008). "Agile 2008 Toronto". Just Enough Documented Information. Retrieved 12 March 2015.
- ↑ Debois, Patrick. "DevOps Days". DevOps Days. Retrieved 31 March 2011.
- 1 2 Alana Brown; Nicole Forsgren; Jez Humble; Nigel Kersten; Gene Kim (2016). "2016 State of DevOps Report" (PDF). Puppet Labs, DORA (DevOps Research. Retrieved 2024-04-24.
- ↑ "Puppet - Alanna Brown". Puppet Labs. Retrieved 2019-04-27.
- ↑ Turner, Graham (20 November 2023). "Report: Software Engineers Face Backlash for Reporting Wrongdoing". DIGIT. Retrieved 5 January 2024.
- ↑ Saran, Cliff. "Software engineers worry about speaking out - Computer Weekly". ComputerWeekly.com. Retrieved 5 January 2024.
- ↑ "75% of software engineers faced retaliation the last time they reported wrongdoing - ETHRWorldSEA". ETHRWorld.com.
- ↑ DeBellis, Derek; Lewis, Amanda; Villalba, Daniella; Farley, Dave. "2023 State of DevOps Report". Google Cloud DevOps Research and Assessment. Retrieved 2024-04-24.
- ↑ DeBellis, Derek; Harvey, Nathan. "2023 State of DevOps Report: Culture is everything". Google Cloud Blog. Retrieved 2024-04-24.
- ↑ Stephens, Rachel (November 26, 2024). "DORA Report 2024 - A Look at Throughput and Stability". RedMonk. Retrieved May 11, 2026.
- ↑ "Accelerate State of DevOps Report 2024". DORA, Google Cloud. Retrieved May 11, 2026.
- ↑ Forsgren, Nicole. Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations. ISBN 978-1-942788-33-1.
- ↑ "DORA Accelerate State of DevOps 2021". DevOps Research and Assessment (2021). 2021.
- ↑ Klein, Brandon Thorin (2021-05-01). "The DevOps: A Concise Understanding to the DevOps Philosophy and Science". Osti.gov. doi:10.2172/1785164. OSTI 1785164. S2CID 236606284.
- ↑ "The History and Evolution of DevOps | Tom Geraghty". 5 July 2020. Retrieved 2020-11-29.
- ↑ "Principles behind the Agile Manifesto". agilemanifesto.org. Retrieved 2020-12-06.
- ↑ Castellanos, Camilo; Correal, Dario (15 September 2018). "Executing Architectural Models for Big Data Analytics". Software Architecture. Lecture Notes in Computer Science. Vol. 11048. pp. 364–371. doi:10.1007/978-3-030-00761-4_24. ISBN 978-3-030-00760-7.
- ↑ Humble, Jez; Farley, David (2011). Continuous Delivery: reliable software releases through build, test, and deployment automation. Pearson Education Inc. ISBN 978-0-321-60191-9.
- ↑ Chen, Lianping (2015). "Continuous Delivery: Huge Benefits, but Challenges Too". IEEE Software. 32 (2): 50–54. doi:10.1109/MS.2015.27. S2CID 1241241.
- ↑ Fluri, Jasmin; Fornari, Fabrizio; Pustulka, Elzbieta (2024). "On the importance of CI/CD practices for database applications". Journal of Software: Evolution and Process. doi:10.1002/smr.2720. Retrieved 2025-08-24.
- ↑ Shahin, Mojtaba; Ali Babar, Muhammad; Zhu, Liming (2017). "Continuous Integration, Delivery and Deployment: A Systematic Review on Approaches, Tools, Challenges and Practices". IEEE Access. 5: 3909–3943. arXiv:1703.07019. doi:10.1109/ACCESS.2017.2685629. Retrieved 2025-08-24.
- ↑ "Database Change Management". DORA. Retrieved 2025-08-24.
- ↑ "A Guide to Database DevOps". Liquibase. Retrieved 2025-08-24.
- ↑ Tak, Rohin; Modi, Jhalak (2018). Mobile DevOps: Deliver continuous integration and deployment within your mobile applications. Packt Publishing. pp. 12–18. ISBN 978-1-78829-624-3.
- ↑ Beyer, Betsy; Jones, Chris; Petoff, Jennifer; Murphy, Niall Richard (April 2016). Site Reliability Engineering. O'Reilly Media. ISBN 978-1-4919-2909-4.
- ↑ Dave Harrison (9 Oct 2018). "Interview with Betsy Beyer, Stephen Thorne of Google". Retrieved 24 July 2024.
- ↑ Analyzing the DNA of DevOps, Brent Aaron Reed, Willy Schaub, 2018-11-14.
- ↑ Gene Kim; Patrick Debois; John Willis; Jezz Humble (2016). The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations.
- ↑ "CWE Top 25 Most Dangerous Software Weaknesses". Retrieved September 21, 2025.
- ↑ "OWASP TOP10". Archived from the original on June 8, 2023. Retrieved June 8, 2023.
- ↑ Wilson, Glenn (December 2020). 'DevSecOps: A leader's guide to producing secure software without compromising flow, feedback and continuous improvement'. Rethink Press. ISBN 978-1-78133-502-4.
- ↑ Emerging Technology Analysis: DevOps a Culture Shift, Not a Technology (Report). Gartner.
- ↑ Loukides, Mike (7 June 2012). "What is DevOps?". O'Reilly Media.
- ↑ Teja Yarlagadda, Ravi (9 March 2021). "DevOps and Its Practices". SSRN 3798877.
- ↑ Morisio, Maurizio (16 April 2021). DevOps: development of a toolchain in the banking domain. Politecnico di Torino (laurea thesis). Retrieved 16 August 2021.
- ↑ "What is GitOps?". www.redhat.com. Retrieved 2023-03-30.
- ↑ Ereth, Julian (2018). "DataOps-Towards a Definition" (PDF). Proceedings of LWDA 2018: 109.
- ↑ "DataOps – It's a Secret". www.datasciencecentral.com. Retrieved 2017-04-05.
- 1 2 3 "What is DataOps (data operations)? - Definition from WhatIs.com". SearchDataManagement. Retrieved 2017-04-05.
- 1 2 3 4 "From DevOps to DataOps, By Andy Palmer - Tamr Inc". Tamr Inc. 2015-05-07. Archived from the original on 2018-07-12. Retrieved 2017-03-21.
- ↑ DataKitchen (2017-03-07). "Lean Manufacturing Secrets that You Can Apply to Data Analytics". Medium. Retrieved 2017-08-24.
- 1 2 3 "What is DataOps? | Nexla: Scalable Data Operations Platform for the Machine Learning Age". www.nexla.com. Retrieved 2017-09-07.
- ↑ "3 reasons why DataOps is essential for big data success". IBM Big Data & Analytics Hub. Archived from the original on 2018-08-10. Retrieved 2018-08-10.
- ↑ Mango Solutions: #DataOps - it's a thing (honest), retrieved 2021-06-28
- ↑ DataKitchen (2017-12-19). "2017: The Year of DataOps". data-ops. Retrieved 2018-01-24.
- ↑ "Gartner Hype Cycle for Data Management Positions Three Technologies in the Innovation Trigger Phase in 2018". Gartner. Retrieved 2019-07-19.
- ↑ "5 trends driving Big Data in 2017". CIO Dive. Retrieved 2017-09-07.
- ↑ "Unravel Data Advances Application Performance Management for Big Data". Database Trends and Applications. 2017-03-10. Retrieved 2017-09-07.
Further reading
- Davis, Jennifer; Daniels, Ryn (2016-05-30). Effective DevOps: building a culture of collaboration, affinity, and tooling at scale. Sebastopol, CA: O'Reilly. ISBN 978-1-4919-2643-7. OCLC 951434424.
- Kim, Gene; Debois, Patrick; Willis, John; Humble, Jez; Allspaw, John (2015-10-07). The DevOps handbook: how to create world-class agility, reliability, and security in technology organizations (First ed.). Portland, OR. ISBN 978-1-942788-00-3. OCLC 907166314.
{{cite book}}: CS1 maint: location missing publisher (link) - Forsgren, Nicole; Humble, Jez; Kim, Gene (27 March 2018). Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations (First ed.). IT Revolution Press. ISBN 978-1-942788-33-1.
