Two partitioning schemes for code tree subdirectories
Option 1: If you just quickly build a runnable first version of the demo code as a new project, you can directly create a single Maven project in the development environment and write the code directly. Disadvantage: All business modules are mixed together, and the possibility of mutual coupling is high. Advantages: The first version of the software can be tested online as soon as possible, at least the class can sort out most of the business details.
Another solution is to split the top-level Maven project into multiple submodules from the beginning. Since the details of some business processes have not been fully sorted out in the early stage of the project, the sub-modules split out in advance may not be completely reasonable. Later, the secondary split changes will be relatively large.