A front-end and back-end verification method and device based on metadata

Through the front-end and back-end verification method based on metadata, the problem of inconsistent performance in the front-end data verification process is solved, the accuracy and consistency of data verification are achieved, the development workload is reduced, and efficiency is improved.

CN112131100BActive Publication Date: 2024-11-08INSPUR GENERSOFT CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202010826908.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-08-17
Publication Date
2024-11-08
Estimated Expiration
2040-08-17

AI Technical Summary

Technical Problem

In systems with front-end and back-end separate architectures, inconsistent performance is likely to occur during the verification process of front-end and back-end data, resulting in verification errors and increased workload.

Method used

Through the front-end and back-end verification method based on metadata, data verification requests are received, front-end models and back-end entities are determined, front-end and back-end verification rules are determined based on these models, and corresponding interpreters are used to verify to ensure front-end and back-end Unify the verification rule interface and interpreter to avoid verification omissions.

Benefits of technology

It realizes the accuracy and consistency of front-end data verification, saves developers' workload and improves processing efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112131100B_ABST
    Figure CN112131100B_ABST
Patent Text Reader

Abstract

The present application discloses a front-end and back-end verification method and device based on metadata, which is used to solve the problems of inconsistent performance of the front-end and back-end during the front-end and back-end data verification process, which easily leads to verification errors. The method receives a data verification request, and determines the front-end model and back-end entity corresponding to the data verification request; determines the front-end verification rules corresponding to the front-end according to the front-end model and the back-end entity, and determines the corresponding front-end interpreter according to the type of the front-end verification rules, and performs front-end verification on the data; determines the back-end verification rules corresponding to the back-end according to the front-end model and the back-end entity, and determines the corresponding back-end interpreter according to the type of the back-end verification rules, and performs back-end verification on the data. This method unifies the data verification process of the front-end and back-end, which is conducive to providing the accuracy of data verification.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of front-end and back-end data verification, and in particular to a front-end and back-end verification method and device based on metadata. Background Art

[0002] In a system with a front-end and back-end separated architecture, in order to ensure the accuracy of the data, it is often necessary to verify the data separately on the front-end and back-end of the system.

[0003] Currently, during the system development process, developers usually develop the system front-end and back-end separately, using different codes and logics to perform front-end verification and back-end verification of data respectively.

[0004] However, this not only increases the workload of developers, but may also result in the same business rules of the data having different logical expressions on the front-end and back-end, resulting in inconsistent performance between the front-end and back-end, and causing problems such as omissions in the data verification process. Summary of the invention

[0005] The embodiments of the present application provide a metadata-based front-end and back-end verification method and device to solve the problem of inconsistent front-end and back-end performances during the front-end and back-end data verification process, which easily leads to verification errors.

[0006] The embodiment of the present application provides a front-end and back-end verification method based on metadata, including:

[0007] Receive a data verification request, and determine a front-end model and a back-end entity corresponding to the data verification request;

[0008] According to the front-end model and the back-end entity, determine the front-end verification rule corresponding to the front-end, and according to the type of the front-end verification rule, determine the corresponding front-end interpreter to perform front-end verification on the data;

[0009] According to the front-end model and the back-end entity, the back-end verification rules corresponding to the back-end are determined, and according to the type of the back-end verification rules, the corresponding back-end interpreter is determined to perform back-end verification on the data.

[0010] In one example, before determining the front-end verification rules corresponding to the front-end based on the front-end model and the back-end entity, the method also includes: initializing the front-end page; determining the verification rule set corresponding to the front-end model based on the front-end model corresponding to the front-end page; and storing the verification rule set in the cache.

[0011] In one example, before determining the front-end verification rules corresponding to the front-end according to the front-end model and the back-end entity, the method further includes: grouping the verification rule sets according to the back-end entity identifiers.

[0012] In one example, front-end verification is performed on data, including: constructing a verification rule context based on entity data corresponding to the front-end model and rule parameters corresponding to the determined front-end verification rules; and passing the verification rule context to the front-end interpreter to perform front-end verification.

[0013] In one example, performing front-end verification on data includes: calling a predefined verification rule base interface according to the configuration of the front-end interpreter; and performing front-end verification according to the verification rule base interface and the verification rule context.

[0014] In one example, the method further includes: during the front-end verification and the back-end verification, determining whether the verification of each verification rule passes respectively; if the verification fails, recording the entity data and the verification result.

[0015] In one example, the method further includes: determining whether verification of all verification rules has passed; if there are verification rules that have not passed the verification, rejecting the operation corresponding to the data verification request.

[0016] In one example, before performing back-end verification on the data, the method further includes: after determining that verification of all front-end verification rules has passed, performing back-end verification.

[0017] In one example, before determining the corresponding front-end interpreter according to the type of the front-end verification rule, the method further includes: determining a set of corresponding interpreters according to the types of all verification rules in the verification rule set; and storing the set of interpreters in a cache.

[0018] The embodiment of the present application provides a front-end and back-end verification device based on metadata, including:

[0019] A receiving module receives a data verification request and determines a front-end model and a back-end entity corresponding to the data verification request;

[0020] A front-end verification module determines the front-end verification rules corresponding to the front-end according to the front-end model and the back-end entity, and determines the corresponding front-end interpreter according to the type of the front-end verification rules to perform front-end verification on the data;

[0021] The backend verification module determines the backend verification rules corresponding to the backend according to the frontend model and the backend entity, and determines the corresponding backend interpreter according to the type of the backend verification rules to perform backend verification on the data.

[0022] The present application provides a metadata-based front-end and back-end verification method and device, which at least have the following beneficial effects:

[0023] By establishing a unified front-end and back-end verification rule interface, the front-end and back-end data verification processing process is unified. And by establishing a front-end interpreter and a back-end interpreter according to the type of verification rule, the interpretation of the verification rules described in the metadata is unified. This can ensure that the front-end and back-end perform the same business rules in a consistent manner, avoid problems such as verification omissions, and help provide data verification accuracy. At the same time, it can save the workload of developers and improve processing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0025] Figure 1 A flowchart of a front-end and back-end verification method based on metadata provided in an embodiment of the present application;

[0026] Figure 2 A schematic diagram of the structure of a front-end and back-end verification device based on metadata provided in an embodiment of the present application. DETAILED DESCRIPTION

[0027] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0028] Figure 1 The flowchart of the front-end and back-end verification method based on metadata provided in the embodiment of the present application specifically includes the following steps:

[0029] S101: receiving a data verification request, and determining a front-end model and a back-end entity corresponding to the data verification request.

[0030] In an embodiment of the present application, the server can determine the pre-defined interface standards that need to be followed when performing front-end and back-end verification of data, including front-end model and verification rule mapping configuration, verification rule interpreter configuration, verification rule context, verification rule base interface, verification rule type, etc.

[0031] Specifically, the client can initiate a data verification request to the server based on the user's operation to request the server to perform the corresponding operation. Then, the server can receive the data verification request from the client and determine the front-end model corresponding to the front end of the system and the back-end entity corresponding to the back end involved in the data verification process. The data verification request may include the front-end model identifier and the back-end entity identifier.

[0032] It should be noted that in the system, one front-end model may correspond to multiple back-end entities. A data verification process usually involves one front-end model and more than one back-end entity.

[0033] S102: Determine the front-end verification rules corresponding to the front-end according to the front-end model and the back-end entity, and determine the corresponding front-end interpreter according to the type of the front-end verification rules to perform front-end verification on the data.

[0034] In the embodiment of the present application, the server can determine the corresponding front-end verification rule when performing verification at the front end according to the front-end model identifier and the back-end entity identifier in the data verification request. Afterwards, the server can determine the front-end interpreter corresponding to the corresponding type according to the type of the obtained front-end verification rule, and use the front-end interpreter to perform front-end verification on the data.

[0035] The specific steps include:

[0036] First, the server can call the "Get Front-end Model Verification Rules" operation in the "Front-end Model and Verification Rule Mapping Configuration" service pre-defined in the interface standard according to the front-end model identifier to obtain the set of all verification rules corresponding to the front-end model.

[0037] "Front-end model and verification rule mapping configuration" is used to define the mapping relationship configuration between the front-end model and the verification rule, which may include attributes such as identifier, front-end model identifier, entity identifier, and verification rule identifier. Among them, "identifier" is used to uniquely identify the mapping relationship between a front-end model and a verification rule; "front-end model identifier" is used to indicate the front-end model included in the mapping relationship; "entity identifier" is used to indicate the identifier of the entity corresponding to the current mapping relationship configuration; "verification rule identifier" is used to uniquely identify a verification rule, which is applied to the current front-end model.

[0038] The server can group the set of all verification rules corresponding to the obtained front-end model according to the entity identifier, and store the verification rules corresponding to the corresponding entity identifier in each group. Afterwards, the server can determine the verification rule matching the back-end entity identifier from the above set according to the back-end entity identifier corresponding to the data verification request.

[0039] It can be seen that the verification rules finally determined are all verification rules corresponding to the data verification request determined based on the front-end model identifier and the back-end entity identifier.

[0040] In one embodiment, during the process of initializing the front-end page, after obtaining the set of verification rules corresponding to the front-end model, the server can store the set of verification rules in the cache. Then, the server can directly call the set of verification rules from the cache to speed up the front-end and back-end verification process and improve the verification efficiency.

[0041] Second, the server can call the "get front-end verification rules" operation in the "verification rule configuration" service pre-defined in the interface standard, and determine the front-end verification rules applied to the front-end from all the verification rules determined in the first step.

[0042] "Verification rule configuration" is used to record metadata information of verification rules, including identification, entity identification, entity attributes, verification rule type identification, first rule parameter value, second rule parameter value, whether the front-end is applicable, whether the back-end is applicable, prompt information, sequence number and other attributes.

[0043] Among them, "identifier" is used to uniquely identify a verification rule; "entity identifier" is used to indicate the identifier of the entity to which the current verification rule applies; "entity attribute" is used to indicate the attribute of the above entity, that is, the attribute targeted by the current verification rule; "verification rule type identifier" is used to indicate the verification rule type to which the current verification rule belongs; "first rule parameter value" is used to indicate the value of a specific parameter of the verification rule; "second rule parameter value" is used to indicate the value of another specific parameter of the verification rule; for the same verification rule type, different entity attributes correspond to different parameter values; "whether front-end applicable" is used to indicate whether the current verification rule is applicable to front-end verification. If so, it indicates that the current verification rule is a front-end verification rule; "whether back-end applicable" is used to indicate whether the current verification rule is applicable to back-end verification. If so, it indicates that the current verification rule is a back-end verification rule; "prompt information" is used to indicate the prompt information displayed to the user when the rule is violated; "sequence number" is used to indicate the order in which the current verification rules take effect.

[0044] Third, the server may traverse the obtained front-end verification rules to determine the type of the corresponding front-end verification rules.

[0045] The verification rule type is used to verify the type of the rule. Different types of verification rules need to be processed by different rule interpreters. The verification rule type may include verification rule type identifier, verification rule code, verification rule type name, description and other attributes. Among them, "verification rule type identifier" is used to uniquely identify a verification rule type; "verification rule code" is used to indicate the code of the verification rule; "verification rule type name" is used to indicate the name of the verification rule type; "description" is used to briefly describe the purpose and characteristics of the verification rule type.

[0046] Fourth, the server can call the "get front-end interpreter configuration" operation in the "verification rule interpreter configuration" service pre-defined in the interface standard, and determine the corresponding front-end interpreter according to the front-end verification rule type.

[0047] "Verification rule interpreter configuration" is used to define the configuration relationship between the verification rule type and the front-end interpreter and back-end interpreter. One verification rule type is configured with a front-end interpreter and a back-end interpreter, which are used for the front-end interpretation work and back-end interpretation work of the corresponding verification rule.

[0048] The verification rule interpreter configuration may include attributes such as identification, verification rule type identification, front-end interpreter configuration, back-end interpreter configuration, and number of rule parameters. Among them, "identification" is used to uniquely identify a verification rule interpreter configuration; "verification rule type identification" is used to indicate the verification rule type included in the current configuration; "front-end interpreter configuration" is used to indicate the configuration of the front-end interpreter corresponding to the above verification rule type, including the full name of the implementation class of the front-end interpreter; "back-end interpreter configuration" is used to indicate the configuration of the back-end interpreter corresponding to the above verification rule type, including the full name of the implementation class of the back-end interpreter; "number of rule parameters" is used to indicate the number of parameters required for the verification rule of this type.

[0049] In one embodiment, after determining all the verification rules (i.e., verification rule set) corresponding to the front-end model, the server can determine the corresponding interpreter set according to the types of all the verification rules, including all corresponding front-end interpreters and back-end interpreters. Afterwards, the server can store the determined interpreter set in the cache so that the interpreter set can be directly called from the cache later, thereby speeding up the data verification process and improving the verification efficiency.

[0050] Fifth, the server can load the front-end interpreter program according to the determined configuration description of the front-end interpreter to implement the call to the verification rule base interface. The server can perform front-end verification through the verification operation in the verification rule base interface. If true is returned, the verification passes, otherwise the verification fails.

[0051] In one embodiment, when the server performs front-end verification on data, it can construct a verification rule context according to the entity data corresponding to the front-end model and the rule parameters corresponding to the determined front-end verification rules. Afterwards, the server can pass the verification rule context to the corresponding front-end interpreter, which calls the verification rule base interface and performs front-end verification according to the verification rule context.

[0052] The validation rule context is used to record the context information required for validation, including properties such as the object to be validated, field, and validation rule parameter list. Among them, "object to be validated" refers to the object waiting to be validated. In the front-end validation process, the object to be validated is the front-end model object data, and in the back-end validation process, the object to be validated is the back-end entity object data; "field" refers to the specific field where the validation rule is implemented. If the validation rule is not implemented for a specific field, the attribute value is empty; "validation rule parameter list" refers to the parameter list involved in the validation rule.

[0053] S103: Determine the backend verification rules corresponding to the backend according to the frontend model and the backend entity, and determine the corresponding backend interpreter according to the type of the backend verification rule to perform backend verification on the data.

[0054] In the embodiment of the present application, the server can determine the corresponding backend verification rules when performing verification at the backend according to the frontend model identifier and the backend entity identifier in the data verification request. Afterwards, the server can determine the backend interpreter corresponding to the corresponding type according to the type of the obtained backend verification rule, and use the backend interpreter to perform backend verification on the data.

[0055] The specific steps include:

[0056] First, the server may call the "get backend verification rules" operation in the "verification rule configuration" service predefined in the interface standard, and determine the frontend verification rules applied to the backend from the verification rule set determined in S102.

[0057] Second, the server may traverse the obtained backend verification rules to determine the type of the corresponding backend verification rules.

[0058] Third, the server can call the "get backend interpreter configuration" operation in the "verification rule interpreter configuration" service pre-defined in the interface standard, and determine the corresponding backend interpreter according to the backend verification rule type.

[0059] In one embodiment, the server may first determine whether a predetermined set of interpreters exists in the cache. If so, it may be directly called. If not, the server may perform corresponding determination work.

[0060] Fourth, the server can load the backend interpreter program according to the determined configuration description of the backend interpreter to implement the call to the verification rule base interface. The server can perform backend verification through the verification operation in the verification rule base interface. If true is returned, the verification is passed, otherwise the verification fails.

[0061] In one embodiment, when the server performs backend verification on data, it can construct a verification rule context according to the entity data corresponding to the backend entity and the rule parameters corresponding to the determined backend verification rule. Afterwards, the server can pass the verification rule context to the corresponding backend interpreter, which calls the verification rule base interface and performs backend verification according to the verification rule context.

[0062] It should be noted that in the embodiment of the present application, the front-end verification process described in S102 is basically similar to the back-end verification process described in S103. Therefore, for the parts not described in detail in S103, refer to the relevant description in S102.

[0063] In the embodiment of the present application, by establishing a unified verification rule interface between the front-end and the back-end, the processing process of data verification by the front-end and the back-end is unified. And by establishing a front-end interpreter and a back-end interpreter according to the type of verification rule, the interpretation of the verification rules described by the metadata is unified. This can ensure that the front-end and the back-end are consistent in their performance of the same business rule, avoid problems such as verification omissions, and at the same time save the workload of developers and improve development efficiency.

[0064] In one embodiment, during the process of front-end verification and back-end verification, the server needs to perform verification according to each verification rule to determine whether each verification rule has passed the verification. If the verification passes, the server can continue to verify the next verification rule. If the verification fails, the server can record the corresponding entity data and the verification results through the violation collector to form a violation collection record.

[0065] The violation collection record is used to record information that violates the verification rules, that is, information that failed the verification, including verification rule name, verification entity, verification field, prompt information and other attributes. Among them, "verification rule name" is used to indicate the verification rule name that failed the verification; "verification entity" is used to indicate the related entity of the violation (i.e. verification failed); "verification field" is used to indicate the related field of the violation; "prompt information" is used to indicate that the verification failed is a prompt information that needs to be displayed to the user.

[0066] In one embodiment, during the process of front-end verification or back-end verification, the server needs to determine whether all verification rules that need to be verified have passed the verification. Only when all verification rules corresponding to the front-end are verified and passed, it means that the front-end verification has passed. Similarly, only when all verification rules corresponding to the back-end are verified and passed, it means that the back-end verification has passed. If there are any verification rules that have not passed the verification, the server can determine that the data verification request does not comply with the verification rules and can reject the operation corresponding to the data verification request.

[0067] In one embodiment, the server needs to make sure that all front-end verification rules have passed the verification. After the front-end verification is completed, the subsequent back-end verification operation can be performed. If any front-end verification rule fails in the front-end verification, the back-end verification cannot be performed.

[0068] For ease of understanding, this application takes the front-end and back-end verification of a sales order as an example for explanation.

[0069] The front-end verification process includes the following steps:

[0070] First, when initializing the front-end page, the server can call the "Get Front-end Model Verification Rules" operation in the "Front-end Model and Verification Rule Mapping Configuration" service according to the front-end model identifier to obtain the set of all verification rules corresponding to the front-end model.

[0071] As shown in Table 1, all the validation rules corresponding to the sales order entity are shown. The first row represents the attribute, and the second to fourth rows represent the corresponding attribute values. It can be seen that the validation rule set corresponding to the front-end model of the sales order entity includes 3 validation rules.

[0072] Table 1

[0073]

[0074] Second, the server can call the "get front-end verification rules" operation in the "verification rule configuration" service pre-defined in the interface standard, and determine the front-end verification rules applied to the front-end from the verification rule set determined in the first step.

[0075] It can be seen that the two verification rules marked as 1 and 3 in Table 1 are applicable to the front-end verification.

[0076] Third, the server may traverse the obtained front-end verification rules to determine the type of the corresponding front-end verification rules.

[0077] Table 2 shows the verification rule type information table corresponding to the determined verification rule. In the table, the first row represents the attribute, and the second and third rows represent the corresponding attribute values. It can be seen that the verification rule identified as 1 and the verification rule identified as 3 in the second step are of different types.

[0078] Table 2

[0079]

[0080]

[0081] Fourth, the server can call the "get front-end interpreter configuration" operation in the "verification rule interpreter configuration" service pre-defined in the interface standard, and determine the corresponding front-end interpreter according to the front-end verification rule type.

[0082] As shown in Table 3 and Table 4, they are the interpreter configurations corresponding to two different types of verification rules. The first column of Table 3 and Table 4 represents attributes, and the second column represents the corresponding attribute values.

[0083] Table 3

[0084] property value Logo 1 Verification rule type identifier Range Front-end interpreter configuration valid.RangeInterpreter,RangeInterpreter.js Backend interpreter configuration com.demo.erp.valid.RangeRule Number of rule parameters 2

[0085] Table 4

[0086]

[0087]

[0088] It can be seen that the front-end interpreter configuration of the verification rule marked as 1 in the first step is valid.RangeInterpreter, RangeInterpreter.js, and the front-end interpreter configuration of the verification rule marked as 3 is valid.NotEmptyInterpreter, NotEmptyInterpreter.js.

[0089] Fifth, the server can construct the verification rule context according to the entity data, the fields of the current rule, and the parameter values. In addition, the server loads the front-end interpreter program according to the determined configuration description of the front-end interpreter, and passes the verification rule context to the front-end interpreter program to implement the call to the verification rule base interface. The server can perform front-end verification through the verification operation in the verification rule base interface. If true is returned, the verification passes, otherwise the verification fails.

[0090] Therefore, the server can follow the above steps and perform verification according to all the front-end verification rules in turn. If all the rules are verified, the data can be submitted to the back-end for back-end verification.

[0091] It should be noted that since the front-end verification process is basically the same as the back-end verification process, this application will not go into details about the back-end verification process. For details, please refer to the steps of the front-end verification process and the related description of S103 above.

[0092] After the server performs backend verification, if the verification passes, the entity data can be persisted into the database, otherwise the data verification request can be rejected.

[0093] The above is a front-end and back-end verification method based on metadata provided by the embodiment of the present application. Based on the same inventive idea, the embodiment of the present application also provides a corresponding front-end and back-end verification device based on metadata, such as Figure 2 shown.

[0094] Figure 2 The schematic diagram of the structure of the front-end and back-end verification device based on metadata provided in the embodiment of the present application specifically includes:

[0095] The receiving module 201 receives a data verification request and determines a front-end model and a back-end entity corresponding to the data verification request;

[0096] The front-end verification module 202 determines the front-end verification rules corresponding to the front-end according to the front-end model and the back-end entity, and determines the corresponding front-end interpreter according to the type of the front-end verification rules to perform front-end verification on the data;

[0097] The backend verification module 203 determines the backend verification rules corresponding to the backend according to the frontend model and the backend entity, and determines the corresponding backend interpreter according to the type of the backend verification rules to perform backend verification on the data.

[0098] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0099] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0100] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A front-end and back-end verification method based on metadata, characterized in that: include: Receive a data verification request, and determine a front-end model and a back-end entity corresponding to the data verification request; According to the front-end model and the back-end entity, determine the front-end verification rule corresponding to the front-end, and according to the type of the front-end verification rule, determine the corresponding front-end interpreter to perform front-end verification on the data; Determine the backend verification rules corresponding to the backend according to the frontend model and the backend entity, and determine the corresponding backend interpreter according to the type of the backend verification rules to perform backend verification on the data; Perform front-end verification of data, including: Constructing a verification rule context according to the entity data corresponding to the front-end model and the rule parameters corresponding to the determined front-end verification rule; Passing the verification rule context to the front-end interpreter for front-end verification; According to the configuration of the front-end interpreter, a predefined verification rule base interface is called; A front-end verification is performed according to the verification rule base interface and the verification rule context.

2. The method according to claim 1, characterized in that Before determining the front-end verification rule corresponding to the front-end according to the front-end model and the back-end entity, the method further includes: Initialize the front-end page; According to the front-end model corresponding to the front-end page, determine the verification rule set corresponding to the front-end model; The validation rule set is stored in a cache.

3. The method according to claim 2, characterized in that Before determining the front-end verification rule corresponding to the front-end according to the front-end model and the back-end entity, the method further includes: The verification rule sets are grouped according to the backend entity identifiers.

4. The method according to claim 1, characterized in that The method further comprises: During the front-end verification and back-end verification process, determine whether each verification rule has passed the verification; If the verification fails, the entity data and the verification result are recorded.

5. The method according to claim 4, characterized in that The method further comprises: Determine whether all validation rules have passed validation; If there are verification rules that fail the verification, the operation corresponding to the data verification request is rejected.

6. The method according to claim 4, characterized in that Before performing back-end verification on the data, the method further includes: After confirming that all front-end verification rules have passed, perform back-end verification.

7. The method according to claim 2, characterized in that Before determining the corresponding front-end interpreter according to the type of the front-end verification rule, the method further includes: Determine a set of corresponding interpreters according to the types of all verification rules in the verification rule set; The set of interpreters is stored in a cache.

8. A front-end and back-end verification device based on metadata, characterized in that: include: A receiving module receives a data verification request and determines a front-end model and a back-end entity corresponding to the data verification request; A front-end verification module determines the front-end verification rules corresponding to the front-end according to the front-end model and the back-end entity, and determines the corresponding front-end interpreter according to the type of the front-end verification rules to perform front-end verification on the data; The backend verification module determines the backend verification rules corresponding to the backend according to the frontend model and the backend entity, and determines the corresponding backend interpreter according to the type of the backend verification rules to perform backend verification on the data.