Operations and Continuous Delivery In the era of Internet product development, product iterations are becoming more and more frequent, and the stage from completion of functional development to successful deployment is called the "last mile" of software development. The level of engineering skills of a team is directly reflected in the code deployment. When I meet people from other companies, they like to ask how you deploy code, which is very eye-opening. It is hard to believe that many (large-scale) companies still manually SSH to a dozen or twenty machines to git pull, manually restart the server, and deploy code for several hours - so primitive, they deserve to work overtime :) Continuous deployment is the rapid delivery of high-quality products through automated build, test, and deployment cycles. To some extent, it represents the degree of engineering of a development team. After all, the labor cost of a fast-running Internet company is higher than that of machines. Investing in machines to optimize development processes also improves human efficiency and maximizes engineering productivity. Key points for successful continuous deployment An automated system for continuous integration and continuous deployment is not that simple. If you do not use other CI services, the development workload is no different from that of a standard large-scale Internet business system. If you have no experience in continuous deployment, you should pay attention to the following in order to successfully carry out continuous deployment: Adequate and extensive automated test coverage; The test feedback time should be as short as possible; Automation of the deployment process; The deployment process must ensure data security; Deploy as early as possible under the premise of stability; Comprehensive risk mitigation measures; Deploy the same product to different environments Continuous Delivery Capability Maturity Model The Operational View of Continuous Delivery 1. From continuous receipt to continuous delivery, the core transformation of operation and maintenance 2. Operation and maintenance have mastered the most important entry point for continuous delivery: CMDB and continuous delivery 3. Final evaluation of delivery: quality, efficiency, and cost 4. Continuous delivery is the core practice of breaking down departmental walls 5. The essence of continuous delivery: standardization + platformization + service and user-oriented value 6. Global optimization based on the delivery chain (Dev/Test/Ops), not local optimization (Ops) 7. The problem of operation and maintenance is not just an operation and maintenance problem, it is an IT problem 8. Operations and maintenance are closest to users. You represent users and have the greatest driving force. 9. Cross-border business is born |
>>: ITU releases draft specification, a big step forward in 5G standardization
[[189050]] When 5G is widely mentioned, network s...
Currently, nearly 100 operators around the world ...
Continue from the previous article "Introduc...
[[408806]] This article is reprinted from the WeC...
Friendhosting launched a promotion for Christmas ...
【51CTO.com Quick Translation】 "I didn't ...
"I missed Lenovo 10 years ago, but I cannot ...
The New Year is coming, say goodbye to 2018, and ...
Today I tweeted some thoughts about how the OSI m...
The core network is the brain of the entire commu...
Xiao Yaqing, Minister of Industry and Information...
The three major US mobile operators AT&T, T-M...
Whether it is the implementation of ITIL in the e...
Tencent Cloud has launched the Double 11 warm-up ...
In accordance with the requirements of blockchain...