Summary of E-commerce background System Reconstruction

Here we will record some experience in restructuring the e-commerce background system.

-- James Fu

1. Unified management of public resources such as membership levels, order statuses, and Order Types
2. Do not use Ajax too much. For example, do not initiate another Ajax request to load data after the page is loaded.
3. Do not write a large number of JS files on the pageCodeAnd do not include services in JavaScript. Many things should be handled at the backend as much as possible, so that later modifications will be clear.
4. Do not overencapsulate. In the just-completed reconstruction project, there are both web form applications and MVC applications. Web forms over-encapsulate server-side controls, resulting in poor performance and bringing new learning tasks to developers. The MVC application encapsulates a large number of JS tools, resulting in huge JS Code and difficulty in maintenance.
5. The project defines multiple DTO, including viewobject, datacontract, entity, and objects which are converted back and forth using transformer. This is really painful. We recommend that you integrate datacontract and entity to ensure uniformity. Define viewobject on the front end and use it. For example:
6. Public class soviewobject {public somsg model {Get; set;} Public String sotypedesc {get {return socommon. getsotypedesc (model. sotype );}}}

6. <unfinished>