WO2019232962A1

WO2019232962A1 - Data processing method, system, computer device and storage medium

Info

Publication number: WO2019232962A1
Application number: PCT/CN2018/104727
Authority: WO
Inventors: 陈培镇; 陈泽晖; 李琦; 刘琼
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-06-06
Filing date: 2018-09-08
Publication date: 2019-12-12
Also published as: CN109213770A; CN109213770B

Abstract

A data processing method, a system, a computer device and a storage medium, the method comprising: an API Gateway receiving a service request sent by a client, and sending the service request to an order field micro-service, the order field micro-service sorting selected micro-services so as to generate an order event; a transaction scheduling center docking the micro-services after receiving the order event so as to execute the order event and output a service result; the micro-services sending a data alternation result to the order field micro-service by means of the transaction scheduling center so as to complete data update for each micro-service. The method coordinates each micro-service by adding the transaction scheduling center to guarantee data consistency when each micro-service calls multiple databases.

Description

Data processing method, system, computer equipment and storage medium

This application claims the priority of a Chinese patent application filed on June 07, 2018 with the Chinese Patent Office, application number 201810584611.3, and the invention name is "data processing method, system, computer equipment and storage medium", the entire contents of which are incorporated by reference. In this application.

Technical field

The present application relates to the field of information technology, and in particular, to a data processing method, system, computer device, and storage medium.

Background technique

A database is a warehouse that organizes, stores, and manages data according to the data structure. In an information society, the full and effective management and use of various information resources is a prerequisite for scientific research and decision management. Database technology is the core part of various information systems such as management information systems, office automation systems, and decision support systems. It is an important technical means for scientific research and decision management. Existing relational databases have the ability to solve complex transaction scenarios, and relational databases meet ACID characteristics, that is, atomicity, consistency, isolation, and permanence. A database with ACID characteristics supports strong consistency of data, which can ensure that the data itself does not appear inconsistent.

However, under the microservice architecture, each microservice has its own database. Once the system under the microservice architecture cannot simply meet the ACID characteristics, there will be inconsistencies in the data under the microservice architecture, including when a microservice When the service spans multiple databases at the same time, it is necessary to operate multiple data at the same time. As a result, some data in the database may fail to be updated and some data may be updated successfully. As a result, the consistency of the data cannot be guaranteed. The microservice has a strong dependency on the database , And easy to invade the micro service system, causing data loss; the existing services under the micro service cannot distinguish between business abnormalities and technical abnormalities, and can not deal with the abnormal situation in time.

Summary of the Invention

Based on this, it is necessary to provide data processing methods, systems, computer equipment, and storage media for problems such as inconsistent data updates during data processing, easy damage to databases, and loss of data.

A data processing method includes:

The interface gateway API Gateway receives the service request sent by the client, and sends the service request to the microservice in the order field. The microservice in the order field selects the microservice to be accessed according to the service request, and sends the selected microservice to the microservice. The services are sorted according to the order in which the business requests are met to generate order events that access the microservices one by one, and the API Gateway and the order field microservices are set in an application system;

After receiving the order event, the transaction scheduling center interfaces with each microservice, accesses the microservices one by one to execute the order event, and outputs a business result that meets the business request, and the transaction scheduling center is set in the application system;

The microservice sends a data replacement result generated when the order event is executed to the transaction scheduling center, the transaction scheduling center summarizes the data replacement result, and sends the data replacement result to the order field Microservices to complete the data update of each microservice.

Based on the same technical concept, this application also provides a data processing system, including:

Generate an order event unit and set it as the interface gateway API. The Gateway receives the business request sent by the client, and sends the business request to the order field microservice, and the order field microservice selects the service to be accessed according to the service request. Microservices, and sorting selected microservices in order of meeting the business request to generate order events for accessing microservices one by one, the API Gateway and the order field microservices are set in an application system;

The output business result unit is set to connect the microservices to the transaction scheduling center after receiving the order event, access the microservices one by one to execute the order event, and output the business results that satisfy the business request. The transaction scheduling center is set in the application. Within the system

A data update unit configured to send the micro service a data replacement result generated when the order event is executed to the transaction scheduling center, and the transaction scheduling center summarizes the data replacement result and the data replacement result Sending to the order field microservice to complete the data update of each microservice.

Based on the same technical concept, the present application also provides a computer device including a memory and a processor. The memory stores computer-readable instructions. When the computer-readable instructions are executed by the processor, the processing causes the processing. The processor performs the following steps:

Based on the same technical concept, the present application also provides a storage medium storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, the one or more processors execute the following steps:

The above data processing method, system, computer equipment, and storage medium receive the business request sent by the client through the API and Gateway, and send the business request to the order field microservice, and the order field microservice is based on the The business request selects the microservices to be accessed by the business request, and sorts the selected microservices according to the order in which the business requests are met to generate order events for accessing the microservices one by one; the transaction scheduling center receives After the order event, each microservice is docked, and the microservices are accessed one by one to execute the order event, and output the business result that meets the business request; the microservice sends the data replacement result generated when the order event is executed to the A transaction scheduling center that summarizes the data replacement results and sends them to the order field microservices to complete the data update of each microservice. Therefore, by adding a transaction scheduling center to coordinate various microservices, to ensure the consistency of data when each microservice calls multiple databases, at the same time, through the retry mechanism, increase the handling of abnormal conditions, improve the real-time nature of data calls and ensure The consistency of the data reduces the degree of dependence of the microservice on the database and avoids intrusion into the microservice system.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flowchart of a data processing method according to an embodiment of the present application;

2 is a schematic diagram of an environment of a data processing method according to an embodiment of the present application;

3 is a schematic diagram of a data processing system according to an embodiment of the present application;

Among them, 1-mobile client; 2-API Gateway; 3-microservices in the order field; 4-microservices in the account field; 5-microservices in the customer field; 6-product microservices; 7-transaction scheduling center; 8-Nginx operating system.

Detailed ways

In order to make the purpose, technical solution, and advantages of the present application clearer, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the application, and are not used to limit the application.

Those skilled in the art will understand that the singular forms "a", "an", "the" and "the" used herein may include the plural forms unless specifically stated. It should be further understood that the wording "including" used in the specification of the present application refers to the presence of the described features, procedures, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, Procedures, steps, operations, elements, components and / or groups thereof.

FIG. 1 is a flowchart of a data processing method according to an embodiment of the present application. As shown in FIG. 1, the data processing method may include the following steps:

Step S1: The interface gateway API receives the service request sent by the client, and sends the service request to the order field microservice. The order field microservice selects the microservice to be accessed according to the service request, and The selected microservices are sorted according to the order in which the business requests are satisfied to generate order events for accessing the microservices one by one, and the API Gateway and the order domain microservices are set in an application system.

In this embodiment, the generating an order event for accessing microservices one by one includes:

The client obtains a service request through the input interface, calls a sending interface to send the service request to the API Gateway, and the API connects to the order field microservice through a data interface, and sends the service request to the order. In the field microservice, the order field microservice selects the microservices to be accessed according to the business request, and sorts the selected microservices according to the order in which the business requests are satisfied to generate one-by-one access microservices. Order event, the input interface and the sending interface are set on the client.

The client refers to a program corresponding to a server and providing local services for the client, and includes a mobile client, a computer client, and a third-party client. The client in this embodiment may be selected as a mobile client. The mobile client refers to software running on a mobile terminal, which can provide enterprises with complete, convenient, diverse and efficient mobile marketing. The user can input a service request through the input interface of the mobile client at any time, and send the service request by calling the sending interface.

In this embodiment, the application system may be selected as the Nginx application system. The Nginx application system is a high-performance HTTP and reverse proxy server for load balancing. It can directly support Rails and PHP programs within it. External services can also support external services as an HTTP server. At the same time, Nginx application system also has the advantages of occupying less memory and strong concurrency.

In this embodiment, the API Gateway refers to an API gateway, that is, a service request sent by a client needs to go through the API Gateway and then reach the microservice in the order field. The API Gateway as the same external interface of the system can reduce the caller's perception of service implementation.

The mobile client obtains the service request through the input interface, and calls the sending interface to send the business request. The Nginx application system sets an API Gateway and order field microservices. The API Gateway receives the service sent by the mobile client. After the request, the order domain microservice is called by calling a data interface, and the business request is sent to the order domain microservice. The order domain microservice will select the microservice to be accessed according to the business request, and The selected microservices are sorted according to the order in which the business requests are satisfied to generate order events for accessing the microservices one by one, and the input interface and the sending interface are set on the mobile client.

Step S2: After receiving the order event, the transaction scheduling center interfaces with each microservice, accesses the microservices one by one to execute the order event, and outputs a business result that meets the business request. The transaction scheduling center is set in the application system.

In this embodiment, the output of a service result satisfying the service request includes:

The transaction scheduling center includes a data processing interface. The transaction scheduling center receives an order event sent by the order field microservice after docking with the order field microservice through the data processing interface. The transaction scheduling center connects with other data processing interfaces through the data processing interface. Microservices, which access microservices one by one to execute order events, output business results that satisfy the business request, and the transaction scheduling center is set in the application system.

The purpose of the transaction scheduling center is to ensure the real-time validity of the data in the database, thereby ensuring that each microservice can run reliably. It includes a data processing interface, and the transaction scheduling center interfaces with each microservice through the data processing interface to execute all the services. The order event.

A transaction scheduling center is set on the Nginx application system. The service scheduling center connects to the microservices in the order field through the data processing interface, receives order events sent by the service scheduling center, and connects to other microservices through the data processing interface. , Accessing microservices one by one to execute the order event, and outputting a business result that satisfies the business request.

Step S3: the microservice sends the data replacement result generated when the order event is executed to the transaction scheduling center, the transaction scheduling center summarizes the data replacement result, and sends the data replacement result to all The microservices in the order field are described to complete the data update of each microservice.

In this embodiment, the update result of the aggregated data and updating the microservice data include:

After the microservice provides the required service for it according to the requirements of the business request, the microservice completes the data replacement result generated by the business request by calling the database record corresponding to the microservice, and updates the data. The result is sent to a transaction scheduling center, which includes a data processing core, and the transaction scheduling center sums up the data replacement result by calling the data processing core, and sends the data replacement result to the order field micro Services to complete data update of each microservice, and the database is set on the operation interface of the microservice.

The database refers to a data collection that is stored together in a certain way, can be shared by multiple users, has as little redundancy as possible, and is independent of the application program. It is integrated and shared. It is a management information system, The core parts of various types of information, such as office automation systems and decision support systems, are important technical means for scientific research and decision management. The database includes Oracle, MySQL, DB2 or Sybase. In this embodiment, the database can be selected as the Oracle database. The Oracle database is a relational database management system of Oracle Corporation, which has been in the leading position in the database field. Its system is portable, easy to use, and functional. Strong, can be applied to all kinds of large, medium, small, and microcomputer environments.

When the transaction scheduling center performs the docking micro service, an abnormal situation occurs when the docking micro service times out or the micro service cannot provide services, and the transaction scheduling center reports the abnormal situation to the order field micro service, and the order field The microservice will retry the order event until the microservice can re-execute the order event. For example, when the transaction scheduling center docks with microservices through the data processing interface, a docking timeout occurs. The transaction scheduling center will report the abnormal situation to the order field microservice, and the order field The micro service will resend the service request, so that the transaction scheduling center reconnects with the micro service.

In the above embodiment, a micro-service is coordinated by adding a transaction scheduling center to ensure data consistency when each micro-service calls multiple databases. At the same time, through the retry mechanism, increase the handling of abnormal conditions, improve the real-time nature of data calls and ensure data consistency.

FIG. 2 is a schematic diagram of an environment of a data processing method according to an embodiment of the present application. As shown in FIG. 2, the selected client is the mobile client 2, the selected application system is the Nginx application system 8, and the Nginx application system is set. APIGateway2, microservices in the order area3, microservices in the account area4, microservices in the customer area5, microservices in the product area6, and transaction scheduling center7.

The mobile client 1 is provided with an input interface and a sending interface. The mobile client 1 obtains a service request for fund purchase from the input interface, and calls the sending interface to send the service request for fund purchase to the API Gateway 2 and API Gateway 2 through the Internet. A data interface is set up on the interface, and is connected to the microservice 3 in the order field through the data interface, and sends the business request for the subscription fund to the microservice 3 in the order field. After receiving the business request, the microservice 3 in the order field selects the access required for fund subscription. The microservices are sorted according to the order in which the subscription funds are completed, and the order events for the subscription funds are generated, and the order events are sent to the transaction scheduling center 7, which includes a data processing core and data Processing interface. The transaction scheduling center 7 connects to the order field microservice 3 through the data processing interface to receive order events for fund purchases, and docks the microservices one by one in accordance with the order of the microservices displayed on the event order to complete the fund purchase.

The product field microservice 6 is called, and the product field microservice 6 determines whether the fund can be purchased according to the subscription amount of the fund product under the fund company. When product service microservice 6 judges that the fund is unavailable for purchase, it feeds back the judgment result to transaction scheduling center 7, and transaction scheduling center 7 feeds back to mobile client 1 through API Gateway2 to inform users that the fund cannot be processed. Purchase. In the product field microservices 6, after judging that the fund can be purchased, the judgment result is fed back to the transaction scheduling center 7, the transaction scheduling center 7 connects with the customer domain microservice 5, and the customer domain microservice 5 is based on the user account deposit, and the fund purchase amount And purchase time to determine whether the user meets the subscription conditions of the fund. When the customer domain microservice 5 determines that the customer does not meet the subscription conditions of the fund, the judgment result is fed back to the transaction scheduling center 7 and the transaction scheduling center 7 Then it returns to the mobile client 1 through the API Gateway2 to inform the user that the fund's subscription conditions are not met. When the customer domain microservice 5 judges that the customer meets the purchase conditions of the fund, the judgment result is fed back to the transaction scheduling center 7, the transaction scheduling center 7 connects to the account field microservice 4, and the account field microservice 4 is based on the fund purchase amount. The user's account deposit is deducted from the user's account deposit, and the fund purchase transaction is recorded, and the fund payment deducted from the user's account deposit is fed back to the transaction dispatch center 7, and the transaction dispatch center 7 passes the API. Gateway2 feeds back to mobile client 1 and informs the user of the success of the fund purchase and the amount deducted due to the fund purchase.

After the subscription fund transaction is completed, the product field microservices 6 feeds back the number of fund products purchased to the transaction scheduling center 7, and the customer field microservices 6 feed back the user's account deposit information to the transaction scheduling center 7 and the account field microservices 4 The information of the amount deducted from the user's account deposit due to the purchase fund is fed back to the transaction scheduling center 7. The transaction scheduling center 7 summarizes the data replacement results in each microservice by calling the data processing core therein, and sends the data replacement results to the order field microservice 3.

In the above embodiment, by inputting the business request of the subscription fund on the mobile client 1, using API Gateway2 to select the required microservices for the subscription fund, and generating order events in sequence, the transaction scheduling center 7 receives the order events one by one. Visit microservices to execute order events and complete fund purchases. The transaction scheduling center 7 saves time for accessing all microservices one by one, and improves the efficiency of fund purchase.

Based on the same technical concept, an embodiment of the present application further provides a data processing system. As shown in FIG. 3, the system includes an order generation unit, an output service result unit, and a data update unit.

The order generation event unit is set to an API. The Gateway receives a service request sent by a client and sends the service request to the order field microservice, and the order field microservice selects a service to be accessed according to the service request. Microservices, and sorting selected microservices in order of meeting the business request to generate order events for accessing microservices one by one, the API Gateway and the order field microservices are set in an application system;

The output service result unit is configured to connect the micro service to each micro service after receiving the order event, access the micro services one by one to execute the order event, and output a service result that meets the business request. The application system;

The data update unit is configured so that the microservice sends a data replacement result generated when the order event is executed to the transaction scheduling center, and the transaction scheduling center summarizes the data replacement result and sends it to The order field microservices complete the data update of each microservice.

In the foregoing embodiment, the order generation event unit receives a service request sent by a client through an API through Gateway, and sends the service request to the order field microservice, and the order field microservice is selected according to the service request. The microservices that need to be accessed, and the selected microservices are sorted according to the order in which the business requests are met, to generate order events for accessing the microservices one by one; using the output business result unit to receive all services through the transaction scheduling center After the order event is described, each microservice is docked, and the microservices are accessed one by one to execute the order event, and the business result that meets the business request is output; the data update unit uses the microservice to change the data generated when the order event is executed The result is sent to the transaction scheduling center, and the transaction scheduling center summarizes the data replacement result and sends it to the order field microservice to complete the data update of each microservice. By adding a transaction scheduling center to coordinate each microservice, it is guaranteed that the data consistency is guaranteed when each microservice calls multiple databases.

In one embodiment, the order generation event unit includes: a service request sending module configured to obtain a service request from a client through an input interface, and call the sending interface to send the service request to the API Gateway, the input interface And the sending interface are set on the client; a docking module is set up so that the API connects the microservices in the order field through the data interface and sends the business request to the microservices in the order field; selecting and The ordering module is configured for the order field microservice to select the microservices to be accessed according to the business request, and to sort the selected microservices according to the order in which the business requests are met to generate one-by-one access microservices Order event.

In one embodiment, the output service result unit includes: an order receiving event module configured to include a data processing interface in the transaction scheduling center, and the transaction scheduling center receives the microservices in the order field through the data processing interface. The order event sent by the microservice in the order field is described. The docking microservice module is set up to connect the transaction scheduling center to other microservices through the data processing interface, access the microservices one by one to execute the order event, and output the information that meets the business request. As a result of the business, the transaction scheduling center is set in the application system.

In one embodiment, the data update unit includes: a record and send result module, configured to provide the microservice with required services according to the requirements of the business request, and then call a database record corresponding to the microservice to complete this. The data replacement result generated by the second service request, the micro service sends the data replacement result to the transaction scheduling center, the database is set on the micro service operation interface; the result module is aggregated and sent, and is set as the The transaction scheduling center includes a data processing core, and the transaction scheduling center summarizes the data replacement result by calling the data processing core, and sends the data replacement result to the order field microservice to complete the data of each microservice. Update.

In one embodiment, the database includes Oracle, MySQL, DB2, or Sybase.

In one embodiment, the client includes a mobile client, a computer client, and a third-party client; and the application system includes an Nginx application system and a WEB application system.

In one embodiment, the output service result unit is further configured that, when the transaction scheduling center performs the docking micro service, an exception occurs when the docking micro service times out or the micro service cannot provide services, and the transaction scheduling center sends the The abnormal situation is fed back to the order domain microservice, and the order domain microservice will retry the order event until the microservice can re-execute the order event.

Based on the same technical concept, the present application also proposes a computer device including a memory, a processor, and computer-readable instructions stored on the memory and executable on the processor, the processing When the processor executes the computer-readable instructions, the steps in the data processing method in the foregoing embodiments are implemented.

Based on the same technical concept, the present application also provides a storage medium storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, the one or more processors execute the foregoing implementations. The steps in the data processing method in the example.

A person of ordinary skill in the art can understand that all or part of the processes in the methods of the foregoing embodiments can be implemented by using a computer program to instruct related hardware. The computer program can be stored in a computer-readable storage medium. When executed, the processes of the embodiments of the methods described above may be included. The foregoing storage medium may be a non-volatile storage medium such as a magnetic disk, an optical disc, a read-only memory (ROM), or a random access memory (Random Access Memory, RAM).

The technical features of the embodiments described above can be arbitrarily combined. In order to simplify the description, all possible combinations of the technical features in the above embodiments have not been described. However, as long as there is no contradiction in the combination of these technical features, It should be considered as the scope described in this specification.

The above-mentioned embodiments only express several implementation manners of the present application, and their descriptions are more specific and detailed, but they should not be construed as limiting the patent scope of the present application. It should be noted that, for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can be made, and these all belong to the protection scope of the present application. Therefore, the protection scope of this application patent shall be subject to the appended claims.

Claims

A data processing method includes:

The interface gateway API Gateway receives the service request sent by the client, and sends the service request to the microservice in the order field. The microservice in the order field selects the microservice to be accessed according to the service request, and sends the selected microservice to the microservice. The services are sorted according to the order in which the business requests are met to generate order events that access the microservices one by one, and the API Gateway and the order field microservices are set in an application system;

After receiving the order event, the transaction scheduling center interfaces with each microservice, accesses the microservices one by one to execute the order event, and outputs a business result that meets the business request, and the transaction scheduling center is set in the application system;

The microservice sends a data replacement result generated when the order event is executed to the transaction scheduling center, the transaction scheduling center summarizes the data replacement result, and sends the data replacement result to the order field Microservices to complete the data update of each microservice.
The data processing method according to claim 1, wherein the generating an order event for accessing microservices one by one comprises:

The client obtains the business request through the input interface, and calls the sending interface to send the business request to the API Gateway. The API Gateway connects to the microservices in the order field through the data interface, and sends the business request to the order field. In microservices, the order field microservice selects the microservices to be accessed according to the business request, and sorts the selected microservices according to the order in which the business requests are met to generate one-by-one access to the microservices. For an order event, the input interface and the sending interface are set on the client.
The data processing method according to claim 1, wherein the output of a service result satisfying the service request comprises:

The transaction scheduling center includes a data processing interface, and the transaction scheduling center receives the order event sent by the order field microservice after docking with the order field microservice through the data processing interface, and the transaction scheduling center uses the data processing interface. Docking other microservices, accessing microservices one by one to execute order events, outputting business results that satisfy the business request, and the transaction scheduling center is set in the application system.
The data processing method according to claim 1, wherein the update result of the summary data and updating the microservice data comprises:

After the microservice provides the required services according to the requirements of the business request, the database service corresponding to the microservice is called to complete the data replacement result generated by the business request, and the microservice sends the data replacement result to the transaction. A scheduling center, the transaction scheduling center includes a data processing core, and the transaction scheduling center summarizes the data replacement result by calling the data processing core, and sends the data replacement result to the order field microservice to complete The data of each microservice is updated, and the database is set on the operation interface of the microservice.
The data processing method according to claim 4, wherein the database comprises Oracle, MySQL, DB2 or Sybase.
The data processing method according to claim 1, wherein the client comprises a mobile client, a computer client, and a third-party client;

The application system includes an Nginx application system and a WEB application system.
The data processing method according to claim 1, wherein when the transaction scheduling center performs the docking micro service, an abnormal situation occurs when the docking micro service times out or the micro service cannot provide services, and the transaction scheduling center sends the The abnormal situation is fed back to the order domain microservice, and the order domain microservice will retry the order event until the microservice can re-execute the order event.
A data processing system includes:

Generate an order event unit and set it as the interface gateway API. The Gateway receives the business request sent by the client and sends the business request to the order field microservice, and the order field microservice selects the microservice to be accessed according to the business request And sort the selected microservices according to the order in which the business requests are met to generate order events that access the microservices one by one, the API Gateway and the order field microservices are set in the application system;

The output business result unit is set to connect the microservices to the transaction scheduling center after receiving the order event, access the microservices one by one to execute the order event, and output the business results that satisfy the business request. The transaction scheduling center is set in the application. Within the system

A data update unit, configured to send the micro service a data replacement result generated when the order event is executed to the transaction scheduling center, the transaction scheduling center summarizes the data replacement result, and stores the data replacement result Sending to the order field microservice to complete the data update of each microservice.
The data processing system according to claim 8, wherein the order generation unit includes:

The sending service request module is configured to obtain a service request from a client through an input interface, call the sending interface to send the service request to the API Gateway, and the input interface and the sending interface are set on the client;

The docking module is configured to connect the API Gateway to a microservice in the order field through a data interface, and send the business request to the microservice in the order field;

A selection and sorting module configured to set the order field microservices to select the microservices to be accessed according to the business request, and sort the selected microservices according to the order in which the business requests are met to generate one by one Access to microservice order events.
The data processing system according to claim 8, wherein the output service result unit comprises:

An order event receiving module, configured that the transaction scheduling center includes a data processing interface, and the transaction scheduling center receives an order event sent by the order field microservice after connecting to the order field microservice through the data processing interface;

The docking microservice module is configured to connect the transaction scheduling center with other microservices through the data processing interface, access the microservices one by one to execute order events, and output a business result that meets the business request. The transaction scheduling center is set at The application system.
The data processing system according to claim 8, wherein the data update unit comprises:

Record and send a result module, which is set to provide the microservice with the required services according to the requirements of the business request, and then call the database corresponding to the microservice to record the data replacement result generated by the business request. The service sends the data replacement result to a transaction scheduling center, and the database is set on an operation interface of the microservice;

The summary and transmission result module is configured so that the transaction scheduling center includes a data processing core, and the transaction scheduling center summarizes the data replacement result by calling the data processing core, and sends the data replacement result to the order field Microservices to complete the data update of each microservice.
The data processing system according to claim 11, wherein the database comprises Oracle, MySQL, DB2 or Sybase.
The data processing system according to claim 8, wherein the client comprises a mobile client, a computer client, and a third-party client;

The application system includes an Nginx application system and a WEB application system.
The data processing system according to claim 8, wherein the output service result unit is further configured that when the transaction scheduling center performs a docking microservice, an abnormal situation occurs when the docking microservice times out or the microservice cannot provide services. , The transaction scheduling center feedbacks the abnormal situation to the order domain microservice, and the order domain microservice will retry the order event until the microservice can re-execute the order event.
A computer device includes a database and a processor. The database stores computer-readable instructions. When the computer-readable instructions are executed by the processor, the processor causes the processor to perform the following steps:

The interface gateway API Gateway receives the service request sent by the client, and sends the service request to the microservice in the order field. The microservice in the order field selects the microservice to be accessed according to the service request, and sends the selected microservice to the microservice. The services are sorted according to the order in which the business requests are met to generate order events that access the microservices one by one, and the API Gateway and the order field microservices are set in an application system;

After receiving the order event, the transaction scheduling center interfaces with each microservice, accesses the microservices one by one to execute the order event, and outputs a business result that meets the business request, and the transaction scheduling center is set in the application system;

The microservice sends a data replacement result generated when the order event is executed to the transaction scheduling center, the transaction scheduling center summarizes the data replacement result, and sends the data replacement result to the order field Microservices to complete the data update of each microservice.
The computer device of claim 15, wherein when generating an order event for accessing the microservices one by one, the processor is caused to perform the following steps:

The client obtains the business request through the input interface, and calls the sending interface to send the business request to the API Gateway. The API Gateway connects to the microservices in the order field through the data interface, and sends the business request to the order field. In microservices, the order field microservice selects the microservices to be accessed according to the business request, and sorts the selected microservices according to the order in which the business requests are met, so as to generate a For an order event, the input interface and the sending interface are set on the client.
The computer device according to claim 15, wherein when the output meets a service result of the service request, the processor is caused to perform the following steps:

The transaction scheduling center includes a data processing interface, and the transaction scheduling center receives the order event sent by the order field microservice after docking with the order field microservice through the data processing interface, and the transaction scheduling center uses the data processing interface. Docking other microservices, accessing microservices one by one to execute order events, outputting business results that satisfy the business request, and the transaction scheduling center is set in the application system.
A storage medium storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, the one or more processors execute the following steps:

The interface gateway API Gateway receives the service request sent by the client, and sends the service request to the microservice in the order field. The microservice in the order field selects the microservice to be accessed according to the service request, and sends the selected microservice to the microservice. The services are sorted according to the order in which the business requests are met to generate order events that access the microservices one by one, and the API Gateway and the order field microservices are set in an application system;

After receiving the order event, the transaction scheduling center interfaces with each microservice, accesses the microservices one by one to execute the order event, and outputs a business result that meets the business request, and the transaction scheduling center is set in the application system;

The microservice sends a data replacement result generated when the order event is executed to the transaction scheduling center, the transaction scheduling center summarizes the data replacement result, and sends the data replacement result to the order field Microservices to complete the data update of each microservice.
The storage medium of claim 18, wherein when generating an order event for accessing microservices one by one, one or more processors are caused to perform the following steps:

The client obtains the business request through the input interface, calls the sending interface to send the business request to the API Gateway, and the API Gateway connects to the microservices in the order field through the data interface and sends the business request to the order field In microservices, the order field microservice selects the microservices to be accessed according to the business request, and sorts the selected microservices according to the order in which the business requests are met, so as to generate a For an order event, the input interface and the sending interface are set on the client.
The storage medium according to claim 18, wherein when the output meets a service result of the service request, causing one or more processors to perform the following steps:

The transaction scheduling center includes a data processing interface, and the transaction scheduling center receives the order event sent by the order field microservice after docking with the order field microservice through the data processing interface, and the transaction scheduling center uses the data processing interface. Docking other microservices, accessing microservices one by one to execute order events, outputting business results that satisfy the business request, and the transaction scheduling center is set in the application system.