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
[[398027]] 2021-05-08 09:07Focus, broadcast on th...
Preface Have you ever had this experience? A larg...
2019 is the first year of 5G. With the issuance o...
Patch panels are important network components tha...
[[419549]] Preface The previous article demonstra...
V5.NET is a business that provides independent se...
[51CTO.com original article] As an indispensable ...
With the progress and development of human societ...
[[434445]] According to foreign media reports, af...
The ping command is used to test the connection t...
The small signal coverage range of 5G base statio...
The tribe has not shared information about VirMac...
This article is reproduced from the WeChat public...
When it comes to industrial communication protoco...
One of the benefits of the Internet age is that w...