Micro-service Business Analysis of docker in Advanced Chapter (9)
Original articles, welcome to reprint. Reprint please indicate: reproduced from IT Story Association, thank you!
Original link address: "Advanced article" docker micro-service business analysis (9)
Starting from this section, when it comes to the development of micro services, there are several problems that need to be solved. First of all, what do we need to develop? After we understand what kind of business scenario, analyze the business scenario, there are several micro-services, what functions each micro-service needs to complete, the relationship between micro-services, the dependency relationship between them, and how they communicate with each other, we can move on to the development stage.
Business scenario
Users can register and log in
The current login system is generally single sign-on, support cross-domain, when to use other systems do not need to log in, it is best not to use session, preferably stateless, avoid using session.
Logged-in users can CURD the course
The above is not a large and comprehensive system, just the function of micro-service, old man, our purpose is very clear to engage in micro-service, not to learn from web development, we start to understand micro-service from 0 on the above functions, and complete the development of micro-service one by one, so that everyone can have a real experience in development.
Basic microservice process user access api gateway api gateway access 2 user edgeservice (java) and course edgeservice (java) these two interfaces provide http protocol (rest) user service course edgeservice access course service user service external interface is Thrift cross-language protocol course service external interface using Dubbo Only java user service (java) backend has a database course service (java) backend also has a database information service (python) external interface is Thrift (when users register, they may send text messages, or email confirmation may require information services) redis to store users' information. The edgeservice and course services provided to the user service use the course to complete the discovery of the service through zookeeper. The user query course needs to invoke the course service, that is, the invocation between the micro services.
PS: next, Lao tie and I will complete the process of building and building microservices.
