CN116012146A - Event-based forehead center data asynchronous calculation method and system - Google Patents

Abstract

The invention discloses an event-based line center data asynchronous calculation method and system, wherein the method comprises the following steps of S1, obtaining user line change and generating line change events; s2, updating the limit change event into a data table under the same transaction; s3, the step of calling an interface to asynchronously send the user id information to a message queue of a message consumer; s4, the step of calculating all product limit information under the current user name again is used for calling the background interface of the consumer message. According to the event-based limit center data asynchronous calculation method and system disclosed by the invention, on one hand, the problems of reduced performance of the database caused by slower interface response, overlong lock occupation time in the database and the like when the flow is relatively large are prevented by simplifying the number of the tables, and on the other hand, the concurrency capacity of the corresponding interfaces and the TPS of the system are improved, so that the whole system can bear higher flow and concurrency.

Description

Event-based forehead center data asynchronous calculation method and system

Technical Field

The invention relates to the field of computers, in particular to an event-based method and an event-based system for asynchronously calculating data of a quota center.

Background

In an enterprise financial credit scene, interfaces related to real-time calculation of the credit amount, such as offer, pay-off, repayment, credit and the like, are related to a plurality of tables in data processing, and have the conditions of complex calculation, large transactions and the like, so that when the flow is relatively large, the problems of slow response of the interfaces, overlong lock occupation time in a database and the like, which cause the performance reduction of the database and the like, exist.

However, in the prior art, the simple lateral expansion of the interfaces causes excessive pressure in terms of enterprise funds and operation and maintenance, and how to improve concurrency capacity of the corresponding interfaces and TPS (Transaction processing systems, transaction processing system) of the system, so that the whole system can bear higher flow and concurrency, which becomes a problem to be solved urgently.

Disclosure of Invention

The invention aims to provide an event-based method and an event-based system for asynchronously calculating the data of a quota center.

The invention provides an event-based limit center data asynchronous calculation method, which comprises the following steps:

s1, acquiring user quota change and generating a quota change event;

s2, updating the limit change event into a data table under the same transaction;

s3, the step of calling an interface to asynchronously send the user id information to a message queue of a message consumer;

s4, the step of calculating all product limit information under the current user name again is used for calling the background interface of the consumer message.

Preferably, the step S2 is used for updating the credit change event into the data table under the same transaction, and includes:

s21 is used for judging the precondition of the line change event, if no corresponding index record exists in the data table, corresponding index data is newly added in the line change statistical information table and the processing identification table, and if the corresponding index record exists in the data table, the line change statistical information table and the processing identification table are updated.

Preferably, the step S4 is configured to invoke the consumer message backend interface to recalculate all product quota information under the current user name, and includes:

s41, a step for acquiring a user quota change event from a message queue;

s42, submitting the user credit change event to a credit thread pool for parameter analysis, and generating analysis data;

s43 is used for calling a quota processing logic interface to calculate the analysis data, and the formula is as follows:

a step of generating calculated data;

s44, updating the calculated data into the business record table and the limit change statistical information table, and updating the identification in the processing identification table.

Preferably, the event-based quota-center data asynchronous calculation method provided by the invention further comprises the following steps:

and a step of judging whether a credit change event exists, if not, performing synchronous calculation, updating the calculated credit information into the data table, and if so, directly inquiring the credit information and updating the credit information into the data table.

The event-based quota-centric data asynchronous computing system provided in this embodiment includes the following modules:

s1, a module for acquiring the user quota change and generating a quota change event;

s2, a module for updating the limit change event to a data table under the same transaction;

s3, a module for calling an interface to asynchronously send the user id information to a message queue of a message consumer;

s4, a module for calling a consumer message background interface to recalculate all product limit information under the current user name.

Preferably, the step S2 is configured to update the credit change event to a data table under the same transaction, and includes:

s21 is used for judging the precondition of the line change event, if no corresponding index record exists in the data table, corresponding index data is newly added in the line change statistical information table and the processing identification table, and if the corresponding index record exists in the data table, the sub-module is used for updating the line change statistical information table and the processing identification table.

Preferably, the S4 is a module for calling the consumer message background interface to recalculate all product quota information under the current user name, including:

s41 is used for obtaining a sub-module of the user quota change event from the message queue;

s42 is used for submitting the user quota change event to a quota thread pool for parameter analysis and generating a submodule for analyzing data;

s43 is used for calling a quota processing logic interface to calculate the analysis data, and the formula is as follows:

a sub-module that generates calculated data;

s44 is used for updating the calculated data into the business record table and the limit change statistical information table, and updating the sub-module for processing the identification in the identification table.

Preferably, the event-based quota-centric data asynchronous computing system provided by the present invention further comprises:

and the sub-module is used for judging whether a credit change event exists, if not, carrying out synchronous calculation, updating the calculated credit information into the data table, and if so, directly inquiring the credit information and updating the credit information into the data table.

According to the event-based quota center data asynchronous calculation method and system, on one hand, the number of tables is simplified, the problems that the number of the tables is large, complex calculation, large transactions and the like are involved in data processing, when the flow is relatively large, interface response is slow, the occupied time of a lock in a database is too long and the like, so that the performance of the database is reduced are solved, on the other hand, only the quota change event is asynchronously pushed to a message consumer to asynchronously calculate the back stage of the queue waiting message consumer, and therefore the concurrency capacity of the corresponding interface and the TPS of the system are improved, and the whole system can bear higher flow and concurrency.

Drawings

FIG. 1 is a flowchart of an event-based method for asynchronous computation of credit center data according to an embodiment of the invention;

fig. 2 is a calculation formula diagram of the maximum credit limit according to an embodiment of the invention.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

Example 1

As shown in fig. 1-2, the event-based quota-center data asynchronous calculation method provided in this embodiment includes the following steps:

s1, acquiring user quota change and generating a quota change event;

s2, updating the limit change event into a data table under the same transaction;

s3, the step of calling an interface to asynchronously send the user id information to a message queue of a message consumer;

s4, the step of calculating all product limit information under the current user name again is used for calling the background interface of the consumer message.

Those skilled in the art will appreciate that the borrowing, repayment, freezing, offer, product line points, etc. for each id user are referred to as line change events. The method comprises the steps of simplifying the storage operations of complex business logic, credit calculation, new addition or update of a large number of tables and the like in an interface to only operate three tables of a most basic business record table, a credit change statistical information table and a processing identification table, reducing the operation of the large number of tables between the database and the database as much as possible, and reducing the duration of a data resource lock of the database.

It can be understood by those skilled in the art that modifying the quota calculation service logic, in order to decouple the association between the calculation logic and the interface and consider the factors that the event message data needs to be persistent, a rabitmq message middleware is introduced, after the original processing interface stores the core data, the corresponding client id information is sent to the message queue, the whole interface service is completed, and then successful response data is returned.

Further, the step S2 is configured to update the credit change event to a data table under the same transaction, including:

s21 is used for judging the precondition of the line change event, if no corresponding index record exists in the data table, corresponding index data is newly added in the line change statistical information table and the processing identification table, and if the corresponding index record exists in the data table, the line change statistical information table and the processing identification table are updated.

Those skilled in the art will appreciate that the service record table records the current event record, including clients, products, event types, event amounts, and other information such as the current service serial number (unique identifier) is used for interfacing idempotent, preventing repeated submission, and creating events, updating time, etc., and the later table can be used for checking functions, etc. The credit change statistical information table is used for recording all change total credit information of the current user. The processing identification table records the occurrence information of the limit event and the identification flag (indicating whether the event is processed or not), the flag bit is set to be processed after the background processing is finished, and the flag bit is updated to be processed when a new event comes in. In terms of indexing, three tables are added with a unique identification index of the customer plus product dimension. In terms of consistency of data, operations for three tables in code logic must be in the same database transaction. The operations of the credit change statistical information table and the processing identification table are newly recorded, the data is newly added when the corresponding index data is not contained in the table, and the corresponding data is updated when the corresponding unique index record is contained (including the processing identification is set as unprocessed, the credit change information and the like), so that the record of the core data only relates to three tables, the interface service logic is simplified, the number of the tables is reduced, and the tables related to the transaction are reduced to three.

Further, the step S4 is configured to invoke the consumer message backend interface to recalculate all product quota information under the current user name, and includes:

s41, a step for acquiring a user quota change event from a message queue;

s42, submitting the user credit change event to a credit thread pool for parameter analysis, and generating analysis data;

s43 is used for calling the quota processing logic interfaceThe port calculates the analytic data, and the formula is:

a step of generating calculated data;

s44, updating the calculated data into the business record table and the limit change statistical information table, and updating the identification in the processing identification table.

Those skilled in the art will appreciate that A, B, E, F, G, X represents a different product; a1 and B1 respectively represent successful marketing limits of the product: and the information consumer background consumes the user id transmitted from the front in real time, then recalculates all product limit information under the clients, configures a plurality of consumers, sets a small number of message delivery quantity, prevents message data from being backlogged on one consumer, and is convenient for fully utilizing the resources of the plurality of consumers. In order to fully utilize the performance of the multi-core CPU, a thread pool for specially calculating the quota task is introduced into a consumer, the quota calculation is submitted to the thread pool as a task, and the thread pool is responsible for executing business logic of the task.

Further, the event-based quota-center data asynchronous calculation method provided in this embodiment further includes:

and a step of judging whether a credit change event exists, if not, performing synchronous calculation, updating the calculated credit information into the data table, and if so, directly inquiring the credit information and updating the credit information into the data table.

As can be appreciated by those skilled in the art, for the aspect of inquiring the credit, whether event information exists is judged before inquiring the credit, if so, synchronous calculation is performed, and then the credit information is responded, so that the correctness of the credit information is ensured.

Example two

The event-based quota-centric data asynchronous computing system provided in this embodiment includes the following modules:

s1, a module for acquiring the user quota change and generating a quota change event;

s2, a module for updating the limit change event to a data table under the same transaction;

s3, a module for calling an interface to asynchronously send the user id information to a message queue of a message consumer;

s4, a module for calling a consumer message background interface to recalculate all product limit information under the current user name.

Those skilled in the art will appreciate that the borrowing, repayment, freezing, offer, product line points, etc. for each id user are referred to as line change events. The method comprises the steps of simplifying the storage operations of complex business logic, credit calculation, new addition or update of a large number of tables and the like in an interface to only operate three tables of a most basic business record table, a credit change statistical information table and a processing identification table, reducing the operation of the large number of tables between the database and the database as much as possible, and reducing the duration of a data resource lock of the database.

It can be understood by those skilled in the art that modifying the quota calculation service logic, in order to decouple the association between the calculation logic and the interface and consider the factors that the event message data needs to be persistent, a rabitmq message middleware is introduced, after the original processing interface stores the core data, the corresponding client id information is sent to the message queue, the whole interface service is completed, and then successful response data is returned.

Further, the step S2 is configured to update the credit change event to a data table under the same transaction, and includes:

s21 is used for judging the precondition of the line change event, if no corresponding index record exists in the data table, corresponding index data is newly added in the line change statistical information table and the processing identification table, and if the corresponding index record exists in the data table, the sub-module is used for updating the line change statistical information table and the processing identification table.

Those skilled in the art will appreciate that the service record table records the current event record, including clients, products, event types, event amounts, and other information such as the current service serial number (unique identifier) is used for interfacing idempotent, preventing repeated submission, and creating events, updating time, etc., and the later table can be used for checking functions, etc. The credit change statistical information table is used for recording all change total credit information of the current user. The processing identification table records the occurrence information of the limit event and the identification flag (indicating whether the event is processed or not), the flag bit is set to be processed after the background processing is finished, the flag bit is updated to be processed when a new event comes in, and in order to prevent the concurrent operation from covering data, the table adopts an optimistic lock processing system added with a version field, so that the performance is improved. In terms of indexing, three tables are added with a unique identification index of the customer plus product dimension. In terms of consistency of data, operations for three tables in code logic must be in the same database transaction. The operations of the credit change statistical information table and the processing identification table are newly recorded, the data is newly added when the corresponding index data is not contained in the table, and the corresponding data is updated when the corresponding unique index record is contained (including the processing identification is set as unprocessed, the credit change information and the like), so that the record of the core data only relates to three tables, the interface service logic is simplified, the number of the tables is reduced, and the tables related to the transaction are reduced to three.

Further, the S4 is a module for calling the consumer message background interface to recalculate all product quota information under the current user name, including:

s41 is used for obtaining a sub-module of the user quota change event from the message queue;

s42 is used for submitting the user quota change event to a quota thread pool for parameter analysis and generating a submodule for analyzing data;

s43 is used for calling a quota processing logic interface to calculate the analysis data, and the formula is as follows:

/>

a sub-module that generates calculated data;

s44 is used for updating the calculated data into the business record table and the limit change statistical information table, and updating the sub-module for processing the identification in the identification table.

Those skilled in the art will appreciate that A, B, E, F, G, X represents a different product; a1 and B1 respectively represent successful marketing limits of the product: and the information consumer background consumes the user id transmitted from the front in real time, then recalculates all product limit information under the clients, configures a plurality of consumers, sets a small number of message delivery quantity, prevents message data from being backlogged on one consumer, and is convenient for fully utilizing the resources of the plurality of consumers. In order to fully utilize the performance of the multi-core CPU, a thread pool for specially calculating the quota task is introduced into a consumer, the quota calculation is submitted to the thread pool as a task, and the thread pool is responsible for executing business logic of the task.

Further, the event-based quota-centric data asynchronous computing system provided in this embodiment further includes:

and the sub-module is used for judging whether a credit change event exists, if not, carrying out synchronous calculation, updating the calculated credit information into the data table, and if so, directly inquiring the credit information and updating the credit information into the data table.

As can be appreciated by those skilled in the art, for the aspect of inquiring the credit, whether event information exists is judged before inquiring the credit, if so, synchronous calculation is performed, and then the credit information is responded, so that the correctness of the credit information is ensured.

Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and are not limiting; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims (8)

1. An event-based forehead center data asynchronous calculation method is characterized by comprising the following steps:

s1, acquiring user quota change and generating a quota change event;

s2, updating the limit change event into a data table under the same transaction;

s3, the step of calling an interface to asynchronously send the user id information to a message queue of a message consumer;

s4, the step of calculating all product limit information under the current user name again is used for calling the background interface of the consumer message.

2. The event-based forehead centre data asynchronous calculation method according to claim 1, wherein S2 is used to update the forehead change event into the data table under the same transaction, including:

s21 is used for judging the precondition of the line change event, if no corresponding index record exists in the data table, corresponding index data is newly added in the line change statistical information table and the processing identification table, and if the corresponding index record exists in the data table, the line change statistical information table and the processing identification table are updated.

3. The event-based credit-centric data asynchronous calculation method according to claim 2, wherein S4 is for invoking a consumer message backend interface to recalculate all product credit information under the current user name, comprising:

s41, a step for acquiring a user quota change event from a message queue;

s42, submitting the user credit change event to a credit thread pool for parameter analysis, and generating analysis data;

s43 is used for calling a quota processing logic interface to calculate the analysis data, and the formula is as follows:

a step of generating calculated data;

s44, updating the calculated data into the business record table and the limit change statistical information table, and updating the identification in the processing identification table.

4. The event-based limit center data asynchronous calculation method as recited in claim 3 further comprising:

and a step of judging whether a credit change event exists, if not, performing synchronous calculation, updating the calculated credit information into the data table, and if so, directly inquiring the credit information and updating the credit information into the data table.

5. An event-based forehead centre data asynchronous computing system, comprising the following modules:

s1, a module for acquiring the user quota change and generating a quota change event;

s2, a module for updating the limit change event to a data table under the same transaction;

s3, a module for calling an interface to asynchronously send the user id information to a message queue of a message consumer;

s4, a module for calling a consumer message background interface to recalculate all product limit information under the current user name.

6. The event-based, line centric data asynchronous computing system of claim 5, wherein S2 is configured to update the line change event to a data table under the same transaction, comprising:

s21 is used for judging the precondition of the line change event, if no corresponding index record exists in the data table, corresponding index data is newly added in the line change statistical information table and the processing identification table, and if the corresponding index record exists in the data table, the sub-module is used for updating the line change statistical information table and the processing identification table.

7. The event based credit center data asynchronous computing system of claim 6, wherein S4 is a module for invoking a consumer message backend interface to recalculate all product credit information under the current user name, comprising:

s41 is used for obtaining a sub-module of the user quota change event from the message queue;

s42 is used for submitting the user quota change event to a quota thread pool for parameter analysis and generating a submodule for analyzing data;

s43 is used for calling a quota processing logic interface to calculate the analysis data, and the formula is as follows:

a sub-module that generates calculated data;

s44 is used for updating the calculated data into the business record table and the limit change statistical information table, and updating the sub-module for processing the identification in the identification table.

8. The event-based, limit center data asynchronous computing system of claim 7, further comprising:

and the sub-module is used for judging whether a credit change event exists, if not, carrying out synchronous calculation, updating the calculated credit information into the data table, and if so, directly inquiring the credit information and updating the credit information into the data table.

Images