DevOps model is to fill the information gap between the development side and the operation and maintenance side, and improve the collaborative relationship between the teams.
With the complexity of business and the increase of personnel,
developers and operation and maintenance personnel have gradually evolved into two independent departments. Their work locations are separated, tool chains are different, and business goals are also different, which makes a gap between them. To release software is to send a piece of software from one side of the chasm to another, and there are many difficulties.
On the other hand, the industry is more competitive. Both the customer and the company itself require software to be released quickly and frequently modified. The gap mentioned above hinders the productivity of the development team and becomes a problem that companies need to solve urgently.
In the face of various outstanding contradictions, the plot of the story seems to have returned to the time when there were only programmers, rather than subdivided into development, testing, and operation and maintenance positions.
The term DevOps comes from the combination of Development and Operations, and emphasizes the importance of communication and cooperation between software developers and operation and maintenance personnel. Through automated processes, software construction, testing, and release are made faster, more frequent, and more reliable.
DevOps is to fill the information gap between the development side and the operation and maintenance side, and improve the collaborative relationship between the teams. However, it needs to be clarified that from development to operation and maintenance, there is also a test link in the middle. DevOps actually contains three parts: development, testing and operation and maintenance.
In other words, what DevOps hopes to do is to open up the IT tool chain during the delivery of software products, so that each team can reduce time loss and work together more efficiently.
Experts have summarized the following DevOps capability map. A good closed loop can greatly increase the overall output.
Some people think that DevOps means that the developer has taken over the operation. This is only a part, not all. When we realize that some operations need to be automated, operation and maintenance personnel need to perform some automated development, and developers also write "operation and maintenance" code, or both. The scary thing is that there is no overall method of collaboration between these two types of personnel. All successful teams coordinate people with
deep development skills and deep operation and maintenance skills to work together to create a better product.
1. Common DevOps technology
Second, DevOps has three characteristics and modes
2.1. System-level efficiency considerations
This emphasizes the consideration of the efficiency and performance of the entire system rather than the work department or subsystem in isolation. It can be a large perspective for integrating developers and IT operations personnel, or it can be as small as an independent publisher such as a developer and System administrator.
The focus is on the entire business value chain, starting with the confirmation of business needs, the development and construction of developers, and then delivered to IT operation and maintenance. In the final link, the software value for customers is reflected as a service.
Because of the emphasis on overall efficiency, do n’t blame the defects downstream, do not allow the overall degradation due to local optimization, and cannot cause a regression in the overall strategy due to the improvement of detailed tactics. If you want to increase the value of the entire system, you must thoroughly understand whole system.
2.2. Amplify feedback loop
About creating a right-to-left feedback loop. If necessary, this feedback loop can be continuously shortened and enlarged. Ability to understand and respond to all customers, both internal and external, shorten and amplify all feedback loops, and embed the knowledge we need.
2.3, continuous exercise and learning
This approach is to create a corporate culture that fosters two things: constant experimentation and risk-taking and learning from failures. Recognize that repetition and practice are prerequisites for mastery.
Experiments and adventures can ensure that we continue to drive improvement. Even if this means entering a dangerous zone beyond our control, we must need the skills to help us escape from the danger zone.
The results of the third path include allocating time to improve daily work, creating rituals for adventure, rewarding teams, and introducing errors into the system to increase flexibility.
Three, the benefits of DevOps
A huge
benefit of DevOps is that it can be delivered efficiently, which is precisely its original intention. Compared with inefficient organizations, efficient organizations are deployed 200 times more frequently, products are put into service 2555 times faster, and service recovery is 24 times faster. In terms of time allocation of work content, inefficient people spend 22% of their time on planning or repetitive work, while efficient people spend 29% of their time on new work. So efficiency here refers not only to the improvement of the efficiency of the company's output, but also to the improvement of the quality of employees' work.
Another benefit of DevOps is that it improves the company's organizational culture and employees' sense of participation. Employees have become more efficient, satisfied and fulfilled, and have more recognition for the company.
