2. Suggestions on writing a series of articles at the app backend

2. Suggestions on writing a series of articles at the app backend

I am very grateful to the netizens in the "app backend" QQ Group for their feedback.

The following suggestions will be incorporated into writing:

 

1. Also, I am very interested in version upgrades. We have already messed up the engineering code to be compatible with the old version.

2. I want to know something about the preliminary plan, so that the system can be expanded continuously in the future.

3. We are now using the back-end cloud, and more cloud services are used. We hope that some cloud-related

4. Technology Selection, technical comparison, and technical implementation at various stages and levels

 

Answers to some questions:

 

Q: Is it recommended that you write the entire process of a typical APP?

A: I have considered case-based solutions, but I gave up later. Without front-end cooperation, the written code is not tested in the production environment, which is unreliable.

 

Q: It is best to combine the specific use environment, that is, under what circumstances is this solution better?

A: The idea of writing each technical point is to write an application scenario and describe the principles.

 

Q: Does the/api/v1/... app correspond to the corresponding api version?

A: This solution is described in "api processing for Version Upgrade. The simple description is that v2 inherits the v1 api. It only overwrites the part that needs to be modified and shares the model. It specifies the returned content in the api test document for comparison.

 

Q: Is there any protocol that is more efficient than http for app background communication? For example, websocket?

Answer: (1) http is the most convenient. If it is websocekt or socket, it involves designing a private protocol, including the encapsulation and splitting of the Protocol, with a heavy workload.

Unless it is a mobile game app that has extremely high requirements on real-time performance and data transmission, you can simply use http.

(2) Another consideration is the development time of the project. As a common global protocol, http supports a wide range of third-party libraries, which greatly improves the development efficiency.

 

 

【Author】 Zeng jiansheng
[QQ] 190678908
[Public Account] appbackend
[Backend QQ group of app] 254659220
Blog http://blog.csdn.net/newjueqi