Michael Davis over at InformationWeek just wrote a compelling article on DevOps and some of the mixed results that people are understandably getting into. There are a number of very interesting results that he shares as part of their DevOps survey including:
8 of 10 companies say they've realized or expect to see at least some improvement in app deployment speed and infrastructure stability as a result.
75% of tech pros know about DevOps, yet only 21% of those familiar with it are using it (21% say they expect their organizations to adopt DevOps principles within a year).
31% have realized or expect significant improvement, but 51% say it's only "some improvement." However, only a mere 3% have seen or expect no improvement (15% think it's too soon to tell).
A few salient points were made throughout the article worth noting:
1. Everyone recognizes that Development & Operations are motivated by different goals. It’s refreshing to finally see someone talk about Architecture before automation. Michael has taken the view up one level again and focused in on the first part of the chain. These guys are often the missing part of the conversation and given they can determine an enterprise technology standard/strategy, it’s great to see it being called out so clearly.
2. Security is part of the conversation, most DevOps would cringe if they actually knew the amount of risk they were introducing into an environment. Security is presumed to be the shrill, hysterical, nonsensical group within IT, but I don't think anyone would say that at the end of the day they don't all want the same thing.
3. What’s actually missing is that not everyone can write scripts or transfer knowledge.
4. The piece de la resistance is the following: The very tools that automate the infrastructure, such as Puppet, Chef, or custom scripts, can drag down the infrastructure if they fail. One bad script could bring down your infrastructure, just as one bad patch update did before DevOps. An essential part of the IT architect's work is knowing the details of how the infrastructure's automation works in order to determine the impact an application change will have.