But how so, there is the same DevOps Handbook, the most authoritative source. It has a whole section devoted to myths about DevOps, why write an article? Well, the fact is that, in my opinion, this book not only explains the methodology, but also sells it in places.
And the section on myths in it is such and contains myths that I would like to refute to the authors, and not those that are popular in reality. Immediately I tried to describe the myths that circulate in the real world, and which I had to deal with, explaining the methodology to my listeners.
1. DevOps is applicable to you
No, DevOps is not for everyone. This myth comes first because some of the founding fathers themselves are gradually promoting it.
For example, Gene Kim et al. In The DevOps Handbook somehow forgets to mention that DevOps is not for everyone, but speculates on its universal applicability. Rate the quote (I highlighted the problem parts in italics ): “... there is now an overwhelming weight of evidence that the problems described above happen almost everywhere , and that the solutions associated with DevOps are nearly universally applicable .” Or here: “In almost every IT organization, there is an inherent conflict between Development and IT Operations which creates a downward spiral ...”.
Well, no, there are a bunch of IT organizations for which all this does not work at all or in part, even if they are not applicable. There are organizations that do not have an IT operations department or productive environment at all. For example, organizations that are engaged in consulting. Often they may have a support department that enforces SLA, but they may not have it at all: companies that implement Wordpress, for example, or consultants who do security testing. There are IT organizations without a development department. Many hosting companies are such organizations. Everything can be arranged for them quite complicatedly, but all the software can be either someone else's “boxed”, or “cloud”, or written by external consultants.
( , ?): “No matter what industry you are in, or what product or service your organization provides, this way of thinking is paramount and necessary for survival for every business and technology leader.”
, , . DevOps — ? , .
2. DevOps
DevOps - -. , , DevOps . :
DevOps . DevOps - , DevOps Chrome .
, DevOps. , . 1.0.0. 1.0.1? , , , . “” .
, , :
- (Time to Market, TTM),
- ,
- -,
, , DevOps .
3. DevOps -
“10 Deploys a Day” Flickr — , -.
, , DevOps, -. , , , , .
“” , - DevOps.
4. DevOps —
, DevOps — -, , , , , “ ”.
, DevOps, DevOps , .
Time to Market , .
- . , , , . “”, .
, , DevOps .
, , . , , .
5. DevOps -
- - - DevOps Server Ultimate 9000 — ?
. , DevOps , , , Linux, git bash. ? — . ? . DevOps . Docker, , Puppet git. , . — Jenkins, — Bamboo, , , TeamCity, GNU Make . , — , , .
. Scrum. Scrum — Agile, , , . - Agile, . DevOps — Agile, Scrum. , “” DevOps Lean. Lean — , , - -, - . , Lean. DevOps.
6. DevOps
, “ ”, : , , QA ..
, . , - — .
— DevOps, , , , DevOps-.
7. DevOps
— — ? . -, DevOps . - DevOps — -, . , DevOps — , , . , Toyota, GM Ford.
, Lean “” Kanban , DevOps 50, CD — 80.
Scrum ? . , . (TTM) , 17.6 , TTM 2 .
, IT, . , DevOps, . , , . , , , ?
In any case, the entire amount of accumulated knowledge, and not just DevOps, will help to better organize work.
There are others
This concludes my short review of the myths about DevOps that do not circulate in reality. Next time I will describe popular misconceptions, which, although not incorrect, but in which there is some truth.
And what myths or deliberately imposed delusions about DevOps have you encountered?