Previously we introduced some very basic aspects of operations management. If we want these fundamental operations to generate greater impact and value, we need to tailor the design and automation to specific operational scenarios, thereby truly enhancing efficiency and stability.
In other words, after getting the basics right, we should move into the stage of scenario-based operations automation aimed at improving efficiency. At this stage, based on my personal experience and suggestions, the first priority should be continuous delivery.
Why start with continuous delivery? If the automation tools we develop within the scope of operations improve operational efficiency, then implementing continuous delivery is the key to enhancing the overall efficiency of the entire R&D system.
Continuous delivery covers the entire lifecycle of an application, involving related aspects such as product, development, testing, operations, and project management.
Starting from the lifecycle perspective naturally reveals the overall scope of automation and leads to holistic planning and design. At this point, any issues that exist in either the development or operations process will be fully exposed. \
So, what should be the main thread to follow? How should different teams…
