Micro-service-based back-end splitting strategy

Abstract

The invention discloses a micro-service-based back-end splitting strategy, and relates to the technical field of micro-service splitting. The micro-service is split into an upper side and a lower sidewhich comprise a portal layer and a core layer; the portal layer provides an interface for the outside and is used for receiving an input parameter called by the interface, returning processing dataand performing simple service logic processing; the core layer is a base layer, is responsible for main service logic processing, provides support of a portal layer interface for calling of a lower layer interface, and is responsible for interaction with a database. According to the method, the micro-service is split into the portal layer and the core layer, so that the micro-service becomes lighter and thinner in structure, and overall maintenance, upgrading and reconstruction of the system are better facilitated; the core layer serves as a base layer, the interface can provide rich and comprehensive data, the portal layer can be changed and packaged into different interfaces according to needs, and dynamic change of the portal layer is achieved.

Description

technical field [0001] The invention belongs to the technical field of microservice splitting, and in particular relates to a backend splitting strategy based on microservices. Background technique [0002] With the rapid development of the Internet, microservice splitting has long been a popular implementation solution in the industry. Microservice splitting can meet the rapid iteration of requirements, realize agile and rapid development, meet the rapidly changing market demand, and quickly occupy the market. Microservice splitting mainly realizes the decoupling between various services, reduces the coupling between each other, and can realize the agile development of each team without affecting each other. [0003] After the microservice is split, it becomes a separate service system. The iteration of all requirements based on the microservice is carried out on this microservice. This microservice is not further split and layered. All updates or reconstructions are based...

AI Technical Summary

Problems solved by technology

[0004] After the existing microservice becomes an independent system, with the continuous iteration of the code, an independent microservice system may eventually become a large and bloated complex system, which will bring a huge workload to the maintenance of the later system. If you want to To upgrade the system, it is also possible to cause a small change to affect the entire microservice system, resulting in system unavailability

If the microservice system is refactored later, it will also bring a huge workload

Images