© J. Allspaw and P. Hammond 2009
Building better software on schedule with DevOps
Collaboration Station
Buzzword alert! The term DevOps, which includes components of software development and operations, is being bandied about wherever you look: You'll find abundant references to DevOps in blogs, books, articles, training courses, and software.
This new style of cooperation between developers and admins was released on an unsuspecting audience by John Allspaw and Paul Hammond (among others) at California's Velocity Conference 2009. Their slides [1] describe how techies from the photo community Flickr achieve 10 or more deploys per day.
The approach described by Allspaw and Hammond is now part of everyday business in other Internet companies. "My impression is that you can no longer survive economically as a company with the old work models," said Schlomo Schapiro, System Architect with Immobilienscout24, in an interview with the author.
IT professionals describe themselves as DevOps specialists with increasing frequency, and some companies even have DevOps departments. The "2014 State of DevOps Report" [2] indicates that 31 percent of more than 9,000 respondents see their position as a DevOps Engineer. According to the survey, 16 percent work in a DevOps department.
The report, with 46 percent of respondents from the United States and 25 percent from Europe, was commissioned by Puppet Labs, IT Revolution Press, and ThoughtWorks. Keep in mind that these companies offer software, publications, and services related to DevOps, which means the way this work method is described is likely to be more positive.
My analysis of these self-assessments showed the following: Departments with above average performance use DevOps techniques. The deployment frequency, the time required for changes, and the mean time to recover are used as the metrics for determining the IT department's performance in the case study. This
...
Buy this article as PDF
(incl. VAT)
Buy ADMIN Magazine
US / Canada
UK / Australia
Related content
-
Common DevOps Mistakes
From industry metaphors, to agile processes, to DevOps, software development is evolving into a mature enterprise. We point out some missteps in the adoption of the DevOps methodology. -
A REST API automation strategy for DevOps
Making resources available through REST APIs breaks down the automation silos that cater to the different IT and development environments and sets up an application-centric automation approach. -
Container technology and work organization
DevOps and container technology often appear together. If you have one of them, you get the other automatically. However, as the following plea for reason shows, it isn't always that simple. -
Jira, Confluence, and GitLab
Jira, Confluence, and GitLab are very popular DevOps tools and often form the basis for agile work flows. With the right Ansible playbooks, Ubuntu can be turned into an agile work center. -
Setting up DevOps Orchestration Platform
DevOps Orchestration Platform open source framework was developed in Golang and can be used to bootstrap an IT infrastructure dynamically or import details of an existing IT infrastructure locally on VirtualBox or in the Cloud.