Micro-service data decoupling interaction method and system and computer readable storage medium
By adopting data decoupling interaction method in the microservice architecture and using the stream event and version number matching mechanism, the timeliness and blocking problems during data interaction between microservices are solved, and efficient data transmission and stable operation of microservices are achieved. .
Patent Information
- Application Number
- CN202411040791.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-31
- Publication Date
- 2024-11-19
AI Technical Summary
In the microservice architecture, when data interaction between microservices occurs, data timeliness and microservice blockage may result in data time nodes and version mismatch, which may cause service termination.
The microservice data decoupling interaction method is adopted. By allowing only designated microservices to be modified when the data table is changed, and other microservices are notified through streaming events, the data consistency is ensured using version number matching, and invalid event delivery and blockage are reduced.
It effectively reduces data coupling between microservices, avoids data errors and service blockage caused by version mismatch, and ensures data timeliness and reliability.
Smart Images

Figure CN118984272A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the field of microservice technology, and in particular to a microservice data decoupling interaction method, system and computer-readable storage medium. Background Art
[0002] In the microservice architecture, each microservice is deployed and run independently. During the operation, data and information interaction between microservices is inevitable.
[0003] In the existing technology, a data table is usually set up. During the operation of the microservice framework, the data table will be read, written and overwritten by multiple microservice frameworks to achieve transmission between microservices. Although this method simplifies the transmission method and is more direct. However, in the interaction process, many different time nodes are often involved, and the data at each time node should be time-sensitive. When multiple microservices modify the data table, the microservice may be blocked due to the reading time factor, which will not only cause the microservice data to time out and fail, but may also cause the microservice to terminate. Summary of the invention
[0004] In order to solve the above problems, the present invention proposes a microservice data decoupling interaction method, system and computer-readable storage medium. The present invention changes the traditional form of microservice table modification to a single microservice corresponding to a unique data table. When the data table is changed, the unique data table can only be modified by the corresponding microservice, and the modification event of the external data table is notified by generating a stream event. Other microservices change their own data tables through the stream event. Through this form, the coupling of data between microservices is reduced, and the microservice termination or microservice blocking caused by the data validity exceeding the predetermined time when modifying the data table is further reduced.
[0005] The purpose of the present invention is achieved through the following technical solutions:
[0006] In a first aspect, the present invention proposes a microservice data decoupling interaction method, which is applied to multiple microservices and information flow channels connected to the microservices for communication, and the method includes:
[0007] Change the specified data table in any microservice, and send the specified flow event and the specified version number to the message flow channel, wherein the microservice that changes the specified data table is defined as the specified microservice, and the microservices other than the specified microservice are defined as the target microservice;
[0008] Determine whether the target microservice is associated with the specified microservice;
[0009] If yes, the target microservice receives the specified stream event and the specified version number, and processes the specified stream event according to the specified version number;
[0010] Otherwise, the target microservice does not process.
[0011] When changing a data table, a stream event is sent to other target microservices through the message stream channel. In order to reduce the coupling between microservices, the stream event is sent to the target microservice related to the modified microservice to reduce the generation of invalid stream events. After confirming that the target microservice is associated with the specified microservice, the stream event is received by the target microservice. In order to prevent message failure and timeout due to message timeout or version mismatch, the specified version number will be matched and determined. After the determination is completed, the stream event will be processed to reduce the problem of invalid data causing data errors to microservices and avoid microservice failure.
[0012] In some implementations, changing a specified data table in any of the microservices and sending a specified flow event and a specified version number to a message flow channel includes:
[0013] Backing up a first designated data table in any of the microservices, and modifying it to generate a second designated data table;
[0014] The second specified data table replaces the first specified data table, and the changed process is recorded as a flow event and assigned a specified version number.
[0015] When changing a data table, back up the currently specified data table for modification, and replace the original data table with the modified one. This method can avoid the risk of being unable to trace back due to direct modification errors. At the same time, the modification records are recorded in the form of stream events, and the modification version number is assigned to inform the current modified content and modified version.
[0016] In some implementations, changing a specified data table in any microservice and sending a specified flow event and a specified version number to a message flow channel includes:
[0017] Perform data upgrade and / or data change on the specified data table, and synchronously send the specified stream event generated by the data upgrade and / or data change and the specified version number corresponding to the data upgrade and / or data change to the message flow channel.
[0018] For the change table expansion data upgrade and / or data change of the specified data table, that is, the data upgrade and service data change of the microservice, after the data is changed and / or upgraded, the change and / or data is notified through the stream event to avoid other microservices from directly changing the specified data table, further affecting other microservices or the data of the specified microservice. This method can reduce the coupling between microservices.
[0019] In some implementations, determining whether the target microservice is associated with a specified microservice includes:
[0020] Determine whether the target microservice subscribes to the specified microservice. If so, send the specified stream event to the target microservice.
[0021] By subscribing, connections between microservices are established so that stream events can be accurately delivered to related microservices, thereby reducing the ineffective delivery of stream events between microservices.
[0022] In some implementations, processing a specified stream event according to a specified version number includes:
[0023] After obtaining the specified version number, the target microservice compares its current target version number with the specified version number. If the specified version number and the target version number are the same, the specified stream event is processed.
[0024] In order to ensure the timeliness of data and avoid erroneous data transmission at different times, especially in the process of microservice upgrade, version numbers will be set. By comparing version numbers, it is ensured that data in the same version, that is, at the same time, interacts to avoid data errors causing microservice stagnation or upgrade blockage.
[0025] In some implementations, processing a specified stream event according to a specified version number further includes:
[0026] The target microservice is set with a target data table, and processing of the specified stream event includes data upgrade, data change, waiting for processing, or no processing of the target data table.
[0027] The processing of specified stream events includes relative updates and / or data changes to the target data table, and / or waiting for other data in the target data table to be upgraded before processing, and / or taking no action on the event. The processing method of the target microservice is determined by the stream event, which can process data more flexibly, rather than forcing the processing after updating the data table, which may cause the task being executed by the microservice to stagnate or cause blocking with other microservices.
[0028] In some implementations, a priority value is also set for the specified stream event. When the target microservice processes the specified stream event, priority processing is performed based on the priority value.
[0029] When multiple stream events are received at the same time, a priority value will be set. The priority value is the degree of influence of the specified microservice outflowing from the specified stream event on the target microservice. The higher the priority value, the priority of processing the stream event.
[0030] In some implementations, data backup is also included, and data backup includes backing up designated stream events and designated data tables to a backup space.
[0031] In order to prevent data loss and achieve data traceability, the stream events and data tables in the interaction process are backed up so that when data errors occur, data can be backtracked based on the backed-up stream events and further backtracked on the data tables.
[0032] In a second aspect, the present invention proposes a microservice data decoupling interaction system, comprising:
[0033] Multiple microservices, with unique designated data tables;
[0034] Information flow channel, communicating with all microservices;
[0035] The microservices interact decoupledly through the information flow channel to perform operations including changing a specified data table in any microservice and sending a specified flow event and a specified version number to the message flow channel, wherein the microservice that changes the specified data table is defined as a specified microservice, and microservices other than the specified microservice are defined as target microservices;
[0036] Determine whether the target microservice is associated with the specified microservice;
[0037] If yes, the target microservice receives the specified stream event and the specified version number, and processes the specified stream event according to the specified version number;
[0038] Otherwise, the target microservice does not process.
[0039] It is mainly composed of microservices and information flow channels. Through the above two parts, a microservice data decoupling interaction method mentioned in the first aspect is realized.
[0040] In a third aspect, the present invention proposes a computer-readable storage medium, comprising at least one execution instruction stored in the storage medium, wherein when the microservice data decoupling interaction system of the second aspect is running, the executable instruction enables the system to execute a microservice data decoupling interaction method such as any one of the first aspect.
[0041] The microservice data decoupling interaction method, system and computer-readable storage medium of the present invention have the following beneficial effects:
[0042] By changing the specified data table in any microservice, sending the specified stream event and the specified version number to the message stream channel, and determining whether the target microservice is associated with the specified microservice, if the association is, the target microservice receives the specified stream event and the specified version number, and processes the specified stream event according to the specified version number. In the above manner, data interaction is carried out in the form of stream events, avoiding the form of directly changing data tables between microservices, reducing data upgrade errors caused by different versions of various microservices after data changes, and avoiding upgrade stagnation or upgrade blockage caused by different versions of data tables during upgrades, thereby reducing data coupling between microservices. BRIEF DESCRIPTION OF THE DRAWINGS
[0043] The accompanying drawings are only used to illustrate the embodiments and are not to be considered as limiting the present invention. In addition, the same reference symbols are used to represent the same components throughout the accompanying drawings. In the accompanying drawings:
[0044] Figure 1 This is a flow chart of the microservice data decoupling interaction method of the present invention;
[0045] Figure 2 A flowchart of modifying data tables, itinerary flow events and version numbers of the present invention;
[0046] Figure 3 This is a structural diagram of the microservice data decoupling interaction system of the present invention. DETAILED DESCRIPTION
[0047] Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present invention are shown in the drawings, it should be understood that the present invention can be implemented in various forms and should not be limited to the embodiments set forth herein.
[0048] Embodiment 1:
[0049] like Figure 1 As shown, this embodiment proposes a microservice data decoupling interaction method, which is applied to multiple microservices and information flow channels connected to the microservices for communication. The method includes:
[0050] Step 101: Change a specified data table in any microservice, and send a specified flow event and a specified version number to a message flow channel, wherein the microservice that changes the specified data table is defined as a specified microservice, and microservices other than the specified microservice are defined as target microservices;
[0051] Specifically, a designated data table is set in any designated microservice, and the designated data table can only be changed by the designated microservice, and other microservices cannot change it. When making changes, in order to notify other microservices, a designated stream event and a designated version number will be sent synchronously to inform other target microservices of the change of the designated data table, so that the target microservice makes corresponding changes to its own data table according to the changed stream event. The beneficial effect of this step is: through this method, other target microservices are notified in a form similar to information notification, rather than directly changing the data table, reducing the coupling between microservices. At the same time, the stream event notifies other microservices in the form of notification, so that the microservice can handle time more flexibly according to its own situation, which can avoid forcibly stopping its own service when the current microservice is still running, and also avoid blocking the microservice caused by forced waiting when other services are being upgraded.
[0052] Step 102: Determine whether the target microservice is associated with the specified microservice;
[0053] Specifically, to determine whether there is an association, when building the microservice framework, the relationship between microservices can be preset in advance according to the business and needs of the microservices themselves, so that the stream event can be accurately transmitted to the microservices that may be affected through the relationship between the microservices. The beneficial effect of this step is that by determining the association between the target microservice and the specified microservice, the stream event can be accurately sent to the associated microservice.
[0054] Step 103: If yes, the target microservice receives the specified stream event and the specified version number, and processes the specified stream event according to the specified version number;
[0055] Otherwise, the target microservice does not process.
[0056] Specifically, a version number or version identifier is set in the stream event to identify different version structures. After the target microservice receives the stream event, it will compare the version number of the stream event with the version number of its current data table. If the version numbers are consistent, the stream event will be processed, otherwise it will not be processed. The beneficial effect of this step is that the data interaction between microservices is in the same version through version number comparison, reducing the data interaction of the wrong version.
[0057] It should be noted that, under this method, each microservice is set up with a unique data table, so each microservice can send stream events accordingly, and form data interaction by sending stream events to each other.
[0058] When changing a data table, a stream event is sent to other target microservices through the message stream channel. In order to reduce the coupling between microservices, the stream event is sent to the target microservice related to the modified microservice to reduce the generation of invalid stream events. After confirming that the target microservice is associated with the specified microservice, the stream event is received by the target microservice. In order to prevent message failure and timeout due to message timeout or version mismatch, the specified version number will be matched and determined. After the determination is completed, the stream event will be processed to reduce the problem of invalid data causing data errors to microservices and avoid microservice failure.
[0059] In some embodiments, changing a specified data table in any of the microservices and sending a specified flow event and a specified version number to a message flow channel includes:
[0060] Step 201: back up a first designated data table in any of the microservices, and modify it to generate a second designated data table;
[0061] Specifically, a cache space is set, and when modifying, the original designated data table is copied to the cache space, and the data is modified in the cache space, thereby forming a second designated data table. The beneficial effect of this step is that it can avoid modification errors that cannot be traced back, and can provide original data reference for modifying data.
[0062] Step 202: Replace the first designated data table with the second designated data table, record the changed process as a flow event, and assign a designated version number.
[0063] Specifically, the modified second designated data table replaces the original first designated data table, and the change record is recorded in the form of a log to form a stream event, and a current version number is assigned. This step can form a time-sensitive stream event, thereby preventing data from being mismatched due to version errors.
[0064] When changing a data table, back up the currently specified data table for modification, and replace the original data table with the modified one. This method can avoid the risk of being unable to trace back due to direct modification errors. At the same time, the modification records are recorded in the form of stream events, and the modification version number is assigned to inform the current modified content and modified version.
[0065] In some embodiments, a specified data table in any microservice is changed, and a specified flow event and a specified version number are sent to a message flow channel; including:
[0066] Perform data upgrade and / or data change on the specified data table, and synchronously send the specified stream event generated by the data upgrade and / or data change and the specified version number corresponding to the data upgrade and / or data change to the message flow channel.
[0067] Specifically, the change of the data table includes data upgrade, and the change of the data includes data type change, data value change, and data relationship change. When sending the stream event, the change will be recorded in the stream event and sent to the outside. The beneficial effect of this embodiment is that for the change of the specified data table, the data upgrade and / or data change, that is, the data upgrade and service data change of the microservice, after the data is changed and / or the data is upgraded, the change and / or data is notified through the stream event to avoid other microservices directly changing the specified data table, further affecting other microservices or the data of the specified microservice. The method can reduce the coupling between microservices.
[0068] In some embodiments, determining whether the target microservice is associated with the specified microservice includes:
[0069] Determine whether the target microservice subscribes to the specified microservice. If so, send the specified stream event to the target microservice.
[0070] Specifically, determining the association between the target microservice and the specified microservice, that is, determining the association between the microservices, includes but is not limited to subscription, binding, etc., wherein the subscription method can enable the target microservice to subscribe to the specified microservice, or to subscribe to the specified stream event generated by the specified microservice. It should be noted that the subscription microservice can subscribe to one or more.
[0071] The beneficial effect of this step is that, by means of subscription, connections between microservices are established so that stream events can be accurately delivered to related microservices, thereby reducing ineffective delivery of stream events between microservices.
[0072] In some embodiments, processing a specified stream event according to a specified version number includes:
[0073] After obtaining the specified version number, the target microservice compares its current target version number with the specified version number. If the specified version number and the target version number are the same, the specified stream event is processed.
[0074] Specifically, if the obtained specified version number is 1.11.1, and the target version number of the target microservice itself is 1.11.1, it further indicates that the version numbers are the same, that is, the version number of the specified stream event is the same as the target microservice, and the specified stream event can be processed. If the current target version number is 1.11.0, it means that the versions are different. At this time, the target microservice does not process the specified stream event, or waits for its own version number to be upgraded to 1.11.1 before processing the stream event. The beneficial effect of this step is that in order to ensure the timeliness of data and avoid erroneous transmission of data at different times, especially in the process of microservice upgrade, the version number will be set, and the data at the same version, that is, at the same time, will be compared to ensure interaction, so as to avoid data errors causing microservice stagnation or upgrade blockage.
[0075] In some embodiments, processing a specified stream event according to a specified version number further includes:
[0076] The target microservice is set with a target data table, and processing of the specified stream event includes data upgrade, data change, waiting for processing, or no processing of the target data table.
[0077] Specifically, it also includes, for example, after confirming the version number, the specified stream event is upgraded from 1.11.1 to 1.11.2, then the corresponding target microservice also needs to be upgraded, but the target microservice can wait for the processing of the specified stream event according to its own situation, if the target microservice is in a state where it is not convenient to upgrade at this time, or, if its own needs do not need to be upgraded, it can not be processed and the target stream event can be sent back for feedback. Further, if data changes are required, for example, the specified stream event is to delete a certain data in the data table, then after the corresponding version number, the target microservice can delete the data in its own target data table for the corresponding data. The beneficial effect of this method is that the processing of the specified stream event includes relative update and / or data change of the target data table, and / or waiting for other data in its own target data table to be upgraded before processing, and / or no action is taken on the event. The processing method of the target microservice is determined by the stream event, and the data can be processed more flexibly, rather than forcing the processing after updating the data table, causing the task being executed by the microservice to stagnate or cause blocking with other microservices.
[0078] In some embodiments, a priority value is also set for the designated stream event. When the target microservice processes the designated stream event, priority processing is performed according to the priority value.
[0079] Specifically, a priority value is set, which can also be a priority flag. The priority value can be a specific value such as 1, 2, 3, etc., or a level such as a, b, c, etc. It should be noted that the priority value needs to be sorted according to the priority value, and the flow events are processed according to the priority value. For example, flow event 1 with a priority value of 1 and flow event 2 with a priority value of 3 can be processed by sorting the flow event with a priority value of 1 according to size. The beneficial effect of this method is that when multiple flow events are received at the same time, a priority value will be set. The priority value is the degree of influence of the specified microservice outflowing from the specified flow event on the target microservice. The higher the priority value, the higher the priority value, the priority of processing the flow event.
[0080] In some embodiments, the method further includes backing up data, and backing up data includes backing up specified stream events and specified data tables to a backup space.
[0081] Specifically, cloud backup and / or hardware backup space are set up, and each time a stream event is generated, the stream event is saved in the cloud backup space and / or hardware space. At the same time, when each microservice changes its own data table, the data table is synchronously updated to the cloud backup and / or hardware backup space. The beneficial effect of this step is that in order to prevent data loss and achieve data traceability, the stream events and data tables in the interaction process are backed up, so that when data errors occur, data can be backtracked based on the backed-up stream events, and further the data table can be backtracked.
[0082] Based on the above method steps, an example is proposed as a specific embodiment to apply the above method: Microservice 1 needs to modify some data in data table 1 due to business needs. Data table 1 belongs to microservice 1, so the microservice can directly modify the content of data table 1. While modifying the data, in order to notify other microservices, microservice 1 will send a stream event to message stream 1. Microservice 2 needs to pay attention to the changes in data table 1, so it will subscribe to stream event 1. In this way, when there is a new message in the stream event, this new message will be sent to microservice 2, and microservice 2 will process this information. This completes the message interaction process. Multiple microservices can subscribe to one or more message streams.
[0083] Embodiment 2:
[0084] like Figure 2 As shown, based on Example 1, this embodiment proposes a microservice data decoupling interaction system, which includes:
[0085] Multiple microservices, with unique designated data tables;
[0086] Information flow channel, communicating with all microservices;
[0087] The microservices interact decoupledly through the information flow channel to perform operations including changing a specified data table in any microservice and sending a specified flow event and a specified version number to the message flow channel, wherein the microservice that changes the specified data table is defined as a specified microservice, and microservices other than the specified microservice are defined as target microservices;
[0088] Determine whether the target microservice is associated with the specified microservice;
[0089] If yes, the target microservice receives the specified stream event and the specified version number, and processes the specified stream event according to the specified version number;
[0090] Otherwise, the target microservice does not process.
[0091] Through this system, each microservice is connected to the information flow channel. When a flow event is generated, it is published to other microservices through the information flow channel. At the same time, a separate data table is set inside each microservice to reduce the data coupling between microservices. The beneficial effect of this method is that through the above two parts, a microservice data decoupling interaction method as mentioned in the first aspect is realized.
[0092] Embodiment 3:
[0093] Based on Example 1, Example 2 This example proposes a computer-readable storage medium, including at least one execution instruction stored in the storage medium. When the executable instruction runs the microservice data decoupling interaction system as in Example 2, the system executes the microservice data decoupling interaction method as in Example 1.
[0094] By using the computer-readable storage medium, it is possible to change a specified data table in any microservice, and send a specified flow event and a specified version number to a message flow channel, wherein the microservice that changes the specified data table is defined as a specified microservice, and microservices other than the specified microservice are defined as target microservices;
[0095] Determine whether the target microservice is associated with the specified microservice;
[0096] If yes, the target microservice receives the specified stream event and the specified version number, and processes the specified stream event according to the specified version number;
[0097] Otherwise, the target microservice does not process.
[0098] The algorithms or displays provided herein are not inherently related to any particular computer, virtual system or other device. In addition, the embodiments of the present invention are not directed to any particular programming language.
[0099] In the description provided herein, a large number of specific details are described. However, it is understood that embodiments of the present invention can be practiced without these specific details. Similarly, in order to simplify the present invention and help understand one or more of the various inventive aspects, in the above description of exemplary embodiments of the present invention, the various features of the embodiments of the present invention are sometimes grouped together into a single embodiment, figure, or description thereof. Wherein, the claims that follow the specific embodiment are hereby expressly incorporated into the specific embodiment, wherein each claim itself is a separate embodiment of the present invention.
[0100] Those skilled in the art will appreciate that the modules in the devices in the embodiments may be adaptively changed and arranged in one or more devices different from the embodiments. The modules or units or components in the embodiments may be combined into one module or unit or component, and further may be divided into a plurality of submodules or subunits or subcomponents. Except that at least some of such features and / or processes or units are mutually exclusive.
[0101] It should be noted that the above embodiments illustrate the present invention rather than limit it, and that those skilled in the art may design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference symbol between brackets shall not be construed as a limitation on the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "one" or "an" preceding an element does not exclude the presence of a plurality of such elements. The present invention may be implemented by means of hardware comprising a number of different elements and by means of a suitably programmed computer. In a unit claim that lists a number of devices, several of these devices may be embodied by the same hardware item. The use of the words first, second, and third, etc. does not indicate any order. These words may be interpreted as names. The steps in the above embodiments, unless otherwise specified, should not be understood as limitations on the order of execution.
Claims
1. A method for decoupling and interacting microservice data. It is characterized in that Applied to a plurality of microservices and an information flow channel connected to the microservices for communication, the method comprises: Modify a specified data table in any of the microservices, and send a specified flow event and a specified version number to the message flow channel, wherein the microservice that modifies the specified data table is defined as a specified microservice, and microservices other than the specified microservice are defined as target microservices; Determine whether the target microservice is associated with the specified microservice; If yes, the target microservice receives the specified stream event and the specified version number, and processes the specified stream event according to the specified version number; Otherwise, the target microservice does not process.
2. According to the microservice data decoupling interaction method of claim 1, It is characterized in that The changing of a specified data table in any of the microservices, and sending a specified stream event and a specified version number to the message stream channel; include: Backing up a first designated data table in any of the microservices, and modifying it to generate a second designated data table; The first designated data table is replaced by the second designated data table, and the changed process is recorded as the flow event and assigned the designated version number.
3. According to the microservice data decoupling interaction method of claim 1, It is characterized in that The changing of a specified data table in any of the microservices, and sending a specified stream event and a specified version number to the message stream channel; include: The designated data table is subjected to data upgrade and / or data change, and the designated stream event generated by the data upgrade and / or data change and the designated version number corresponding to the data upgrade and / or data change are synchronously sent to the message stream channel.
4. The microservice data decoupling interaction method according to claim 1, It is characterized in that The determining whether the target microservice is associated with the designated microservice includes: Determine whether the target microservice subscribes to the specified microservice, and if so, send the specified stream event to the target microservice.
5. The microservice data decoupling interaction method according to claim 1, It is characterized in that The processing of the specified stream event according to the specified version number includes: After obtaining the specified version number, the target microservice compares its current target version number with the specified version number, and processes the specified stream event if the specified version number is the same as the target version number.
6. The microservice data decoupling interaction method according to claim 5, It is characterized in that The processing of the specified stream event according to the specified version number further includes: The target microservice is provided with a target data table, and the processing of the specified stream event includes upgrading data of the target data table, and / or changing data, and / or waiting for processing, and / or not processing.
7. The microservice data decoupling interaction method according to claim 1, It is characterized in that The designated stream event is also provided with a priority value. When the target microservice processes the designated stream event, priority processing is performed according to the priority value.
8. The microservice data decoupling interaction method according to claim 1, It is characterized in that The method also includes backing up the data, wherein the backing up the data includes backing up the designated stream event and the designated data table to a backup space.
9. A microservice data decoupling interaction system, It is characterized in that include: Multiple microservices, with unique designated data tables; Information flow channel, communicating with all microservices; The microservices interact decoupledly through the information flow channel to perform operations including changing a specified data table in any of the microservices, and sending a specified flow event and a specified version number to the message flow channel, wherein the microservice that changes the specified data table is defined as a specified microservice, and microservices other than the specified microservice are defined as target microservices; Determine whether the target microservice is associated with the specified microservice; If yes, the target microservice receives the specified stream event and the specified version number, and processes the specified stream event according to the specified version number; Otherwise, the target microservice does not process.
10. A computer-readable storage medium, It is characterized in that The storage medium includes at least one execution instruction stored therein, and the executable instruction enables the device to execute the microservice data decoupling interaction method according to any one of claims 1 to 8 in the microservice data decoupling interaction system according to claim 9.
