Micro-service construction method and micro-service system for cloud manufacturing platform

Abstract

The embodiment of the application discloses a micro-service construction method and a micro-service system for a cloud manufacturing platform, relates to the technical field of intelligent manufacturing, and can quickly and conveniently develop new function modules according to requirements, and realizes quick and convenient dynamic function integration and expansion. The application comprises: receiving data uploaded by a client device through a view layer, wherein the client device comprises a user terminal device and an enterprise terminal device, the uploaded data comprises order information sent by the user terminal device and resource information sent by the enterprise terminal device, and the resource information records production equipment resources of the enterprise; inputting the data uploaded by the view layer into a micro-service layer through a gateway layer; querying resource information corresponding to the order information by a micro-service module registered in the micro-service layer; decomposing an order according to the order information to obtain sub-tasks, and allocating production equipment resources of the enterprise according to the sub-tasks, and then recording allocation information; and sending a production command to the production equipment of the enterprise according to the allocation information.

Description

Technical Field

[0001] This invention relates to the field of intelligent manufacturing technology, and in particular to a microservice construction method and microservice system for cloud manufacturing platforms. Background Technology

[0002] In recent years, increasing attention has been paid to digital manufacturing and network-based collaborative manufacturing. Information technology is continuously integrating with the industrial sector, leading to the emergence of numerous industrial internet platforms that enable remote transmission and visualization of industrial data. Currently, cloud platforms also allow for personalized product customization, unified allocation of enterprise orders, and unified resource allocation across discrete enterprises, achieving network-based collaborative manufacturing and significantly improving production efficiency and resource utilization. As information technology continues to penetrate the industrial sector, cloud manufacturing platforms are becoming increasingly feature-rich, and their system architectures are becoming highly complex, making system maintenance and functional expansion increasingly difficult. Microservice architecture is a new technology for deploying applications and services in the cloud. Its purpose is to decompose a complex and large system into discrete, less coupled services based on their functions, thereby decoupling a complex and large monolithic system and improving its maintainability and scalability.

[0003] Existing intelligent manufacturing information systems based on microservice architecture primarily select corresponding logical function modules from pre-developed business application modules according to user needs. These modules are then connected to basic and public service modules via a service access module, thus generating a microservice-based intelligent manufacturing information system. The shortcomings of this approach are that it requires the pre-development of numerous business modules, resulting in a large workload. Furthermore, it cannot achieve rapid and convenient dynamic function integration and expansion when encountering needs that some business modules cannot meet, ultimately limiting the application scope of this approach. Summary of the Invention

[0004] The embodiments of the present invention provide a microservice construction method and microservice system for a cloud manufacturing platform, which can quickly and easily develop new functional modules according to needs, and realize rapid and convenient dynamic function integration and expansion.

[0005] To achieve the above objectives, the embodiments of the present invention adopt the following technical solutions:

[0006] In a first aspect, the method provided by embodiments of the present invention includes:

[0007] S1. Receive data uploaded by the client device through the view layer, wherein the client device includes a user terminal device and an enterprise terminal device running, and the uploaded data includes: order information sent by the user terminal device and resource information sent by the enterprise terminal device, wherein the resource information records the enterprise's production equipment resources;

[0008] S2. Input the data uploaded by the view layer into the microservice layer through the gateway layer;

[0009] S3. The microservice module registered in the microservice layer queries the resource information corresponding to the order information;

[0010] S4. The order is broken down into sub-tasks based on the order information, and the enterprise's production equipment resources are allocated according to the sub-tasks. The allocation information is then recorded.

[0011] S5. Send production orders to the enterprise's production equipment according to the allocation information.

[0012] Secondly, the microservice system provided by the embodiments of the present invention includes: a view layer, a gateway layer, a microservice layer, and a data storage layer; the microservice layer includes at least two service modules, and each service module includes at least four microservice modules, the four microservice modules being: a user microservice module, an order microservice module, an enterprise resource microservice module, and a resource allocation microservice module;

[0013] The view layer is used to receive data uploaded by client devices through the view layer. The client devices include user devices and enterprise devices running. The uploaded data includes order information sent by the user devices and resource information sent by the enterprise devices. The resource information records the enterprise's production equipment resources.

[0014] The gateway layer is used to input the data uploaded by the view layer into the microservice layer through the gateway layer;

[0015] The microservice layer is used to query the resource information corresponding to the order information through the registered microservice modules; and to break down the order into sub-tasks based on the order information, then allocate the enterprise's production equipment resources according to the sub-tasks and record the allocation information; finally, to send production commands to the enterprise's production equipment according to the allocation information.

[0016] The data storage layer establishes sub-databases corresponding to the microservice modules.

[0017] The microservice construction method and microservice system for cloud manufacturing platforms provided in this invention can resolve system problems at the specific module level without affecting the normal use of other modules. It also simplifies the expansion of new functions and solves the problem of difficult system maintenance. Furthermore, it improves system scalability, allowing functional modules to be developed independently and then uniformly registered with the service center, reducing development difficulty and shortening the development cycle. Moreover, by using the well-established microservice architecture system technology solution Spring Cloud Alibaba, the compatibility of various technical components is better, reducing system development configuration and improving development efficiency. In summary, compared to traditional system architectures, the microservice architecture of this embodiment has the advantage of high scalability. This alleviates the difficulty of functional expansion in traditional cloud platform architectures, improves system integration and scalability, and enables the rapid and convenient development of new functional modules according to needs, achieving fast and convenient dynamic functional integration and expansion. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1a , 1b This is a schematic diagram of the architecture of a microservice system provided in an embodiment of the present invention.

[0020] Figure 2 This is a schematic diagram illustrating the working principle of the Nacos service registration and discovery center provided in this embodiment of the invention.

[0021] Figure 3 The diagram illustrates the responsibilities and collaborative work of various microservices provided in this embodiment of the invention.

[0022] Figure 4 This is a schematic diagram of the Hystrix service fuse provided in an embodiment of the present invention.

[0023] Figure 5 This is a schematic diagram of the method flow provided in an embodiment of the present invention. Detailed Implementation

[0024] To enable those skilled in the art to better understand the technical solutions of the present invention, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. Embodiments of the present invention will be described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and should not be construed as limiting the present invention. Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the term “comprising” as used in the specification of the present invention means the presence of the stated features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. It should be understood that when we say an element is “connected” or “coupled” to another element, it can be directly connected or coupled to the other element, or there may be intermediate elements. Furthermore, “connected” or “coupled” as used herein can include wireless connections or couplings. The term "and / or" as used herein includes any and all combinations of one or more of the associated listed items. It will be understood by those skilled in the art that, unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. It should also be understood that terms such as those defined in general dictionaries should be understood to have the meaning consistent with their meaning in the context of the prior art, and should not be interpreted in an idealized or overly formal sense unless defined as herein.

[0025] This invention provides a microservice construction method and microservice system for a cloud manufacturing platform. The method is used in a microservice system, as shown in Figure 1. In this embodiment, the platform structure of the microservices is designed in layers, and divided into different microservices according to specific logical functions. The overall platform architecture is divided into four layers. After a user initiates access to the platform, the user sequentially passes through the view layer, gateway layer, microservice layer, and data storage layer. The microservice system includes: a view layer, gateway layer, microservice layer, and data storage layer. The microservice layer includes at least two service modules, and each service module contains at least four microservice modules: a user microservice module, an order microservice module, an enterprise resource microservice module, and a resource allocation microservice module. In this embodiment, one microservice module can correspond to one specific service, for example... Figure 1bAs shown, a service related to orders can be called an "order microservice." Its microservice modules include various functional units, such as API interfaces, NacosClient, product upload units, order reservation units, and order progress display units. Another example is the user microservice, which includes API interfaces, NacosClient, user login units, user registration units, and information modification units. Here, Nacos client refers to the Nacos client; Nacos stands for Dynamic Naming and Configuration Service. Nacos generally consists of a server (Nacos server) and a client (Nacos client). Each microservice must contain a Nacos client, which is then registered with the Nacos server, allowing the Nacos server to be aware of each microservice.

[0026] The view layer is used to visualize data for both users and enterprises, displaying the platform's functional interfaces and human-computer interaction entry points, and receiving order information from user devices and resource information from enterprise devices. As shown in Figure 1, the view layer uses the Vue framework to visualize the data. The Vue framework employs the MVVM design pattern, ensuring that the view updates immediately when data variables change. Vue interacts with the backend using Ajax, enabling asynchronous communication between the frontend and backend. This allows for page updates without loading the entire page, reducing browser load. The view layer primarily provides the interactive interface for users to create orders and upload enterprise resources.

[0027] The data storage layer includes sub-databases corresponding to microservice modules. For example, the sub-databases in the data storage layer include: a user microservice database, an order microservice database, an enterprise resource microservice database, and a resource allocation microservice database, which are used to record the data generated by the user microservice module, order microservice module, enterprise resource microservice module, and resource allocation microservice module in the microservice layer during operation. The data layer is a data persistence layer that stores system data. Since each microservice is directly independent and has low coupling, the data correlation between services is low. Therefore, each microservice has its own database for data storage, and each microservice's database is independent of the others.

[0028] Specifically, such as Figure 5 As shown, the method includes:

[0029] S1. Receive data uploaded by the client device through the view layer.

[0030] The client device includes a user terminal device and an enterprise terminal device running, and the uploaded data includes: order information sent by the user terminal device and resource information sent by the enterprise terminal device, wherein the resource information records the enterprise's production equipment resources.

[0031] S2. Input the data uploaded by the view layer into the microservice layer through the gateway layer.

[0032] S3. The microservice module registered in the microservice layer queries the resource information corresponding to the order information.

[0033] Specifically, in S3, the following steps are included: the order microservice module queries the enterprise resource microservice module for the resource information corresponding to the order information; then, the order microservice module submits the order information and the resource information fed back by the enterprise resource microservice module to the resource allocation microservice module.

[0034] S4. Based on the order information, the order is broken down into sub-tasks, and the enterprise's production equipment resources are allocated according to the sub-tasks. Then, the allocation information is recorded.

[0035] Specifically, S4 includes: the resource allocation microservice module breaking down the order based on the order information, which can be done using a task decomposition method based on the BOM (Bill of Materials). Then, it allocates the enterprise's production equipment resources to the sub-tasks obtained from the order breakdown based on the resource information, and records the allocation information.

[0036] S5. Send production orders to the enterprise's production equipment according to the allocation information.

[0037] Specifically, S5 includes: sending the allocation information to the enterprise resource microservice module, and the enterprise resource microservice module sending production commands to the enterprise's production equipment.

[0038] Specifically, such as Figure 3 The diagram illustrates the main relationships between the microservices, which collaborate directly to complete manufacturing tasks. Users submit manufacturing orders from the cloud platform. The order information first requests the order service. Upon receiving the order, the order service stores the order information, analyzes the required resource service types, and then sends a request to the enterprise resource microservice to query the specified type of enterprise resource information, returning a set of relevant enterprise resource services. After receiving the request, the order service submits the order and resource information to the resource allocation service. The resource allocation service breaks down the order and allocates enterprise resources according to a resource allocation algorithm, finally assigning the matching information to the enterprise resource service. The enterprise resource service then begins processing and production, updating the enterprise resource information.

[0039] Furthermore, when a new microservice module needs to be added to the microservice layer, the new microservice module is registered in the Nacos service registry; the configuration information of the registered microservice module is stored in the Nacos service registry; and a sub-database corresponding to the registered microservice module is established in the data storage layer.

[0040] In this embodiment, the open-source Nacos technology tool is used. Nacos supports service discovery based on DNS and RPC. After a service provider registers its service using the native SDK, OpenAPI, or a separate Agent TODO, service consumers can use DNS TODO or HTTP & API to find and discover the service. Specifically, as shown in Figure 1, the system uses Nacos to implement service registration and discovery in this embodiment. By registering in the Nacos service registry, each microservice can discover its corresponding microservice through Feign and make the corresponding calls. The configuration center is responsible for the unified management of the configuration information of all microservices. Nacos integrates the functionality of the configuration center, which facilitates the unified management and maintenance of the configuration file information of various microservices in the system. Nacos replaces the traditional Eureka + Spring Cloud Config approach, offering richer and more stable functionality and greater ease of use.

[0041] The microservice layer can be implemented on a cloud platform and can contain various functional modules, such as task order management, enterprise resource information management, and equipment monitoring management modules. Modules can be developed independently based on their functions, and then registered with a service registry and discovery center. This enables collaborative calls between services. The decomposition of sub-application modules improves development convenience, high scalability, and maintainability. As business functions increase, only the corresponding sub-application modules need to be developed and registered in the registry center to expand the business. For example… Figure 2 As shown, Nacos serves as the registration and discovery center for various application sub-services. We need to register each independently developed sub-application module with the Nacos registry according to a unified standard. This allows other sub-application services to discover themselves and remotely invoke their business functions. All microservice sub-applications are connected through Nacos, enabling mutual discovery and invocation between microservices and reducing the coupling of traditional system architectures.

[0042] Furthermore, this embodiment also includes: a circuit breaker is set in the microservice layer, the circuit breaker using the Spring Cloud Hystrix component; when a microservice module fails or becomes unresponsive, the circuit breaker triggers a circuit breaking mechanism, and / or performs degradation processing on the failed or unresponsive microservice module. For example, as shown in Figure 1 and... Figure 4 As shown, the circuit breaker uses the Spring Cloud Hystrix component. When a microservice fails, service requests will fail. Without corresponding feedback and response, users will continue to wait, resulting in a degraded user experience. Hystrix can implement a circuit breaker mechanism to degrade the service when a microservice fails and becomes unresponsive.

[0043] The microservice layer designed in this embodiment consists of multiple services, a service registration and discovery center, a unified configuration center, and a circuit breaker. Each service contains all the functions related to that service and can run independently. Through unified service registration and discovery, it is easy to implement gateway routing to various application sub-services and function calls between services. Furthermore, considering the large number of services, the configuration files of each service are managed uniformly. To address the scenario of a large number of requests accessing the backend service, which may cause request blocking, a service degradation method is configured using the circuit breaker. When a service request exceeds a certain time, a degradation method is used to respond to the request.

[0044] In the gateway layer, a gateway architecture for microservices is established using Spring Cloud Gateway components. Each microservice module consists of: a module identifier, an API interface, a Nacos Client, and functional units. The microservice module communicates with the gateway layer through the API interface.

[0045] Specifically, the main function of the gateway layer is to reduce the complexity of client request addresses and to uniformly receive and process client requests. Each microservice has its own network address, and client requests often require calls to multiple microservices to complete. Therefore, by adding a gateway layer, clients can directly access the gateway, which then proxies them to the specific microservice addresses. This reduces client complexity and the complexity of project refactoring. As shown in Figure 1, the API gateway layer uses the Spring Cloud Gateway component to implement the gateway layer of the microservice architecture. It achieves unified management of all user-initiated requests. All requests pass through the API gateway layer and are then forwarded to the corresponding services.

[0046] This embodiment also provides a microservice system for a cloud manufacturing platform, as shown in Figure 1. The microservice system includes a view layer, a gateway layer, a microservice layer, and a data storage layer. The microservice layer includes at least two service modules, and each service module contains at least four microservice modules. The four microservice modules are: a user microservice module, an order microservice module, an enterprise resource microservice module, and a resource allocation microservice module.

[0047] The view layer is used to receive data uploaded by client devices through the view layer. The client devices include user devices and enterprise devices running. The uploaded data includes order information sent by the user devices and resource information sent by the enterprise devices. The resource information records the enterprise's production equipment resources.

[0048] The gateway layer is used to input the data uploaded by the view layer into the microservice layer through the gateway layer;

[0049] The microservice layer is used to query the resource information corresponding to the order information through the registered microservice modules; and to break down the order into sub-tasks based on the order information, then allocate the enterprise's production equipment resources according to the sub-tasks and record the allocation information; finally, to send production commands to the enterprise's production equipment according to the allocation information.

[0050] The data storage layer establishes sub-databases corresponding to the microservice modules.

[0051] A circuit breaker is provided in the microservice layer. The circuit breaker is used to trigger a circuit breaker mechanism when a microservice module fails or becomes unresponsive, and / or to degrade the failed or unresponsive microservice module. A Nacos service registry is deployed in the microservice layer. The Nacos service registry is used to register newly added microservice modules. Each microservice module consists of: a module identifier, an API interface, a Nacos Client, and functional units. The microservice module communicates with the gateway layer through the API interface.

[0052] In this embodiment, the complex monolithic architecture system is divided into functionally independent microservice units. The advantages of this design are: reduced system coupling, improved maintainability, allowing solutions to system problems to be implemented at the specific module level without affecting other modules, and simplifies the expansion of new functionalities, thus addressing system maintenance difficulties. Furthermore, it enhances system scalability, enabling individual development of functional modules followed by unified registration with the service center, reducing development complexity and shortening the development cycle. Moreover, the use of Spring Cloud Alibaba, a microservice architecture technology with a robust ecosystem, ensures better compatibility among various technical components, reducing system development configuration and improving development efficiency.

[0053] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on its differences from other embodiments. In particular, the device embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments. The above descriptions are merely specific embodiments of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for building microservices for a cloud manufacturing platform, characterized in that, The method is used in a microservice system, which includes a view layer, a gateway layer, a microservice layer, and a data storage layer. The method includes: S1. Receive data uploaded by the client device through the view layer, wherein the client device includes a user terminal device and an enterprise terminal device running, and the uploaded data includes: order information sent by the user terminal device and resource information sent by the enterprise terminal device, wherein the resource information records the enterprise's production equipment resources; S2. Input the data uploaded by the view layer into the microservice layer through the gateway layer; S3. The microservice module registered in the microservice layer queries the resource information corresponding to the order information; S4. The order is broken down into sub-tasks based on the order information, and the enterprise's production equipment resources are allocated according to the sub-tasks. The allocation information is then recorded. S5. Send a production command to the enterprise's production equipment according to the allocation information; The microservice layer includes at least two service modules, and each service module contains at least four microservice modules. The four microservice modules are: user microservice module, order microservice module, enterprise resource microservice module, and resource allocation microservice module. The data storage layer includes sub-databases corresponding to the microservice modules. In S3, the following steps are included: the order microservice module queries the enterprise resource microservice module for the resource information corresponding to the order information; then, the order microservice module submits the order information and the resource information fed back by the enterprise resource microservice module to the resource allocation microservice module. In S4, the following is included: the resource allocation microservice module decomposes the order based on the order information and the BOM task decomposition method, and allocates the enterprise's production equipment resources to the sub-tasks obtained from the order decomposition based on the resource information, and then records the allocation information; In S5, the process includes: sending the allocation information to the enterprise resource microservice module, which then sends production commands to the enterprise's production equipment; wherein, the user submits a manufacturing order from the cloud platform, the order information first requests an order service, the order service receives the order, stores the order information, analyzes the required resource service types, then sends a request to the enterprise resource microservice to query the specified type of enterprise resource information, and returns a service set of relevant enterprise resources; after receiving the request, the order service submits the order information and resource information to the resource allocation service, the resource allocation service breaks down the order and allocates enterprise resources according to the resource allocation algorithm, and finally allocates the matching information to the enterprise resource service, which then begins processing and production and updates the enterprise resource information; It also includes: when a new microservice module needs to be added to the microservice layer, the newly added microservice module is registered in the Nacos service registry; wherein, the configuration information of the registered microservice module is stored in the Nacos service registry; and, a sub-database corresponding to the registered microservice module is established in the data storage layer; Nacos serves as the registration and discovery center for each application subservice, registering individually developed sub-application modules to the Nacos registry according to a unified standard, so that sub-application services can discover themselves and remotely call their own business functions.

2. The method according to claim 1, characterized in that, Also includes: A circuit breaker is set in the microservice layer, and the circuit breaker uses the Spring Cloud Hystrix component; When a microservice module fails or becomes unresponsive, the circuit breaker triggers a circuit breaker mechanism and / or degrades the microservice module that fails or becomes unresponsive.

3. The method according to claim 1, characterized in that, The sub-databases in the data storage layer include: a user microservice database, an order microservice database, an enterprise resource microservice database, and a resource allocation microservice database, which are used to record the data generated by the user microservice module, order microservice module, enterprise resource microservice module, and resource allocation microservice module in the microservice layer during operation.

4. The method according to claim 1, characterized in that, In the gateway layer, a microservice gateway architecture is built using Spring Cloud Gateway components; Each microservice module comprises: a module identifier, an API interface, a Nacos Client, and functional units, wherein the microservice module communicates with the gateway layer through the API interface.

5. A microservice system for a cloud manufacturing platform, characterized in that, The microservice system includes: a view layer, a gateway layer, a microservice layer, and a data storage layer; The view layer is used to receive data uploaded by client devices through the view layer. The client devices include user devices and enterprise devices running. The uploaded data includes order information sent by the user devices and resource information sent by the enterprise devices. The resource information records the enterprise's production equipment resources. The gateway layer is used to input the data uploaded by the view layer into the microservice layer through the gateway layer; The microservice layer is used to query the resource information corresponding to the order information through the registered microservice modules; break down the order into subtasks based on the order information; allocate production equipment resources of the enterprise according to the subtasks and record the allocation information; and finally send production commands to the enterprise's production equipment according to the allocation information. The data storage layer establishes sub-databases corresponding to the microservice modules; The microservice layer includes at least two service modules, and each service module contains at least four microservice modules. The four microservice modules are: user microservice module, order microservice module, enterprise resource microservice module, and resource allocation microservice module. The data storage layer includes sub-databases corresponding to the microservice modules. Specifically, the order microservice module queries the enterprise resource microservice module for the resource information corresponding to the order information. Then, the order microservice module submits the order information and the resource information fed back by the enterprise resource microservice module to the resource allocation microservice module. The resource allocation microservice module breaks down the order based on the order information and the BOM task decomposition method, and allocates the enterprise's production equipment resources to the sub-tasks obtained from the order breakdown according to the resource information, and then records the allocation information. The allocation information is sent to the enterprise resource microservice module, which then sends production commands to the enterprise's production equipment. Specifically, when a user submits a manufacturing order from the cloud platform, the order information first requests an order service. Upon receiving the order, the order service stores the order information, analyzes the required resource service types, and then sends a request to the enterprise resource microservice to query the specified type of enterprise resource information, returning a set of relevant enterprise resource services. After receiving the request, the order service submits the order information and resource information to the resource allocation service. The resource allocation service breaks down the order and allocates enterprise resources according to a resource allocation algorithm, finally assigning the matching information to the enterprise resource service. The enterprise resource service then begins processing and production and updates the enterprise resource information. When a new microservice module needs to be added to the microservice layer, the new microservice module is registered in the Nacos service registry. The configuration information of the registered microservice module is stored in the Nacos service registry. Furthermore, a sub-database corresponding to the registered microservice module is established in the data storage layer. Nacos serves as the registration and discovery center for each application subservice, registering individually developed sub-application modules to the Nacos registry according to a unified standard, thereby enabling sub-application services to discover themselves and remotely invoke their own business functions.

6. The microservice system according to claim 5, characterized in that, A circuit breaker is provided in the microservice layer. The circuit breaker is used to trigger the circuit breaking mechanism when a microservice module fails or becomes unresponsive, and / or to degrade the microservice module that fails or becomes unresponsive. A Nacos service registry is deployed in the microservice layer. The Nacos service registry is used to register newly added microservice modules. Each microservice module consists of: a module identifier, an API interface, a NacosClient, and a functional unit. The microservice module communicates with the gateway layer through the API interface.

Images