The shift in thinking is far more valuable than simply lifting the operational dimension

Why do I choose to embark on the road of transport.

Before I joined Mushroom Street, I worked in Huawei for more than seven years and experienced many jobs such as development, testing, operation, and front-line customer service. This experience in Huawei not only quickly enhanced my ability to cultivate my sense of comprehensive thinking, but also let me accumulate a wealth of telecommunications and internet business development and operation experience.

Speaking of it, it is a great contingency to embark on the road of operation and maintenance, mainly because:

First, I do not have the heart to look at themselves and the team worked hard to develop the system to the line is always a problem, so whenever there are problems, I will be the first time to solve the problem, over the years, they have accumulated a wealth of experience, but also become a team of more important role;

Second, and a more important factor, I myself enjoy the sense of accomplishment after overcoming the problem.

Practitioners in this decade, I met these challenges, let me get a lot of valuable practical experience and insights, but also let me have some different thinking about operation.

I think the shift in operational dimension is far more valuable than the mere lifting of operational technology.

I think that, in a research and development team, to remove the business requirements to achieve the level of things, the other is the scope of operations, this category of things in essence is in the software lifecycle of the operation of the maintenance phase of service.

We have learned in the University software engineering, from the software life cycle point of view, the software development phase only accounted for the whole life cycle of 20%~30%, software operation Maintenance phase is the longest tail, this rule in the current era of the same application.

In the software life cycle, we can clearly divide the "development phase" and "operational dimension Stage", which is from the development of the completion of code development, test acceptance, delivery to the operation of the software package started, since then the stage is the operation of the software maintenance phase.

A company's demand for development should be to fully achieve business needs, and will be released as soon as possible to achieve business benefits. But, in a company, in addition to focusing on the development and testing roles of business requirements, there will be another broad category of development, such as our common middleware development, stability development, tool development, monitoring development, IaaS or PAAs platform development, and even focus on the underlying infrastructure of kernel development, network development, Protocol development and so on.

Here, please come with me. In addition to business development and testing, the technical positions mentioned above are for the operational maintenance phase of the software lifecycle, and the role of these roles is to improve research efficiency and stability, thereby reducing costs. While they are not all defined as operational positions, they are essentially directly related to the operational maintenance phase of the business software.

I have done outside sharing, has always expressed a point of view is that operational capacity is the overall technical framework of the embodiment of the operational dimension of the problem or failure, it must be the overall technical framework of the problem, fragmented both, simply look at the technical framework or operational dimensions are meaningless.

However, in the vast majority of cases, we ignore this hidden in the software lifecycle of the real operation of the category, but simply directly from the software lifecycle Segmentation point of view, the development and operation of the dimensions of a rigid line.

It is such a simple direct demarcation, let us only limited to the server maintenance, network equipment configuration, software installation and maintenance of the most end of the responsibility, and we hope that the role of the operation to control the overall situation, do not appear at this stage any problems. This is like the impending thirst and digging well, is not realistic.

Obviously, I think that the transformation of operational dimension is far more valuable than simply upgrading the operational dimension, and the real value of yun-dimensional should be consistent with the research and development team, and truly focus on efficiency, stability and cost.

And that's the biggest pain point and problem that many of our companies and teams are experiencing at the moment. So, in my column, I'm going to share some of my thoughts on these pain points and problems.

What can you see in my column?

Through the "Zhao System Management Class" column, I will do the system content output, with 3 months time to a operational system to speak through. Column content focused on the application of distributed software architecture in this field, more is my thinking about the architecture of operation, there are four main parts:

Application of operation and maintenance system construction. This is the basis of our operation, I will share from the standardization and application lifecycle, how to establish a step-by-step technology system and organizational structure, as well as the whole process of communication and collaboration, and share how we should set up the correct idea of the operation and maintenance.

Best practices in terms of efficiency and stability. These are the embodiment of operational dimension value, I will be around the continuous delivery and stability building two aspects, sharing how to build the End-to-end delivery process without any operational dimension participation, how to temper the stability guarantee system in practice.

Thinking and practice in cloud computing. The development of cloud computing technology provides more possibilities for our business and technology, and using the good cloud platform will be a necessary requirement for the transformation of operation and maintenance upgrades. I will share practical experience in mixed cloud, cloud storage, Static, and CDN, as well as the tremendous cost and experience benefits of these practices.

Personal growth and trend of hot analysis. This part will be more of my personal thinking, including the development of operational technology trends, team management, personal growth, hot event analysis, collision of views and so on.

--------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------------------- ---------------------------------------------------------