This paper briefly introduces some problems and experiences in the development of enterprise-owned systems in e-commerce industry. Development, taking into account these problems, development will be more smooth, the development of software will be more vitality. Take
advantage of legacy system functions to minimize workloadThe company's system is the system is running, do two times the development of the time is often in the original some of the basic functions of upgrading, which requires not to destroy the original functional logic, but also to take advantage of the first function, because to achieve certain functions, there may be some features already. For example, the e-commerce platform needs to do a recharge function, the system originally has a payment function, gift certificate function, then we can consider the two functions to be integrated to transform it?
platform-based design, development, modularity, toolingdevelopment of the system, sometimes need to think out, the development of the perspective, not limited to the project itself, not confined to the project group itself, to stand in the overall perspective. For example, there is a scenario where the project team that is responsible for the return business needs to develop a feature that will need to push a message to the app client after a successful refund, which may require a study of third-party solutions such as Aurora push, au push, and then call the third-party API to develop the appropriate functionality. Coincidentally, the payment group, may also want to do similar functions, after the user pays the success, need to push a message to the app, remind the user to pay the success, this time, the payment group to study the third-party push solution, do repetitive work. In fact, in the beginning, the return group should be analyzed, the message push should be a more general function, can develop a common tool module, tools, for the whole company to use. Of course, the work of developing a generic module, where some companies may have a dedicated architecture group development, is just an example.
handling code accumulation, refactoring codebelieve that the change in demand is the source of the code's stink and the confusion and corruption of the code. In particular, continuous iteration of the updated code, sometimes in order to catch up, or to avoid large changes in the system, it is easy to break the original design of the code, or the arbitrary copy of the code to quickly implement some of the functions, logic becomes more and more complex, repetitive code becomes more and more, the code eventually can not be changed, Then I remembered to tidy up the code, this time is too late, it may be pushed to re-come over the cost will be lower. Therefore, in the development of the time, to do a conscientious, a small optimization, a small quantitative change, are for the future to do qualitative change and preparation.
All-end compatible, compatible versionsThe company is the channel e-commerce solution, the development of a function, need to take into account the PC official website, Android, iOS, Mobile T station, store system, ERP system, how these different platforms to achieve, how to trade-offs; mobile side of the same platform, development, but also to consider to the low version compatibility. There may be different teams behind the different ends, it's a big challenge to have a wide-ranging project, how to communicate with each group more efficiently, and how to grasp the progress of the project. The
control of input, the balance between the system perfection and the progress, the relationship before the project riskthe development of a function, sometimes not the more perfect the better, nor do the more perfect the better, but to balance the cost of development and the output of the project, to consider the value is not worth it. Of course, as a pure programmer, do not consider the capitalist thing, do 100% perfect, easy to use is the best.
feasibility, demand, development, testing, on-line, on-line monitoring, after-the-line effect, follow-up operations and upgrade the needs of the whole trackas a developer, in the life cycle of participating projects, the e-commerce industry differs from other industries in that it may be on-line monitoring, effect tracking and operation. In the e-commerce industry, if there is a problem with the system, it is likely to affect sales, affect customer experience, or there are some loopholes, causing the company to lose. Therefore, to ensure that the system runs steadily, the problem is critical, after the system on-line, must be well monitored to ensure that the problem can be found and processed the first time. After the stability of the system, it is necessary to do the effect evaluation, look at the development of the function, whether the project has brought return, the effect, see if there is any need to improve, upgrade, to obtain greater returns. read to the end, the reader may feel that the article may be the title of the party, these experiences may be related to e-commerce enterprise development relationship is not very inevitable,
perhaps in any software development company will encounter these problems , this may be the software development figured out the place, But this is really I am engaged in the e-commerce industry software development work only sense, if there is unreasonable place, also please correct, if there are more good experience and methods, welcome to share.
E-commerce system two development---experience
