Business data checking method and device, storage medium and checking platform

Abstract

The application discloses a kind of service data checking method, device and storage medium, checking platform, the method comprises: access the middleware of the service function module of multiple applications, when the target event corresponding to the service function module is monitored to change, target service data is obtained from the middleware corresponding to target event;Target service data is checked using pre-established business rules, and when the checking result is data exception, alarm is carried out.The method can automatically access the change of each event in each application service and middleware in complex distributed system architecture, each event change will trigger the pre-established business rule script to execute corresponding check, to determine whether target service data exists abnormal data.The method discovers online business dirty data or error logic with high real-time, discovers in the first time and promptly informs technical support department, and promptly repairs.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, and in particular to a business data checking method and device, a storage medium and a checking platform. BACKGROUND

[0002] With the increasing scale and complexity of software systems, the calling between systems becomes more and more complex. In such a complex distributed system architecture, problems such as remote call failure, timeout, message sending failure, and concurrency bug inevitably occur. These problems eventually lead to inconsistency of data between systems. SUMMARY

[0003] The present application aims to at least solve one of the technical problems in the related art. To this end, one object of the present application is to provide a business data checking method that can discover dirty data or incorrect logic of online business in real time and notify technical support in the first place.

[0004] A second object of the present application is to provide a business data checking device.

[0005] A third object of the present application is to provide a computer-readable storage medium.

[0006] A fourth object of the present application is to provide a checking platform.

[0007] To achieve the above objects, the first aspect of the present application provides a business data checking method, which comprises the following steps: accessing middleware corresponding to business function modules of a plurality of applications, and obtaining target business data from the middleware corresponding to a target event when a change in the target event is monitored; checking the target business data using a pre-established business rule, and issuing an alarm when the checking result is data abnormality.

[0008] The business data checking method according to the embodiments of the present application can automatically access changes in each event occurring in each application service and middleware in a complex distributed system architecture. Each event change triggers a pre-established business rule script to perform corresponding checking to determine whether the target business data contains abnormal data. The embodiments of the present application can discover dirty data or incorrect logic of online business in real time and notify technical support in the first place.

[0009] In addition, the business data checking method according to the above embodiments of the present application can have the following additional technical features:

[0010] According to one embodiment of the present application, the process of establishing the business rules comprises: determining a plurality of business function modules of the applications; and compiling a business rule corresponding to each of the business function modules according to a loss point of each of the business function modules, to generate the business rules.

[0011] According to one embodiment of the present application, the middleware corresponding to the business function modules of the applications comprises: determining a type of each of the business function modules; determining a middleware corresponding to each of the business function modules according to the type of each of the business function modules, and constructing a standardized subscription component according to an interface type of the middleware; and accessing the middleware corresponding to each of the business function modules by using the standardized subscription component.

[0012] According to one embodiment of the present application, the middleware comprises at least one of a database log, a message queue, a database, a distributed search and analysis engine.

[0013] According to one embodiment of the present application, the process of checking the target business data by using the pre-established business rules comprises: determining a target business rule from the pre-established business rules according to the target event; and checking the target business data by using the target business rule.

[0014] According to one embodiment of the present application, before the process of checking the target business data by using the pre-established business rules, the method further comprises: determining a delay time length according to a level of the business function module; and checking the target business data by using a preset target business rule after a time length from a change of the target event corresponding to the business function module reaches the delay time length.

[0015] According to one embodiment of the present application, the method further comprises: determining a business function module coverage rate according to a number of the business function modules corresponding to the business rules.

[0016] To achieve the above object, a second aspect of the present application provides a business data checking device, which comprises: an access module, configured to access middleware corresponding to business function modules of a plurality of applications, and to obtain target business data from the middleware corresponding to a target event of the business function modules when a change of the target event is monitored; and a checking module, configured to check the target business data by using pre-established business rules, and to alarm when a checking result is data abnormality.

[0017] To achieve the above object, a third aspect of the present application provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the business data checking method according to the first aspect of the present application.

[0018] To achieve the above object, the fourth aspect of the present application provides a verification platform, comprising a memory and a processor, wherein the memory stores a computer program, and the computer program is executed by the processor to realize the business data verification method according to the first aspect of the present application.

[0019] Additional aspects and advantages of the present application will be made apparent by the following description and the accompanying drawings. BRIEF DESCRIPTION OF DRAWINGS

[0020] Figure 1 is a flowchart of the business data verification method according to an embodiment of the present application;

[0021] Figure 2 is a flowchart of constructing a business rule according to an embodiment of the present application;

[0022] Figure 3 is a flowchart of accessing middleware according to an embodiment of the present application;

[0023] Figure 4 is a flowchart of the business data verification according to a specific embodiment of the present application;

[0024] Figure 5 is a flowchart of verifying target business data according to an embodiment of the present application;

[0025] Figure 6 is a schematic diagram of a use environment according to an embodiment of the present application;

[0026] Figure 7 is a flowchart of the business data verification according to a specific embodiment of the present application;

[0027] Figure 8 is a schematic diagram of a business data verification device according to an embodiment of the present application;

[0028] Figure 9 is a structural block diagram of a verification platform according to an embodiment of the present application. DETAILED DESCRIPTION

[0029] Embodiments of the present application are described in detail below with reference to the accompanying drawings, wherein the same or similar notations are used to denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to explain the present application, and should not be understood as limiting the present application.

[0030] The business data verification method, device and storage medium, and verification platform according to the embodiments of the present application are described in detail below with reference to the accompanying drawings and specific embodiments.

[0031] Figure 1 is a flowchart of a service data checking method of an embodiment of the present application. As shown in Figure 1 , the service data checking method can include:

[0032] S101, accessing middleware corresponding to service function modules of multiple applications, and obtaining target service data from middleware corresponding to a target event when a change in the target event is monitored;

[0033] S102, checking the target service data using a pre-established service rule, and alarming when the checking result is data abnormality.

[0034] When dirty data or error logic occurs in online services, there is a certain delay in waiting for customers to find and feedback, which can cause serious losses. To find and timely notify technical support at the first time when dirty data or error logic occurs in online services, an embodiment of the present application accesses middleware corresponding to service function modules of multiple (at least one) applications using a checking platform, and listens to services of online service function modules in real time. When a change in a target event of the service function module is monitored, a pre-established service rule script is triggered to perform corresponding checking to determine whether target service data obtained from middleware corresponding to the target event has abnormal data.

[0035] Specifically, an application that needs to be checked for service data is determined, and a service function module in the corresponding application that needs to be checked for service data is determined. Middleware corresponding to multiple service function modules that need to be checked for service data is accessed to the checking platform. The checking platform listens to services of the accessed service function modules in real time, and obtains target service data from middleware corresponding to a target event (an event for which a corresponding service rule is pre-established) when a change in the target event is monitored. The checking platform checks the target service data using a pre-established service rule, and alarms when the checking result is data abnormality. R&D testers can find and locate problems for repair and fast online at the first time.

[0036] The service data checking method of the embodiment of the present application can automatically access each event change of each application service and middleware in a complex distributed system architecture. Each event change triggers a pre-established service rule script to perform corresponding checking to determine whether target service data has abnormal data.

[0037] In an embodiment of the present application, as shown in Figure 2 , the process of establishing a service rule includes:

[0038] S201, determining service function modules of multiple applications;

[0039] S202, according to the capital loss checking point of each business function module, write the business rules corresponding to each business function module, and generate the business rules.

[0040] Specifically, the tester sorts out multiple applications and multiple business function modules corresponding to the multiple applications. According to the capital loss checking point of the business function module, the business rule script of the corresponding test module is written, and the business rule is generated. For example, the tester performs the test of the battery replacement order payment scene, and can write the checking rule of the payment amount consistency, checks whether the amount on the order and the actual payment amount are consistent, if consistent, the rule checking is passed, if inconsistent, the checking fails, and the corresponding personnel is notified to enter the troubleshooting.

[0041] It can be implemented that the grovy rule engine is used to write the rule script when the business rule script of the corresponding test module is written.

[0042] In the embodiments of the application, the core business function modules can be preferentially accessed, such as the payment business function module, the marketing business function module, the order business function module, etc., and the business rules corresponding to each core business function module are preferentially written to quickly prewarn the core business function modules.

[0043] In an embodiment of the application, as shown in Figure 3 The middleware corresponding to the business function modules of the multiple applications is accessed, including:

[0044] S301, determining the type of the business function modules of the multiple applications;

[0045] S302, determining the middleware corresponding to each business function module according to the type of each business function module, and constructing a standardized subscription component according to the interface type of the middleware;

[0046] S303, accessing the middleware corresponding to each business function module by using the standardized subscription component.

[0047] As shown in Figure 4 Since there are multiple different types of middleware in the distributed system architecture, in order to access different types of middleware, the standardized subscription component constructed in the embodiments of the application interfaces different types of middleware.

[0048] Specifically, types of service function modules of a plurality of applications are determined, and a middleware corresponding to each service function module is determined according to each type of service function module, such as Binlog (database log), MQ (message queue), and ES (distributed search and analysis engine). A standardized subscription component is constructed according to an interface type of the middleware. The standardized subscription component is used to access the middleware corresponding to each service function module. After accessing the middleware corresponding to each service function module, a corresponding response event is accessed, and data is assembled, such as a parameter required by a corresponding checking rule, a trigger node of the checking rule, and the like. The checking platform is triggered to perform a checking process, and abnormal data is obtained.

[0049] In an embodiment of the present application, the middleware at least includes one of a database log, a message queue, a database, and a distributed search and analysis engine.

[0050] Specifically, the middleware can be a Binlog database log, a mq message queue, a redis database, an ES distributed search and analysis engine, and a log.

[0051] In an embodiment of the present application, the standardized subscription component can access a Binlog (database log), a mq (message queue), a redis (database), an ES (distributed search and analysis engine), and a log, to obtain target business data of a target event from the corresponding middleware.

[0052] In an embodiment of the present application, as shown in Figure 5 checking the target business data using the preset target business rule can include:

[0053] S401, determining a target business rule from a preset business rule according to a target event;

[0054] S402, checking the target business data using the target business rule.

[0055] Specifically, a business rule corresponding to the target event is queried from the preset business rule according to the target event, and the business rule is recorded as the target business rule. The target business data is checked using the target business rule.

[0056] In an embodiment of the present application, before checking the target business data using the preset target business rule, the business data checking method further includes:

[0057] The delay duration is determined according to the level of the service function module, and the target business data is checked using the preset target business rule after a duration of the target event corresponding to the service function module changes and reaches the delay duration.

[0058] The service function module can be classified according to importance levels (a first level, a second level, a third level, etc.), and the delay time length is determined. If the service function module type is the first level, the preset target service rule is used to check the target service data immediately after the target event of the service function module changes. If the service function module type is the third level, the preset target service rule is used to check the target service data after a preset time delay after the target event of the service function module changes. It should be noted that the higher the importance level, the shorter the delay time length.

[0059] The delay time length in the embodiment of the application can be minutes, hours, days, etc. The embodiment of the application does not limit the length of the delay time length, and the length can be specifically limited as required.

[0060] The delay time length can also be determined according to the type of the service function module, and whether the service function module has a timing task can also be detected. For example, if the timing task needs to be checked at a specified time, such as generating a bill at 0 o'clock, the checking only needs to be performed once after 0 o'clock.

[0061] The checking process can be manually controlled by directly writing an sql script to control the checking platform to perform the checking process, or the checking platform can be started to trigger the checking process to realize real-time, T+H (hours), and T+N (days) verification.

[0062] In an embodiment of the application, the service data checking method can further include determining the service function module coverage rate according to the number of service function modules corresponding to the pre-established service rule.

[0063] Because of the wide application, the number of service function modules in the application is also relatively large. In order to understand the service function module coverage rate of the service data checking, the number of service function modules corresponding to the service rule and the total number of service function modules in all applications that need to be checked can be counted to determine the service function module coverage rate of the service data checking, so as to understand the service data checking coverage.

[0064] It should be noted that, as shown in Figure 6 The service data checking method of the embodiment of the application can be reused for monitoring and checking in multiple environments (test environment, demo environment, and prod environment), and the test environment case can be copied to the demo and prod environments for use.

[0065] It should be noted that the related data checking method needs to be manually checked after the test environment use case is executed, and the automatic checking is not perfect. The business data checking method of the embodiment of the present application provides perfect checking and verification in the test environment, discovers problems in time, so as to repair as soon as possible and ensure the continuous and stable delivery of software.

[0066] When the test case is executed, the events of each node of the business system when the business data changes will trigger the execution of these rule scripts, and the data checking is performed to judge the correctness. If the rule checking is correct, it is passed, and if the checking fails, the enterprise WeChat robot will be notified to the development and test to alarm, and the problem is checked in the first time.

[0067] The test personnel combs the checking points of the function before the project is put into test, and writes the checking rule script on the checking platform. After the test environment is put into test, the test personnel executes the case to automatically trigger the rule checking function whether it is passed. After the project is released to the demo environment, the test personnel can copy the script to the demo environment, and the automatic test case automatically executes the regression test, and automatically triggers the rule checking function whether it is passed. After the project is released to the production, the online user uses the business function, and the rule is automatically triggered whether there is abnormal data.

[0068] The test environment can be intervened to check, and the test personnel can write the business rule script on the checking platform in the test environment. The test personnel checks the rule script execution result to perform data checking in the project test stage, avoids missing data verification in the test environment, and can be connected to the automatic regression test, and the case is executed by hand to check, and the test resources are saved.

[0069] The business data checking method of the embodiment of the present application is described by a specific embodiment:

[0070] As shown in Figure 7 , the test personnel tests the order placing module using the coupon, the test personnel combs the data checking points (such as the coupon deduction 5 yuan, the user payment amount = order amount-coupon amount) of the order amount and the amount to be paid after the coupon deduction, and writes the business rule script corresponding to each event of the order placing module using the coupon on the checking platform.

[0071] When the test case of placing an order using a coupon is executed, the checking platform automatically receives the message of the change of the order related table of the coupon deduction database (the coupon amount on the order checking table = the coupon deduction amount), the message of the change of the database marketing related table after deduction (the coupon amount on the order checking table = the coupon deduction amount), the third-party Alipay payment success callback message (the user payment amount = the order amount - the coupon amount), the message of the order service sent to the marketing service (the used state of the deducted coupon is changed), and other messages of various events, automatically triggers the business rule script of the order placing module using a coupon to perform checking, and judges whether the data stored in the database is correct. If the checking fails, the test personnel can be notified through the enterprise WeChat and the like to intervene, the developer locates the problem and modifies the bug to be released quickly online, so that further loss of funds is avoided.

[0072] The embodiment of the application can perform real-time monitoring after the business function module is online, and can alarm corresponding personnel in real time when there is data anomaly.

[0073] The application provides a business data checking device.

[0074] Figure 8 Fig. 1 is a schematic diagram of a business data checking device according to an embodiment of the application. As shown in Fig. 1, the business data checking device 100 can include: Figure 8 An access module 10 is configured to access the middleware corresponding to the business function module of a plurality of applications, and to acquire target business data from the middleware corresponding to a target event when the target event is monitored to change.

[0075] A checking module 20 is configured to check the target business data by using a pre-established business rule, and to alarm when the checking result is data anomaly.

[0076] When dirty data or error logic occurs in an online business, it is delayed to find and feedback by a customer, and serious loss can be caused. In order to find and timely notify the technical support in the first time when dirty data or error logic occurs in the online business, the embodiment of the application accesses the middleware corresponding to the business function module of a plurality of (at least one) applications by using the checking platform, and listens to the business of the online business function module in real time. When the target event is monitored to change, the pre-established business rule script is triggered to perform corresponding checking, and whether the target business data acquired from the middleware corresponding to the target event is abnormal data is judged.

[0077]

[0078] ​Specifically, the application needing to be checked for business data is determined, and the business function modules in the corresponding application are checked for the middleware corresponding to the plurality of business function modules. The checking platform listens to the business of the online business function modules in real time, and when a target event change is monitored, the target business data is obtained from the middleware corresponding to the target event. The checking platform checks the target business data by using the pre-established business rules, and alarms when the checking result is data anomaly, so that the R&D testers can find and locate the problems and quickly put them online.

[0079] The business data checking method of the embodiment of the application can automatically access each event change of each application service and middleware in a complex distributed system architecture. Each event change triggers the pre-established business rule script to perform corresponding checking, and judges whether the target business data has abnormal data.

[0080] In an embodiment of the application, the business data checking device 100 further comprises a rule service module configured to receive the business rules.

[0081] In an embodiment of the application, the process of establishing the business rules comprises: determining the business function modules of the plurality of applications; and writing the business rules corresponding to each business function module according to the checking points of each business function module, to generate the business rules.

[0082] In an embodiment of the application, the access module 10 is configured to determine the middleware corresponding to the business function modules according to the types of the business function modules of the plurality of applications; and access the middleware according to the interface types of the middleware.

[0083] According to an embodiment of the application, the middleware at least comprises one of a database log, a message queue, a database, a distributed search and analysis engine.

[0084] In an embodiment of the application, the checking module 20 is configured to determine the target business rule from the pre-established business rules according to the target event; and check the target business data by using the target business rule.

[0085] In an embodiment of the application, the checking module 20 is configured to determine the delay duration according to the type of the business function module, and check the target business data by using the preset target business rule when the duration after the target event change reaches the delay duration.

[0086] In an embodiment of the application, the business data checking device 100 further comprises a statistical module configured to determine the business function module coverage rate according to the number of the business function modules corresponding to the pre-established business rules.

[0087] It should be noted that other specific embodiments of the service data checking device provided by the embodiments of the present application can refer to the other specific embodiments of the service data checking method of the above-mentioned embodiments of the present application.

[0088] The service data checking device of the embodiments of the present application can automatically access the changes of various events of various application services and middleware in the system in a complex distributed system architecture, and the various event changes will trigger the pre-established business rule script to perform corresponding checking to determine whether the target service data has abnormal data. The online business dirty data or error logic can be found in high real-time manner, and the technical support can be found and notified in the first time.

[0089] The present application provides a computer readable storage medium.

[0090] In this embodiment, the computer readable storage medium stores a computer program, and the computer program is executed by the processor to implement the service data checking method as described above.

[0091] The present application provides a checking platform.

[0092] In this embodiment, the checking platform can include a memory and a processor, and the memory stores a computer program, and the computer program is executed by the processor to implement the service data checking method as described above.

[0093] Figure 9 The present application provides a checking platform.

[0094] As shown in Figure 9 The checking platform 500 includes a processor 501 and a memory 503. The processor 501 and the memory 503 are connected, such as through a bus 502. Optionally, the checking platform 500 can also include a transceiver 504. It should be noted that in actual application, the transceiver 504 is not limited to one, and the structure of the checking platform 500 does not constitute a limitation on the embodiments of the present application.

[0095] The processor 501 can be a CPU (Central Processing Unit), a general-purpose processor, a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It can implement or execute various exemplary logical blocks, modules and circuits described in conjunction with the present disclosure. The processor 501 can also be a combination of computing functions, such as one or more microprocessor combinations, combinations of DSP and microprocessor, etc.

[0096] The bus 502 can include a path for transmitting information between the above-mentioned components. The bus 502 can be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. The bus 502 can be divided into an address bus, a data bus, a control bus, etc. For convenience of representation, Figure 9 Only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0097] The memory 503 is used to store a computer program corresponding to the business data checking method of the above-mentioned embodiments of the present application, which is controlled and executed by the processor 501. The processor 501 is used to execute the computer program stored in the memory 503 to realize the content shown in the above-mentioned method embodiments.

[0098] The checking platform 500 includes but is not limited to mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Tablet Personal Computers), PMPs (Portable Multimedia Players), car terminals (such as car navigation terminals), etc. and fixed terminals such as digital TVs, desktop computers, etc. Figure 9 The checking platform 500 shown is only an example and should not limit the functions and use range of the embodiments of the present application.

[0099] The computer readable storage medium and the checking platform of the embodiments of the present application use the above-mentioned business data checking method to find online business dirty data or error logic in real time, find and timely inform technical support in the first time.

[0100] It is to be appreciated that the above description and the examples that follow are intended to be illustrative only and that changes can be made to the description, either functionally or chronologically, as well as changes being made concerning the order of implementation. The logic and / or steps represented in the flow diagrams and / or described herein can be considered as a sequence of executable instructions, and can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For purposes of this specification, a "computer-readable medium" can be any apparatus that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer-readable medium can be, for example, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus) or a propagation medium. More specific examples (a non-exhaustive list) of the computer-readable medium include the following: an electrical connection (electronic) having one or more wires, a portable computer diskette (magnetic), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber (optical), and a portable compact disc read-only memory (CDROM). Note that the computer-readable medium can even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, for example, via optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.

[0101] It is to be understood that the various parts of the application can be implemented by hardware, software, firmware or a combination thereof. In the above embodiments, a number of steps or methods can be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any of the following technologies known in the art, or a combination thereof, can be used: discrete logic circuitry having logic gates for implementing logic functions on data signals, application specific integrated circuits having appropriate combinational logic gates, programmable gate arrays (PGA), field programmable gate arrays (FPGA), etc.

[0102] In the description of the present specification, the description of the terms "one embodiment", "some embodiments", "an example", "a specific example", or "some examples" and the like means that the specific features, structures, materials or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. In the present specification, illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Also, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner.

[0103] In the description of the application, it should be understood that the orientation or positional relationship indicated by the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "upper", "lower", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", "clockwise", "counterclockwise", "axial", "radial", "circumferential" and the like is based on the orientation or positional relationship shown in the drawings, and is only for the convenience of describing the application and simplifying the description, and does not indicate or imply that the device or element referred to must have a particular orientation, be constructed and operated in a particular orientation, and therefore cannot be understood as a limitation on the application.

[0104] In addition, the terms "first", "second" are only for descriptive purposes and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the technical features indicated. Therefore, the features defined with "first", "second" can explicitly or implicitly include at least one of the features. In the description of the application, the meaning of "a plurality of" is at least two, such as two, three, etc., unless otherwise explicitly specified and limited.

[0105] In the present application, unless otherwise explicitly specified and limited, the terms "mounting", "connecting", "connecting", "fixing" and the like should be understood broadly, for example, it can be fixedly connected, or it can be detachably connected, or it can be integrated; it can be mechanically connected, or it can be electrically connected; it can be directly connected, or it can be indirectly connected through an intermediate medium; it can be the internal communication of two elements or the interaction relationship between two elements, unless otherwise explicitly limited. For those skilled in the art, the specific meaning of the above terms in the present application can be understood according to the specific circumstances.

[0106] In the present application, unless otherwise explicitly specified and limited, the first feature is "on" or "under" the second feature, which can be direct contact between the first and second features, or indirect contact between the first and second features through an intermediate medium. Moreover, the first feature "above", "above" and "above" the second feature can be directly above or obliquely above the first feature, or only indicate that the horizontal height of the first feature is higher than that of the second feature. The first feature "below", "below" and "below" the second feature can be directly below or obliquely below the first feature, or only indicate that the horizontal height of the first feature is less than that of the second feature.

[0107] Although the embodiments of the application have been shown and described above, it should be understood that the above embodiments are exemplary and cannot be understood as a limitation on the application, and those skilled in the art can make changes, modifications, replacements and variations to the above embodiments within the scope of the application.

Claims

1. A method for verifying business data, characterized in that, The method includes: The middleware corresponding to the business function modules of multiple applications can obtain target business data from the middleware corresponding to the target event when it detects a change in the target event corresponding to the business function module. The target business data is checked using pre-established business rules, and an alarm is triggered when the check result indicates data anomalies. The middleware for accessing the business function modules of multiple applications includes: determining the types of business function modules of the multiple applications; determining the middleware corresponding to each business function module according to the type of each business function module, and constructing a standardized subscription component according to the interface type of the middleware; and using the standardized subscription component to access the middleware corresponding to each business function module, wherein the middleware includes at least one of message queue, distributed search and analysis engine. Before verifying the target business data using pre-established business rules, the method further includes: The delay duration is determined based on the level of the business function module. After the duration following the change of the target event corresponding to the business function module reaches the delay duration, the target business data is verified using preset target business rules.

2. The business data verification method according to claim 1, characterized in that, The process of establishing the aforementioned business rules includes: Identify the business function modules of multiple applications; Based on the asset loss verification points of each of the aforementioned business function modules, business rules corresponding to each of the aforementioned business function modules are written, and the business rules are generated.

3. The business data verification method according to claim 1, characterized in that, The middleware also includes database logs and databases.

4. The business data verification method according to claim 1, characterized in that, The step of verifying the target business data using pre-established business rules includes: The target business rule is determined from the pre-established business rules based on the target event; The target business data is verified using the target business rules.

5. The business data verification method according to claim 1, characterized in that, The method further includes: The coverage rate of business function modules is determined based on the number of business function modules corresponding to the pre-established business rules.

6. A business data verification device, characterized in that, The device includes: The access module is used to access the middleware corresponding to the business function modules of multiple applications. When a change in the target event corresponding to the business function module is detected, the target business data is obtained from the middleware corresponding to the target event. The verification module is used to verify the target business data using pre-established business rules and to issue an alarm when the verification result is abnormal. The access module is used to determine the types of business function modules of the multiple applications; determine the middleware corresponding to each business function module according to the type of each business function module, and construct a standardized subscription component according to the interface type of the middleware; and use the standardized subscription component to access the middleware corresponding to each business function module, wherein the middleware includes at least one of message queue, distributed search and analysis engine. The verification module is used to determine the delay duration according to the level of the business function module before verifying the target business data using the pre-established business rules, and to verify the target business data using the preset target business rules after the duration after the target event corresponding to the business function module changes reaches the delay duration.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the business data verification method as described in any one of claims 1-5.

8. A verification platform, comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the computer program is executed by the processor, it implements the business data verification method as described in any one of claims 1-5.

Images