Business processing method of micro-service architecture and related equipment

Abstract

The invention discloses a service processing method of a micro-service architecture and related equipment. According to the embodiment of the invention, when a target business service node is started, service configuration information is read from a target memory grid node deployed by the target business service node, and service registration is carried out in the target memory grid node to obtain target registration information; synchronously storing the target registration information to a memory grid node in an associated business service node of the target business service node; the received node registration information of the associated business service node sent by the associated business service node is stored in the target memory grid node; and based on the registration information in the target memory grid node, processing a received target service request sent by the target terminal device, and obtaining and returning a service processing result to the target terminal device. According to the embodiment of the invention, the method can reduce the business interruption risk caused by a single-point fault, and facilitates the guarantee of the stability of a business service system. Therefore, the scheme can improve the business processing efficiency.

Description

Technical Field

[0001] This application relates to the field of computer science, specifically to a business processing method and related equipment based on a microservice architecture. Background Technology

[0002] To improve service efficiency, various industries are actively promoting business digitalization, encouraging enterprises, organizations, and institutions to migrate more of their business to online information systems in order to expand service scope and meet the needs of more users.

[0003] Currently, information systems generally adopt a microservice architecture. A microservice architecture can break down a large and complex system into multiple independent and small services. Each service can be developed, deployed, and maintained independently. Therefore, a microservice architecture has high availability, high performance, and flexible horizontal elastic scaling capabilities.

[0004] However, current microservice architectures also have some drawbacks. For example, core components are managed externally in a centralized manner. Specifically, current microservice architectures rely on external service management nodes such as external registry centers and configuration centers. This makes it difficult to guarantee system stability in resource-constrained environments, increasing the complexity of operation and maintenance. Furthermore, centralized management makes troubleshooting more difficult, impacting the provision of stable business services. Summary of the Invention

[0005] This application provides a business processing method and related equipment for a microservice architecture. The related equipment includes a business processing device for the microservice architecture, electronic devices, computer-readable storage media, and computer program products. It can implement a microservice architecture without relying on external service management nodes. Data is stored by deploying memory grid nodes on each business service node. The memory grid node data adopts a distributed multi-replica storage principle to reduce the risk of business interruption caused by single point of failure when processing business requests, ensure that each business service is easy to maintain, help ensure the stability of the business service system, and improve business processing efficiency.

[0006] This application provides a business processing method based on a microservice architecture, applicable to target business service nodes in a microservice cluster. The target business service nodes deploy target memory grid nodes, which store service configuration information of the target business service nodes. The method includes:

[0007] When the target service node starts, it reads the service configuration information from the target memory grid node;

[0008] Based on the service configuration information, service registration is performed in the target memory grid node so that the target memory grid node stores the target registration information of the target business service node;

[0009] The target registration information is synchronously stored in the memory grid node of the associated business service node of the target business service node. The associated business service node is another business service node in the microservice cluster to which the target business service node belongs.

[0010] Receive node registration information of associated service nodes sent by associated service nodes, and store the node registration information in the target memory grid node;

[0011] When a target service request is received from the target terminal device, the target service request is processed based on the registration information in the target memory grid node, and the service processing result is obtained and returned to the target terminal device.

[0012] This application embodiment also provides a business processing device for a microservice architecture, applicable to a target business service node in a microservice cluster, wherein the target business service node deploys a target memory grid node, and the target memory grid node stores the service configuration information of the target business service node; the device includes:

[0013] The information reading unit is used to read service configuration information from the target memory grid node when the target service node starts.

[0014] The service registration unit is used to register services in the target memory grid node based on service configuration information, so that the target memory grid node stores the target registration information of the target business service node;

[0015] The information synchronization unit is used to synchronize and store the target registration information to the memory grid node in the associated business service node of the target business service node. The associated business service node is another business service node in the microservice cluster to which the target business service node belongs.

[0016] The information storage unit is used to receive the node registration information of the associated business service node sent by the associated business service node, and store the node registration information in the target memory grid node;

[0017] The request processing unit is used to process the target service request based on the registration information in the target memory grid node when it receives a target service request sent by the target terminal device, and to obtain and return the service processing result to the target terminal device.

[0018] In some embodiments, the request processing unit includes a dependency query subunit, an auxiliary sending subunit, an auxiliary receiving subunit, and a result processing subunit:

[0019] The dependency query subunit is used to look up the node registration information of the auxiliary service node by using the registration information in the target memory grid node when it receives a target service request sent by the target terminal device through the gateway device and detects that the target service request depends on the auxiliary service node.

[0020] The auxiliary sending subunit is used to send the target service request to the auxiliary service node based on the node registration information of the auxiliary service node. The auxiliary service node is any other service node in the microservice cluster other than the target service node.

[0021] The auxiliary receiving subunit is used to trigger the auxiliary service node to process the target service request, obtain the intermediate service processing result, and return the intermediate service processing result to the target service node.

[0022] The result processing subunit is used to process the intermediate business processing results and return the business processing results to the target terminal device.

[0023] In some embodiments, the apparatus further includes a dependency detection subunit and a request processing subunit:

[0024] The dependency detection subunit is used to perform dependency service detection on the target service request when a target service request is received from the target terminal device.

[0025] The request processing subunit is used to process the target business request when no dependency on other business service nodes is detected, and to obtain and return the business processing result to the target terminal device.

[0026] In some embodiments, the apparatus further includes a fault handling unit, a data synchronization unit, and a request response unit:

[0027] The fault handling unit is used to trigger the storage of intermediate business processing data of the target business request into the target memory grid node when a fault event is detected during the processing of the target business request, and to select a reference business service node that can handle the target business request from the microservice cluster through the registration information in the target memory grid node.

[0028] The data synchronization unit is used to synchronize intermediate business processing data to the memory grid nodes of the reference business service nodes through the target memory grid nodes;

[0029] The request-response unit is used to trigger the reference service node to obtain intermediate service processing data from its memory grid node, so that the reference service node can process the target service request based on the intermediate service processing data, obtain and return the service processing result to the target terminal device.

[0030] In some embodiments, before synchronizing and storing the target registration information to the memory grid node in the associated business service node of the business service node, the apparatus further includes an information broadcasting unit, a cluster judgment unit, and a cluster determination unit:

[0031] The information broadcasting unit is used to generate broadcast information based on the service cluster identifier information of the microservice cluster to which the target business service node belongs;

[0032] The cluster judgment unit is used to send broadcast information within a preset area to trigger the business service nodes within the preset area to determine whether the business service nodes within the preset area and the target business service node belong to the same microservice cluster based on the broadcast information.

[0033] The cluster determination unit is used to determine the associated business service nodes based on the judgment result.

[0034] In some embodiments, the gateway device is deployed with memory grid nodes, and the microservice cluster includes at least two distributed business service nodes; the memory gateway nodes in the gateway device synchronously store the registration information of each business service node;

[0035] The request processing unit includes a request receiving subunit and a result returning subunit:

[0036] The request receiving subunit is used to receive the target service request sent by the target terminal device through the gateway device. The target service request instructs the gateway device to forward it to the service service node in the microservice cluster that can handle the request. The gateway device determines the service service node that can handle the request through the registration information in its memory grid node.

[0037] The result return sub-unit is used to process the target business request based on the registration information in the target memory grid node, and to obtain and return the business processing result to the target terminal device.

[0038] This application also provides an electronic device, including a processor and a memory, wherein the memory stores multiple instructions; the processor loads instructions from the memory to execute steps in any of the microservice architecture business processing methods provided in this application.

[0039] This application also provides a computer-readable storage medium storing a plurality of instructions adapted for loading by a processor to execute steps in any of the microservice architecture business processing methods provided in this application.

[0040] This application also provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the steps in any of the microservice architecture business processing methods provided in this application.

[0041] This application embodiment can be applied to target business service nodes in a microservice cluster. The target business service node deploys a target memory grid node, which stores the service configuration information of the business service node. The method includes: when the target business service node starts, reading the service configuration information from the target memory grid node; registering the service in the target memory grid node based on the service configuration information, so that the target memory grid node stores the target registration information of the target business service node; synchronously storing the target registration information in the memory grid nodes of the associated business service nodes of the target business service node, where the associated business service nodes are other business service nodes in the microservice cluster to which the target business service node belongs; receiving node registration information from the associated business service nodes and storing the node registration information in the target memory grid node; and when a target business request is received from a target terminal device, processing the target business request based on the registration information in the target memory grid node, obtaining and returning the business processing result to the target terminal device.

[0042] In this application, when a target service node starts up, it can read and register service configuration information from its deployed target memory grid node, thereby obtaining target registration information. The target service node can then synchronously store the target registration information to the memory grid nodes of associated service nodes using the target memory grid node, and receive node registration information sent by associated service nodes using their deployed content grid nodes. This allows each service node in the microservice cluster to understand the service services provided by each other. When a target service node receives a target service request, it can effectively process the request based on the registration information stored in the target memory grid node and return the processing result to the target terminal device. In this way, each service node in the microservice cluster can collaborate to achieve efficient interaction of service services.

[0043] Furthermore, while implementing a microservice architecture, data storage can be handled without relying on external service management nodes. This is achieved by deploying memory grid nodes on each business service node. The memory grid nodes employ a distributed, multi-replica storage principle, reducing the risk of business interruption due to single points of failure when processing business requests. This ensures that each business service is easy to maintain and contributes to the stability of the business service system. Consequently, business processing efficiency is improved. Attached Figure Description

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

[0045] Figure 1a This is a schematic diagram of a business processing method for a microservice architecture provided in this application embodiment;

[0046] Figure 1b This is a flowchart illustrating the business processing method of the microservice architecture provided in the embodiments of this application;

[0047] Figure 2a This is a flowchart illustrating the business processing method of a microservice architecture based on a memory data grid model provided in this application embodiment;

[0048] Figure 2b This is a data interaction diagram of the business processing method of the microservice architecture provided in the embodiments of this application;

[0049] Figure 3 This is a schematic diagram of the business processing device of the microservice architecture provided in the embodiments of this application;

[0050] Figure 4 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0051] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0052] This application provides a business processing method and related equipment for a microservice architecture.

[0053] Specifically, the business processing device of this microservice architecture can be integrated into an electronic device, such as a terminal or server. The terminal can be a mobile phone, tablet, smart Bluetooth device, laptop, or personal computer (PC); the server can be a single server or a server cluster composed of multiple servers.

[0054] In some embodiments, the business processing device of the microservice architecture can also be integrated into multiple electronic devices. For example, the business processing device of the microservice architecture can be integrated into multiple servers, and the business processing method of the microservice architecture of this application can be implemented by multiple servers.

[0055] In some embodiments, the server may also be implemented as a terminal.

[0056] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0057] It is understood that in the specific implementation of this application, data such as service configuration information are involved. When the embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0058] For example, refer to Figure 1a This electronic device can be applied to target business service nodes in a microservice cluster. The target business service node deploys a target memory grid node, which stores the service configuration information of the target business service node. The method includes: when the target business service node starts, reading the service configuration information from the target memory grid node; registering the service in the target memory grid node based on the service configuration information, so that the target memory grid node stores the target registration information of the target business service node; synchronously storing the target registration information in the memory grid nodes of the associated business service nodes of the target business service node, where the associated business service nodes are other business service nodes in the microservice cluster to which the target business service node belongs; receiving node registration information sent by the associated business service nodes and storing the node registration information in the target memory grid node; and when a target business request is received from a target terminal device, processing the target business request based on the registration information in the target memory grid node, obtaining and returning the business processing result to the target terminal device.

[0059] In this way, the various business service nodes in the microservice cluster can collaborate to achieve efficient interaction of business services. Furthermore, while implementing a microservice architecture, it is possible to store data without relying on an external service management node. Data is stored using memory grid nodes deployed on each business service node. The memory grid nodes employ a distributed, multi-replica storage principle to reduce the risk of business interruption due to single points of failure when processing business requests, ensuring that each business service is easy to maintain and contributing to the stability of the business service system. This, in turn, improves business processing efficiency.

[0060] The following sections provide detailed descriptions of each example. It should be noted that the sequence numbers of the following embodiments are not intended to limit the preferred order of the embodiments.

[0061] In this embodiment, a business processing method based on a microservice architecture is provided, applicable to target business service nodes in a microservice cluster. The target business service nodes deploy target memory grid nodes, which store the service configuration information of the target business service nodes. Figure 1b As shown, the specific flow of this microservice-based business processing method can be as follows:

[0062] 101. When the target service node starts, read the service configuration information from the target memory grid node.

[0063] A microservice cluster refers to a cluster consisting of multiple business service nodes that provide business service support for an application. Each business service can correspond to at least one business service node to ensure the stable operation of the business service.

[0064] Applications can be software running on various terminal devices, including but not limited to mobile phones, computers, smart voice interaction devices, smart home appliances, in-vehicle terminals, and aircraft. These applications provide business services through a microservice architecture to meet user needs and provide functionality.

[0065] Business service nodes are nodes in a microservice architecture that provide specific business services. For example, a business service node can be a server, a virtual machine, etc.

[0066] The server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The terminal can be a smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, etc., but is not limited to these. The terminal and server can be connected directly or indirectly through wired or wireless communication methods, which is not limited herein.

[0067] The target business service node is the business service node that is currently starting up in the microservice cluster. The target memory grid node is a memory grid node that enables automatic data exchange between the target business service node and other business service nodes in the microservice cluster.

[0068] For example, the target service node supports a memory grid service. Through this service, the target service node can allocate a portion of its memory resources to target memory grid nodes. These target memory grid nodes, based on the memory grid service, can exchange data with the content grid nodes of other service nodes in the microservice cluster, enabling automatic data exchange among the various service nodes in the microservice cluster. Service configuration information provides the target service node with configuration parameters for running the corresponding service. For example, service configuration information may include the target service node's node service data, address information, node identifier, etc.

[0069] 102. Based on the service configuration information, register the service in the target memory grid node so that the target memory grid node stores the target registration information of the target business service node.

[0070] Among them, the target registration information is the information obtained after the service configuration information of the target business service node is registered in its target memory grid node. The purpose of service registration is to enable other business service nodes in the microservice cluster to which the target business service node belongs to discover and read the target registration information in the target memory grid node.

[0071] For example, the service configuration information of the target business service node can be registered in the registry center of the target memory grid node. Through the service discovery mechanism supported by the registry center, other business service nodes in the microservice cluster to which the target business service node belongs can automatically read the target registration information in the registry center of the target business service node.

[0072] 103. Synchronously store the target registration information in the memory grid node of the associated business service node of the target business service node. The associated business service node is another business service node in the microservice cluster to which the target business service node belongs.

[0073] Among them, the associated business service nodes are business service nodes other than the target business service node in the microservice cluster to which the target business service node belongs. These associated business service nodes may include business service nodes that have the same business services as the target business service node, as well as business service nodes that have different business services.

[0074] For example, associated business service nodes can automatically read and store target registration information from the target business service node's target memory grid node through a service discovery mechanism, based on their own memory grid nodes, so that associated business service nodes can learn about the business services provided by the target business service node through the target registration information.

[0075] In some embodiments, in order to locate business service nodes belonging to the same microservice cluster after the target business service node starts, before synchronously storing the target registration information in the memory grid node of the associated business service node, the method further includes:

[0076] Based on the service cluster identifier information of the microservice cluster to which the target business service node belongs, a broadcast message is generated.

[0077] By sending broadcast information within a preset area, the business service nodes within the preset area are triggered to determine whether the business service nodes within the preset area and the target business service node belong to the same microservice cluster based on the broadcast information.

[0078] Based on the judgment results, the associated business service nodes are determined.

[0079] The service cluster identification information refers to the identification information of the microservice cluster to which the target business service node belongs. For example, the service cluster identification information may include the identifier, name, service port, and Internet address of the microservice cluster to which the target business service node belongs, or the identifier, name, and version number of the application served by the microservice cluster. There are no restrictions on the service cluster identification information.

[0080] Broadcast messages are propagable messages generated based on service cluster identification information.

[0081] The preset area range is the range within which broadcast information can be broadcast.

[0082] Sending broadcast information within a preset area includes, but is not limited to:

[0083] 1) Through multicast network broadcast, the target service node sends a broadcast message to a specific multicast address. This address is a predefined range of Internet addresses used to identify a multicast group. Only service nodes that have joined this multicast group will receive the sent message.

[0084] 2) Send a broadcast message to all service nodes in the same network. The target service node sends the broadcast information to the network's broadcast address, and all service nodes connected to the network can receive the broadcast information.

[0085] The judgment result can reflect whether the business service nodes within the preset area belong to the same microservice cluster as the target business service node.

[0086] For example, after receiving a broadcast message, a business service node within a preset area can determine whether it belongs to the same microservice cluster as the target business service node by using the service cluster identifier information of its own microservice cluster and the service cluster identifier information in the broadcast message. If the determination result indicates that it belongs to the same microservice cluster as the target business service node, it will establish a data transmission connection with the target business service node through the Transmission Control Protocol (TCP), thereby enabling the target business service node to obtain the associated business service node.

[0087] In some embodiments, it also includes:

[0088] Based on the establishment of a data transmission channel with the associated business service nodes, it is determined that the associated business service nodes are in operation.

[0089] 104. Receive the node registration information of the associated business service node sent by the associated business service node, and store the node registration information in the target memory grid node.

[0090] Among them, the node registration information is the service configuration information of the associated business service node obtained by registering the service in its memory grid node.

[0091] For example, when the target business service node synchronously stores the target registration information in the memory grid node of the associated business service node, the target business service node can automatically read and store the node registration information from the memory grid node of the associated business service node through the service discovery mechanism provided by the target content grid node.

[0092] 105. When a target service request is received from the target terminal device, the target service request is processed based on the registration information in the target memory grid node, and the service processing result is obtained and returned to the target terminal device.

[0093] The target terminal device is a terminal running an application served by a microservice cluster. For example, target terminal devices include, but are not limited to, mobile phones, computers, smart voice interaction devices, smart home appliances, in-vehicle terminals, and aircraft.

[0094] A target service request is a service request sent by the target terminal device that matches the service provided by the target service service node.

[0095] The registration information includes target registration information and node registration information for each associated business service node.

[0096] The business processing result is the result obtained by the target business service node in processing the target business request.

[0097] In some embodiments, to ensure effective collaboration among multiple required service nodes when processing a service request to complete all operations required for the request, upon receiving a target service request from a target terminal device, the target service request is processed based on the registration information in the target memory grid node to obtain and return a service processing result to the target terminal device, including:

[0098] When a target service request is received from a target terminal device through a gateway device, and it is detected that the target service request depends on an auxiliary service node, the node registration information of the auxiliary service node is searched through the registration information in the target memory grid node.

[0099] Based on the node registration information of the auxiliary business service node, the target business request is sent to the auxiliary business service node, which is another business service node in the microservice cluster other than the target business service node;

[0100] The auxiliary business service node is triggered to process the target business request, obtain the intermediate business processing result, and return the intermediate business processing result to the target business service node.

[0101] The intermediate business processing results are processed to obtain and return the business processing results to the target terminal device.

[0102] Gateway devices are used to connect target terminal devices and the microservice cluster, enabling interaction between them. For example, gateway devices can be routers, switches, firewalls, network proxy software, etc.

[0103] Auxiliary business service nodes refer to business service nodes that the target business service node needs to rely on or work in collaboration with when processing target business requests. These auxiliary business service nodes may provide other functions, data or resources related to the target business service node to support the target business service node in completing specific business logic or processing tasks.

[0104] For example, in a distributed system, a target business request may require the collaborative work of multiple different business service nodes to complete. The business service node receiving the target business request handles the core business logic processing and is called the target business service node, while other business service nodes may provide additional services or data support and are called auxiliary business service nodes. These auxiliary business service nodes may include caching services, authentication services, storage services, etc., and they work together with the target business service node to complete the processing of the target business request.

[0105] The node registration information of auxiliary service nodes is used to indicate the auxiliary service nodes required for the processing of target service requests, so that the target service request can be sent to the auxiliary service nodes based on the node registration information.

[0106] The intermediate business processing result is the result obtained by the auxiliary business service node in processing the target business request. This intermediate business processing structure needs to be returned to the target business service node so that the target business service node can continue to process the intermediate business processing result according to the target business processing request, and finally obtain the business processing result.

[0107] For example, suppose there is a smart home system where a user sends a request to control the home lights to the gateway device via a target terminal device (such as a smartphone, smart control panel, or smart speaker), which is then sent to the target service node in the system. Upon receiving the request, the system detects that the request depends on other service nodes, such as needing to query the status of the lights in the home through another service node.

[0108] The system will find the node registration information of the auxiliary business service node responsible for the status of the lighting fixtures based on the node registration information in the target memory grid node.

[0109] Then, the system sends the target service request for controlling the lights to this auxiliary service node, requesting it to query the status of the lights in the home.

[0110] After receiving the target business request, the auxiliary business service node will perform the corresponding operation, query the status of each light fixture in the home, and generate intermediate business processing results, such as which lights are on and which are off.

[0111] Then, the auxiliary business service node returns the intermediate business processing results to the target business service node.

[0112] After receiving the intermediate business processing result, the target business service node may perform further processing based on the target business request, such as deciding whether to turn on or off certain lights based on the lighting control operation specified in the target business request.

[0113] Finally, the system returns the final business processing result to the target terminal device, informing it of the execution status of the target business request.

[0114] In some embodiments, in order to determine whether collaboration with other service nodes is needed when a target service node processes a service request, the method further includes:

[0115] When a target service request is received from the target terminal device, dependency service detection is performed on the target service request.

[0116] When no service node is detected that the target service request depends on other service nodes, the target service request is processed, and the service processing result is obtained and returned to the target terminal device.

[0117] For example, suppose there's an online shopping system. A user opens the corresponding application on their target device and clicks the "buy" button, sending a purchase request to the target service node in the system. Upon receiving the request, the target service node performs a dependency check to see if the request depends on other service nodes. For instance, it might need to check the user's payment information or product inventory.

[0118] If the system detects that the purchase request does not depend on other service nodes, it will process the request directly. The system will deduct the corresponding amount from the user's account, update the product inventory information, and generate an order. Finally, the system will return the processing result to the user's mobile phone, informing them that the purchase operation was successful. If the purchase request depends on other service nodes, the system will first call those other service nodes to complete the necessary operations before processing the purchase request.

[0119] In some embodiments, to select another service node from the microservice cluster to continue processing the target service request in the event of a failure during the processing of the target service request by the target service node, the method further includes:

[0120] When a fault event is detected during the processing of a target business request, the intermediate business processing data of the target business request is stored in the target memory grid node, and a reference business service node that can handle the target business request is selected from the microservice cluster based on the registration information in the target memory grid node.

[0121] The intermediate business processing data is synchronized to the memory grid nodes of the reference business service nodes through the target memory grid nodes;

[0122] The reference service node is triggered to retrieve intermediate service processing data from its memory grid node, so that the reference service node can process the target service request based on the intermediate service processing data, and obtain and return the service processing result to the target terminal device.

[0123] In this context, a failure event refers to an abnormal situation that prevents the target business service node from performing its tasks normally. For example, a failure event could be a software error, network failure, database failure, or resource exhaustion. Intermediate business processing data refers to temporary data generated by the target business service node during the processing of target business requests before the failure event occurs.

[0124] Reference service nodes refer to other service nodes in a microservice cluster that have the same service functions as the target service node. In the event of a failure of the target service node, they can replace the target service node to continue processing the target service request based on intermediate business processing data, thereby reducing the risk of business interruption caused by single point of failure, ensuring that each service is easy to maintain, and helping to ensure the stability of the service system.

[0125] For example, the reference service node can be an idle service node selected from the microservice cluster that can handle the target service request. Alternatively, it can be a reference service node that can handle the target service request can be selected by calculating the hash value based on the source Internet address in the target service request using a load balancing algorithm, or it can be a reference service node that can handle the target service request can be selected from the microservice cluster using a round-robin method.

[0126] In some embodiments, in order to select a business service node that can quickly process the target business request after a failure event occurs at the target business service node, a reference business service node capable of processing the target business request is selected from the microservice cluster based on the registration information in the target memory grid node, including:

[0127] Based on the registration information in the target memory grid node, candidate business service nodes with the same business service functions as the target business service node are selected from the microservice cluster.

[0128] Based on the operational status of the candidate service nodes, a reference service node is determined from among the candidate service nodes.

[0129] Among them, candidate business service nodes are other business service nodes that have the same business service functions as the target business service node.

[0130] The reference service node is the candidate service node that is currently operating optimally. For example, the reference service node is a candidate service node that is currently operating well and has sufficient system resources.

[0131] In some embodiments, in order for the microservice cluster to allocate business service nodes to process business requests, the gateway device is deployed with memory grid nodes, and the microservice cluster includes at least two distributed business service nodes; the memory gateway nodes in the gateway device synchronously store the registration information of each business service node;

[0132] When a target service request is received from a target terminal device, the request is processed based on the registration information in the target memory grid node, and the service processing result is obtained and returned to the target terminal device, including:

[0133] The gateway device receives a target service request sent by the target terminal device through the gateway device. The target service request instructs the gateway device to forward it to the service node in the microservice cluster that can handle the request. The gateway device determines the service node that can handle the request through the registration information in its memory grid node.

[0134] Based on the target service request, the target service request is processed using the registration information in the target memory grid node, and the service processing result is obtained and returned to the target terminal device.

[0135] For example, when a gateway device receives a service request from a target terminal device, it first analyzes the service required by the request. Next, the gateway device checks the registration information of each service node in its memory grid, which contains the service functions provided by each node. By comparing the required services with the registration information in the memory grid, the gateway device can determine which service nodes are capable of handling the request.

[0136] If the registration information of the target service node matches the target service request, the gateway device will retrieve the address of the matching target service node from its registration information and send the target service request to the target service node to complete the request processing. In this way, the gateway device can effectively send requests to service nodes capable of processing them based on the registration information in the memory grid nodes, thereby realizing request routing and distribution.

[0137] As can be seen from the above, the embodiments of this application can be applied to target business service nodes in a microservice cluster. The target business service node deploys a target memory grid node, and the target memory grid node stores the service configuration information of the business service node. The method includes: when the target business service node starts, reading the service configuration information from the target memory grid node; registering the service in the target memory grid node based on the service configuration information, so that the target memory grid node stores the target registration information of the target business service node; synchronously storing the target registration information in the memory grid nodes of the associated business service nodes of the target business service node, wherein the associated business service nodes are other business service nodes in the microservice cluster to which the target business service node belongs; receiving the node registration information of the associated business service nodes sent by the associated business service nodes, and storing the node registration information in the target memory grid node; when a target business request is received from a target terminal device, processing the target business request based on the registration information in the target memory grid node, obtaining and returning the business processing result to the target terminal device.

[0138] Therefore, this solution allows each business service node in the microservice cluster to understand the business services they provide. When a target business service node receives a target business request, it can effectively process the request based on the registration information stored in the target memory grid node and return the processing result to the target terminal device. In this way, the business service nodes in the microservice cluster can collaborate to achieve efficient interaction of business services. Furthermore, while implementing a microservice architecture, it can avoid relying on an external service management node by deploying memory grid nodes on each business service node for data storage. The memory grid node data adopts a distributed, multi-replica storage principle to reduce the risk of business interruption due to single points of failure when processing business requests, ensuring that each business service is easy to maintain and contributing to the stability of the business service system. This improves business processing efficiency.

[0139] The method described in the above embodiments will be further described in detail below.

[0140] In this embodiment, a new fully decentralized microservice architecture model based on the In-Memory Data Grid (IMDG) model will be implemented as an example to illustrate the method of this application embodiment.

[0141] like Figure 2a As shown, a business processing method is applicable to target business service nodes in a microservice cluster. The target business service nodes deploy target memory grid nodes, and the target memory grid nodes store the service configuration information of the target business service nodes. The specific process of this method is as follows:

[0142] 201. When the target business service node in the microservice cluster starts, it automatically discovers the associated business service nodes within the preset area through multicast network broadcast. The target business service node can be any business service node in the microservice cluster.

[0143] 202. Through the transmission control protocol, establish a data transmission connection with the associated service node so that the associated service node can determine the normal operation of the target service node based on the data transmission connection.

[0144] 203. Read service configuration information from the target memory grid node, complete the loading of service configuration data, and automatically register the service configuration data to the target memory grid node after loading, thus obtaining the target registration information.

[0145] 204. The target registration information registered in the target memory grid node will be automatically distributed, copied and synchronized to the memory grid nodes of the associated business service nodes of the target business service node, and will receive the node registration information of the associated business service nodes sent by the associated business service nodes, and store the node registration information in the target memory grid node.

[0146] 205. When receiving a target service request sent by the target terminal device through the gateway device, the gateway device performs dependency service detection on the target service request. The target service request instructs the gateway device to forward it to the service service node in the microservice cluster that can handle the request. The gateway device determines the service service node that can handle the request through the registration information in its memory grid node.

[0147] 206. When no target service request is detected to depend on other service nodes, process the target service request, obtain and return the service processing result to the target terminal device.

[0148] 207. When a target service request is detected to depend on an auxiliary service node, the node registration information of the auxiliary service node is found through the registration information in the target memory grid node; based on the node registration information of the auxiliary service node, the target service request is sent to the auxiliary service node, which is another service node in the microservice cluster besides the target service node; the auxiliary service node is triggered to process the target service request, obtain intermediate service processing results, and return the intermediate service processing results to the service node; the intermediate service processing results are processed to obtain and return the service processing results to the target terminal device.

[0149] For example, such as Figure 2bAs shown, an IMDG memory grid node is embedded within the business service node. This built-in memory grid node enables shared data storage for all microservices within the microservice cluster. When a business service node starts, it automatically registers its service configuration data, such as node service data and address information, with the memory grid node. The same self-registration logic is executed when a new business service node is added to the microservice cluster. Furthermore, when a business service node malfunctions or goes offline, the memory grid node's self-discovery mechanism automatically maintains the node information within the memory grid node, ensuring high consistency of information across the memory grid nodes.

[0150] Based on this logical mechanism, by embedding memory grid nodes within microservice nodes, all business logic of the registry and configuration center can be implemented, simplifying the original complex model that relied on external service management nodes. The overall architecture is simpler, easier to maintain and expand, and also saves a significant amount of server resources.

[0151] This application mainly implements a new fully decentralized microservice architecture model through the IMDG model. The implementation method is to embed IMDG memory grid nodes within business service nodes. By embedding IMDG memory grid nodes, the characteristics of memory grid nodes can be used to enable all business service nodes to access shared data in the memory grid nodes nearby. The shared data includes data from other business service nodes.

[0152] When a service node writes data to a memory grid node, the data is automatically distributed to other service nodes and shared by all service nodes in the current microservice cluster. Users do not need to know which service node the data is stored on. Because the data is stored in the memory of each service node in the microservice cluster, the data access efficiency is as high as the efficiency of accessing local data when a user accesses any data.

[0153] Therefore, it can be seen that the data in the distributed memory grid nodes is distributed and stored across all business service nodes, and all business service nodes can share the data, achieving data access with performance consistent with local access. The data accessible to each business service node follows the consistency principle. When a new business service node is added to this microservice cluster, the data in the memory grid nodes is automatically distributed and shared across the new business service node's memory grid nodes. The data in the memory grid nodes adopts a distributed, multi-replica, high-availability storage principle, ensuring that data in the memory grid nodes will not be lost due to business service nodes going offline. The business service nodes in the microservice cluster are highly scalable, allowing for flexible addition or removal, with data automatically redistributed without affecting the data integrity within the memory grid nodes. The memory grid nodes within all business service nodes are autonomous and decentralized, allowing each business service node to join or leave at any time, without a defined order of operation.

[0154] As can be seen from the above, this application mainly reduces the complexity of the microservice architecture itself, realizes the complete decentralization of the microservice architecture, and at the same time reduces the external service management nodes that the microservice architecture depends on, thereby reducing the external service management nodes that are prone to failure. This improves the overall stability and availability of the microservice architecture and evolves into a more streamlined, easy-to-use, and simple-to-configure microservice architecture.

[0155] The benefits of the microservice architecture implemented in this application include: achieving complete decentralization and service self-governance; streamlining the microservice architecture's reliance on service clusters, effectively reducing service dependencies and lowering the learning curve for microservice usage; reducing deployment difficulty and hardware resource requirements, saving hardware resources and operational costs; reducing the complexity of the microservice architecture itself and the accident rate caused by node failures, thus improving microservice availability; improving the performance of data sharing communication among various business service nodes within the microservice architecture through memory grid nodes; and greater scalability, such as enabling global business session management and global caching services without relying on external modules through memory grid nodes.

[0156] To better implement the above methods, this application also provides a microservice architecture business processing device, which can be integrated into an electronic device, such as a terminal or server. The terminal can be a mobile phone, tablet computer, smart Bluetooth device, laptop computer, or personal computer; the server can be a single server or a server cluster composed of multiple servers.

[0157] For example, in this embodiment, the method of this application embodiment will be described in detail by taking the business processing device of microservice architecture specifically integrated into an electronic device as an example.

[0158] For example, such as Figure 3 As shown, the business processing device of this microservice architecture is suitable for target business service nodes in a microservice cluster. The target business service nodes are deployed with target memory grid nodes, which store the service configuration information of the target business service nodes. The device may include an information reading unit 301, a service registration unit 302, an information synchronization unit 303, an information storage unit 304, and a request processing unit 305, as follows:

[0159] (I) Information reading unit 301.

[0160] The information reading unit 301 is used to read service configuration information from the target memory grid node when the target service node starts.

[0161] (II) Service Registration Unit 302.

[0162] Service registration unit 302 is used to register services in the target memory grid node based on service configuration information, so that the target memory grid node stores the target registration information of the target business service node.

[0163] (III) Information Synchronization Unit 303.

[0164] The information synchronization unit 303 is used to synchronize and store the target registration information to the memory grid node in the associated business service node of the target business service node. The associated business service node is another business service node in the microservice cluster to which the target business service node belongs.

[0165] In some embodiments, before synchronizing and storing the target registration information to the memory grid node in the associated business service node of the business service node, the apparatus further includes an information broadcasting unit, a cluster judgment unit, and a cluster determination unit:

[0166] The information broadcasting unit is used to generate broadcast information based on the service cluster identifier information of the microservice cluster to which the target business service node belongs;

[0167] The cluster judgment unit is used to send broadcast information within a preset area to trigger the business service nodes within the preset area to determine whether the business service nodes within the preset area and the target business service node belong to the same microservice cluster based on the broadcast information.

[0168] The cluster determination unit is used to determine the associated business service nodes based on the judgment result.

[0169] (iv) Information storage unit 304.

[0170] The information storage unit 304 is used to receive the node registration information of the associated business service node sent by the associated business service node, and store the node registration information in the target memory grid node.

[0171] (v) Request processing unit 305.

[0172] The request processing unit 305 is used to process the target service request based on the registration information in the target memory grid node when it receives a target service request sent by the target terminal device, and to obtain and return the service processing result to the target terminal device.

[0173] In some embodiments, the request processing unit includes a dependency query subunit, an auxiliary sending subunit, an auxiliary receiving subunit, and a result processing subunit:

[0174] The dependency query subunit is used to look up the node registration information of the auxiliary service node by using the registration information in the target memory grid node when it receives a target service request sent by the target terminal device through the gateway device and detects that the target service request depends on the auxiliary service node.

[0175] The auxiliary sending subunit is used to send the target service request to the auxiliary service node based on the node registration information of the auxiliary service node. The auxiliary service node is any other service node in the microservice cluster other than the target service node.

[0176] The auxiliary receiving subunit is used to trigger the auxiliary service node to process the target service request, obtain the intermediate service processing result, and return the intermediate service processing result to the target service node.

[0177] The result processing subunit is used to process the intermediate business processing results and return the business processing results to the target terminal device.

[0178] In some embodiments, the apparatus further includes a dependency detection subunit and a request processing subunit:

[0179] The dependency detection subunit is used to perform dependency service detection on the target service request when a target service request is received from the target terminal device.

[0180] The request processing subunit is used to process the target business request when no dependency on other business service nodes is detected, and to obtain and return the business processing result to the target terminal device.

[0181] In some embodiments, the apparatus further includes a fault handling unit, a data synchronization unit, and a request response unit:

[0182] The fault handling unit is used to trigger the storage of intermediate business processing data of the target business request into the target memory grid node when a fault event is detected during the processing of the target business request, and to select a reference business service node that can handle the target business request from the microservice cluster through the registration information in the target memory grid node.

[0183] The data synchronization unit is used to synchronize intermediate business processing data to the memory grid nodes of the reference business service nodes through the target memory grid nodes;

[0184] The request-response unit is used to trigger the reference service node to obtain intermediate service processing data from its memory grid node, so that the reference service node can process the target service request based on the intermediate service processing data, obtain and return the service processing result to the target terminal device.

[0185] In some embodiments, the gateway device is deployed with memory grid nodes, and the microservice cluster includes at least two distributed business service nodes; the memory gateway nodes in the gateway device synchronously store the registration information of each business service node;

[0186] The request processing unit includes a request receiving subunit and a result returning subunit:

[0187] The request receiving subunit is used to receive the target service request sent by the target terminal device through the gateway device. The target service request instructs the gateway device to forward it to the service service node in the microservice cluster that can handle the request. The gateway device determines the service service node that can handle the request through the registration information in its memory grid node.

[0188] The result return sub-unit is used to process the target business request based on the registration information in the target memory grid node, and to obtain and return the business processing result to the target terminal device.

[0189] In practice, each of the above units can be implemented as an independent entity or can be arbitrarily combined to be implemented as the same or several entities. For the specific implementation of each of the above units, please refer to the previous method embodiments, which will not be repeated here.

[0190] As can be seen from the above, the business processing device of the microservice architecture in this embodiment is applicable to target business service nodes in a microservice cluster. The target business service node is deployed with a target memory grid node, which stores the service configuration information of the target business service node. When the target business service node starts, the information reading unit reads the service configuration information from the target memory grid node. The service registration unit registers the service in the target memory grid node based on the service configuration information, so that the target memory grid node stores the target registration information of the target business service node. The information synchronization unit synchronizes and stores the target registration information in the memory grid nodes of the associated business service nodes of the target business service node. The associated business service nodes are other business service nodes in the microservice cluster to which the target business service node belongs. The information storage unit receives the node registration information sent by the associated business service nodes and stores the node registration information in the target memory grid node. When the request processing unit receives the target business request sent by the target terminal device, it processes the target business request based on the registration information in the target memory grid node, obtains and returns the business processing result to the target terminal device.

[0191] Therefore, the embodiments of this application can implement a microservice architecture without relying on external service management nodes. Data is stored by deploying memory grid nodes on each business service node. The memory grid node data adopts a distributed multi-replica storage principle. When processing business requests, it can reduce the risk of business interruption caused by single point of failure, ensure that each business service is easy to maintain, help ensure the stability of the business service system, and improve business processing efficiency.

[0192] This application also provides an electronic device, which can be a terminal, a server, or other similar device. The terminal can be a mobile phone, tablet computer, smart Bluetooth device, laptop computer, personal computer, etc.; the server can be a single server or a server cluster composed of multiple servers, etc.

[0193] In some embodiments, the business processing device of the microservice architecture can also be integrated into multiple electronic devices. For example, the business processing device of the microservice architecture can be integrated into multiple servers, and the business processing method of the microservice architecture of this application can be implemented by multiple servers.

[0194] In this embodiment, a server will be used as an example for detailed description. For example, ... Figure 4 As shown, it illustrates a schematic diagram of the server structure involved in an embodiment of this application. Specifically:

[0195] The server may include components such as a processor 401 with one or more processing cores, a memory 402 with one or more computer-readable storage media, a power supply 403, an input module 404, and a communication module 405. Those skilled in the art will understand that... Figure 4 The server architecture shown does not constitute a limitation on the server and may include more or fewer components than illustrated, or combine certain components, or have different component arrangements. Wherein:

[0196] The processor 401 is the control center of the server, connecting various parts of the server via various interfaces and lines. It performs various server functions and processes data by running or executing software programs and / or modules stored in the memory 402, and by calling data stored in the memory 402. In some embodiments, the processor 401 may include one or more processing cores; in some embodiments, the processor 401 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may also not be integrated into the processor 401.

[0197] The memory 402 can be used to store software programs and modules. The processor 401 executes various functional applications and data processing by running the software programs and modules stored in the memory 402. The memory 402 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the server, etc. In addition, the memory 402 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 402 may also include a memory controller to provide the processor 401 with access to the memory 402.

[0198] The server also includes a power supply 403 that supplies power to the various components. In some embodiments, the power supply 403 can be logically connected to the processor 401 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 403 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0199] The server may also include an input module 404, which can be used to receive input numeric or character information, and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.

[0200] The server may also include a communication module 405. In some embodiments, the communication module 405 may include a wireless module, through which the server can perform short-range wireless transmission, thereby providing users with wireless broadband internet access. For example, the communication module 405 can be used to help users send and receive emails, browse web pages, and access streaming media.

[0201] Although not shown, the server may also include a display unit, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 401 in the server loads the executable files corresponding to the processes of one or more applications into the memory 402 according to the following instructions, and the processor 401 runs the applications stored in the memory 402, thereby implementing the steps in the methods of the various embodiments of this application.

[0202] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0203] As shown above, a microservice architecture can be implemented without relying on external service management nodes. Data can be stored by deploying memory grid nodes on each business service node. The memory grid node data adopts a distributed multi-replica storage principle, which can reduce the risk of business interruption caused by single point of failure when processing business requests, ensure that each business service is easy to maintain, help ensure the stability of the business service system, and improve business processing efficiency.

[0204] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0205] To this end, embodiments of this application provide a computer-readable storage medium storing multiple instructions that can be loaded by a processor to execute steps in any of the microservice architecture business processing methods provided in this application. This method is applicable to target business service nodes in a microservice cluster, where the target business service nodes are deployed with target memory grid nodes, and the target memory grid nodes store service configuration information of the target business service nodes. For example, the instructions can execute the following steps:

[0206] When the target service node starts, it reads the service configuration information from the target memory grid node;

[0207] Based on the service configuration information, service registration is performed in the target memory grid node so that the target memory grid node stores the target registration information of the target business service node;

[0208] The target registration information is synchronously stored in the memory grid node of the associated business service node of the target business service node. The associated business service node is another business service node in the microservice cluster to which the target business service node belongs.

[0209] Receive node registration information of associated service nodes sent by associated service nodes, and store the node registration information in the target memory grid node;

[0210] When a target service request is received from the target terminal device, the target service request is processed based on the registration information in the target memory grid node, and the service processing result is obtained and returned to the target terminal device.

[0211] The storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0212] According to one aspect of this application, a computer program product or computer program is provided, comprising a computer program / instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer program / instructions from the computer-readable storage medium and executes the computer program / instructions, causing the electronic device to perform methods provided in various optional implementations of the business processing aspects of the microservice architecture provided in the above embodiments.

[0213] Since the instructions stored in the storage medium can execute the steps in any of the microservice architecture business processing methods provided in the embodiments of this application, the beneficial effects that any of the microservice architecture business processing methods provided in the embodiments of this application can achieve can be realized. For details, please refer to the previous embodiments, which will not be repeated here.

[0214] The above provides a detailed description of a microservice architecture business processing method and related equipment provided in the embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A business processing method based on a microservice architecture, characterized in that, The method is applicable to target business service nodes in a microservice cluster, wherein the target business service node deploys a target memory grid node, and the target memory grid node stores the service configuration information of the target business service node; the method includes: When the target service node starts, it reads service configuration information from the target memory grid node; Based on the service configuration information, service registration is performed in the target memory grid node so that the target memory grid node stores the target registration information of the target service node. The target registration information is synchronously stored in the memory grid node of the associated business service node of the target business service node, and the associated business service node is another business service node in the microservice cluster to which the target business service node belongs; Receive the node registration information of the associated service node sent by the associated service node, and store the node registration information in the target memory grid node; When a target service request is received from a target terminal device, the target service request is processed based on the registration information in the target memory grid node, and the service processing result is obtained and returned to the target terminal device.

2. The method according to claim 1, characterized in that, When a target service request is received from a target terminal device, the process of processing the target service request based on the registration information in the target memory grid node, obtaining and returning the service processing result to the target terminal device, includes: When a target service request is received from a target terminal device through a gateway device, and it is detected that the target service request depends on an auxiliary service node, the node registration information of the auxiliary service node is searched through the registration information in the target memory grid node. Based on the node registration information of the auxiliary service node, the target service request is sent to the auxiliary service node, which is another service node in the microservice cluster other than the target service node; The auxiliary service node is triggered to process the target service request, obtain an intermediate service processing result, and return the intermediate service processing result to the target service node. The intermediate service processing results are processed to obtain and return the service processing results to the target terminal device.

3. The method according to claim 2, characterized in that, The method further includes: When a target service request is received from a target terminal device, a dependency service detection is performed on the target service request. When no other service nodes are detected to be dependent on the target service request, the target service request is processed, and the service processing result is obtained and returned to the target terminal device.

4. The method according to claim 1, characterized in that, The method further includes: When a fault event is detected during the processing of the target business request, the intermediate business processing data of the target business request is stored in the target memory grid node, and a reference business service node that can process the target business request is selected from the microservice cluster through the registration information in the target memory grid node. The intermediate service processing data is synchronized to the memory grid node of the reference service node through the target memory grid node; The reference service node is triggered to obtain the intermediate service processing data from its memory grid node, so that the reference service node processes the target service request based on the intermediate service processing data, and obtains and returns the service processing result to the target terminal device.

5. The method according to claim 1, characterized in that, Before synchronizing and storing the target registration information to the memory grid node in the associated business service node of the business service node, the method further includes: Based on the service cluster identifier information of the microservice cluster to which the target business service node belongs, a broadcast message is generated. By sending broadcast information within a preset area, the service nodes within the preset area are triggered to determine whether the service nodes within the preset area and the target service node belong to the same microservice cluster based on the broadcast information. Based on the judgment results, the associated business service nodes are determined.

6. The method according to claim 1, characterized in that, The gateway device is equipped with memory grid nodes, and the microservice cluster includes at least two distributed business service nodes; the memory gateway nodes in the gateway device synchronously store the registration information of each business service node. When a target service request is received from a target terminal device, the process of processing the target service request based on the registration information in the target memory grid node, obtaining and returning the service processing result to the target terminal device, includes: The gateway device receives a target service request sent by a target terminal device through a gateway device. The target service request instructs the gateway device to forward it to a service node in the microservice cluster that can handle the request. The gateway device determines the service node that can handle the request through the registration information in its memory grid node. Based on the target service request, the target service request is processed using the registration information in the target memory grid node, and the service processing result is obtained and returned to the target terminal device.

7. A business processing device with a microservice architecture, characterized in that, This is applicable to target business service nodes in a microservice cluster, wherein the target business service node is deployed with a target memory grid node, and the target memory grid node stores the service configuration information of the target business service node; The device includes: The information reading unit is used to read service configuration information from the target memory grid node when the target service node is started. A service registration unit is used to register services in the target memory grid node based on the service configuration information, so that the target memory grid node stores the target registration information of the target service node. An information synchronization unit is used to synchronize and store the target registration information to a memory grid node in the associated business service node of the target business service node, wherein the associated business service node is another business service node in the microservice cluster to which the target business service node belongs; An information storage unit is used to receive node registration information of the associated service node sent by the associated service node, and to store the node registration information in the target memory grid node; The request processing unit is used to process the target service request based on the registration information in the target memory grid node when it receives a target service request sent by the target terminal device, and to obtain and return the service processing result to the target terminal device.

8. An electronic device, characterized in that, It includes a processor and a memory, the memory storing multiple instructions; the processor loads instructions from the memory to execute steps in the business processing method of the microservice architecture as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a plurality of instructions adapted for loading by a processor to execute steps in the business processing method of the microservice architecture according to any one of claims 1 to 6.

10. A computer program product comprising multiple instructions, characterized in that, When the instruction is executed by the processor, it implements the steps in the business processing method of the microservice architecture according to any one of claims 1 to 6.

Images