The leader said he would go online tomorrow, but he didn't know the development process at all

1. Preface

What are the common types of work in Internet companies ？

The launch of a project on the Internet will require the cooperation of various types of work , From the perspective of R & D, we will undertake the demand of products , I'll give it to the test for verification , Finally complete the project delivery online . In addition to that , There will be business 、 operating 、UI Design 、 Operation and maintenance , To cooperate with the initiation of the project 、 Use and maintenance .

Except for one line of work , There is also cross departmental collaboration between the same type of work . such as ：

• Product stage ：A Some of the services in the product , It needs to be supported by another department . Then the products of both sides need to coordinate the time rhythm , Go online with .
• R & D stage ： Undertake the docking function of products across departments , Both sides will define the docking interface 、 Docking time , And the final joint commissioning .
• Testing phase ： According to the function node of the product 、 R & D process and interface description , Conduct test verification .

Final , The alternation of work with the Department 、 Cross departmental collaboration , Ensure that all materials needed in the project development process are on-line on schedule .

Now let's talk about , The implementation process of each stage of the project launch . Of course , Not all development is carried out according to this process .​ According to the size of the company 、 The size of the project 、 There are some differences in the patterns of Architecture . therefore , Just for reference , There is no need to force convergence .

---

2. Time rhythm

• matter ： Define the project development time node
• personnel ： Business 、 product 、 R & D team leader 、 Test team leader 、 Architects 、 Core project members
• describe ： This definition of tempo is very important , It can be project manager initiated or product initiated . Most of the time, Internet companies send a project , I often hear the boss say I want to go to work at this time . Maybe this sentence seems unreasonable , But to survive , In order to stop the market quickly , When you press down to the bottom, the executive is a time when you have to go online . but , If you want to meet the online time , Then we need to confirm the overall time rhythm . For example, when will the business and products confirm the requirements clearly , When and when did R & D work PRD, When will R & D develop to test , When will the test be completed . If , Without this tempo , After all the time spent by the front duty personnel , The further back, the higher the risk . It's like the final R & D is just 4 God , The test is just 2 God , That belt BUG Go online ！？ Therefore, the overall control is the responsibility for the project .

---

3. Resource input

• matter ： R & D resources investment
• personnel ： Architects 、 R & D personnel 、 Testers
• describe ： From the perspective of R & D , R & D needs to start from engineering development 、 Test Coordination （ Change bug）、 Participate in the whole process of project launch, etc , It's a long cycle of work . But at some stage, the time cost will be different , It can be invested according to a certain proportion of resources （1 yes 100%、0.8 yes 80%）. that , When a new project comes down , We need to follow the latest principles and the personnel input of the project , Arrange the input of resources . If there are many projects , The arrangement of resources is unreasonable . It may lead to late project submission and testing or some functions submitted and tested by a R & D , Finally, it can't be changed BUG. And that leads to , The risk of project delay .

---

4. Research and development 、 test 、 Go live

• matter ： Research and development 、 test 、 Go live
• personnel ： R & D personnel 、 Testers 、 Architects / Technical team leader
• describe ： This stage covers a lot , It's mainly about connecting people from the perspective of R & D . R & D takes over the needs of products and starts to design , After the design is completed, the design review is initiated by the R & D leader , There are more people involved in this stage （ Research and development 、 Architects 、 test 、 Products, etc. ）. The rational design of functions is also an important part of ensuring the use of resources very effectively , Another reasonable structure of requirements will pave the way for subsequent requirements iterations . It's like changing the women's room to the men's room , If there's no pipe running out of urine , It's very troublesome. . The final R & D needs to submit the corresponding products , Especially the test report 、 Interface document 、 Single test information . If R & D cannot have complete unit test coverage , So after you give it to the test , Daily repair bug There will be a lot of things . When R & D and testing are done , The next step is to launch . On the eve of the launch, R & D will launch the launch report , At the same time, the cooperation of all parties and products 、 Use to prepare the corresponding online configuration data and permissions . Finally, the product is delivered online for operation .

---

5. Project resumption

• matter ： Project resumption
• personnel ： For R & D and testers
• describe ： The second round may be due to an accident 、 Technical summary 、 Share growth , Several directions 、 summary , Avoid the same kind of thing . The contents of the second offer generally include the use of technology , for example ：DB、 application development 、 Gateway, etc. , It also includes the construction of business domain logic .

replay DB

• The number of database connections is increased according to the business scenario
• It is forbidden to use complex nesting and function class for business query
• Strengthen the anti duplication logic field to avoid the problem of not anti duplication
• Index field initialization detection and slow query optimization

Re offer business

• The design of all marketing scenarios should conform to the standard process , Consistency of cache usage
• In the aspect of capital flow settlement, we should strengthen the verification of anti duplication design , The test environment simulates various scenarios
• Depending on the volume of external support for business development , Report the flow rate by pressure measurement
• All core function processes strengthen the R & D side code review quality , And continue to optimize according to the amount of development
• R & D side code quality improvement, regular review and optimization , Improve quality through exercise
• In R & D and testing 、 Repair 、 Pay attention to the development branch of the online process , Avoid confusion and merger problems
• All business process configuration monitoring and chart and print log , It is convenient to track the online abnormality in time
• The whole link voltage measurement of the core scenario can effectively guarantee the quality , It can also reduce the traffic risk very well

Double disk function

• Functional logic encapsulation optimization , cache 、 Threads 、 verification
• Log integrity verification , Enter the reference 、 The ginseng 、 abnormal
• Setting the timeout duration of calling external interface and the retrying convention
• The urgent problem of abnormal display , Test environment recurrence traceability

Second round deployment

• Deploy services according to pressure testing standards
• Core business: two computer rooms and three computer rooms
• Non core business isolation RPC Interface configuration
• Adjust as needed JVM、 The number of connections 、 Log and other parameters

Double disk interface

• The integrity of functional verification
• Retestability of abnormal processes
• Data index monitoring range
• After the new product is online, it will be tested regularly

Sum up , Maybe it's just a summary review of a project , Easy for new people to accept and understand the key content of the project . If the team can timely and effective summary technology and landing data , Can be very effective to do a good job in technology inheritance .

---

6. summary

• The development process of large and medium-sized projects in the Internet , There are many processes involved , It also needs reasonable control . Otherwise, there may be some risks in the process , As a result, the project can not go online as scheduled . Of course, not all projects need to be dealt with this way , Simple iterations and small requirements, for example , It can simplify the process , Fast iteration . Build a pit 、 pigsty 、 Three bedrooms are different , Can't generalize
• Do a good job in technical analysis 、 replay 、 summary 、 inductive , The precipitated technical data are very valuable , The experience of project development can be passed on to new people , It can also let everyone do their own technological growth . And through the review and summary , It can also refine more new ideas and improve the technical atmosphere .

Copyright notice ： In this paper, the source , Rare earth Nuggets community ： Little brother Fu