The problem of the rationality of the Partition of Project Modules

A management system that can connect many third parties originally wants to build a sub-project next to a third party, these sub-projects refer to public code projects, but it is found that some public management pages need to use the business of various third-party sub-projects, but public works cannot refer to these sub-projects. Now there are two kinds of considerations. one is to build another public management project and quote all the third-party sub-projects, and the other is to merge these sub-projects into a business project and divide them in the form of each sub-module. then build a public management module in this business project, so that you can directly call the code of all sub-modules.

I don"t know which of these two ways is better? The main purpose is to know the advantages and disadvantages of dividing different modules under a project and building a sub-project independently. The convenience of maintenance and development should be considered, because each third party will open a branch for development independently, and after the development is completed, it will become a stable version, and the production version will be maintained on the stable version.

Sep.06,2021

soa architecture, each third party invokes the service to build a project, provides http interface to the outside, and invokes the third party service internally; the bus establishes the interface and calls each module


for the requirements of the management system, it is suggested that the system should be separated, the management system should be isolated from the business system, and the interface standard should be established based on the requirement of the management system. The business system should be developed according to the interface and registered in the management system

.

about the pros and cons of dividing a project into different modules and building an independent sub-project
the choice of module or sub-project mainly depends on your business scenario and the amount of data loaded. When the access volume is small and the amount of data is small, module development is definitely conducive to team development. If you use a module, the deployment complexity of the architecture design server is very low
, but how high is the business coincidence of your sub-project? If the degree of coincidence is high, it is recommended to use saas mode to make a system. If you do not consider this, the iterative upgrading of business functions with high degree of coincidence will be very painful for many of your sub-projects, so the higher the degree of coincidence, the more recommended saas mode

.
Menu