According to the micro-service design idea, combining some excellent projects of spring cloud, such as service discovery, governance, configuration management, routing load, security control and other excellent solutions, using MAVEN technology to modular, service, atomization encapsulation and build, also for the post-grayscale publishing, Continuous integration prepare for the job ahead of time
In addition, before setting up the environment, you need to master the use of Maven and related issues (not repeated here)
The Spring Cloud cloud architecture is built using MAVEN, and using MAVEN is more than just a jar package, it's important to capture the core role of Maven, which is to divide the entire project into a modular way, decoupling business from business, The modular business is then serviced or modularized to allow for any project or platform-based business porting
Finally, consider the fine-grained division of services, such as: A login module, we can all the services related to the login service (basic information verification; user name, email, mobile phone authentication login, mobile phone Verification Code acquisition, verify the user is bound, etc.), and finally for multi-service service orchestration, And that's what's going on. Micro-Service Architecture
These are some of my experiences in doing projects or architectures to share with everyone
Here's a look at the code structure of the entire architecture:
System Services
Common components
Business Services
Here is simply a description of the Honghu Cloud architecture code structure.
Some distributed solutions, friends who are willing to know can find our team to discuss technical support 1791743380
Spring Cloud-honghu Cloud Distributed Cloud system--Construction of code structure