CN110633160A - Interface calling method and device, computer equipment and storage medium - Google Patents
Interface calling method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN110633160A CN110633160A CN201910779102.0A CN201910779102A CN110633160A CN 110633160 A CN110633160 A CN 110633160A CN 201910779102 A CN201910779102 A CN 201910779102A CN 110633160 A CN110633160 A CN 110633160A
- Authority
- CN
- China
- Prior art keywords
- interface
- program
- check
- verification
- logic
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Software Systems (AREA)
- Computational Linguistics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application relates to an interface calling method, an interface calling device, computer equipment and a storage medium. The method comprises the following steps: receiving an interface calling request, wherein the interface calling request carries an interface identifier of an interface to be called; judging whether the interface to be called has a check identifier or not through an interface interception program according to the interface identifier; when the check identifier exists, acquiring a check logic corresponding to the interface calling request through an interface interception program according to the interface identifier; verifying the interface calling request by adopting a verification logic through a verification program to obtain a verification result; and generating an interface calling result according to the verification result, and sending the interface calling result to the terminal. The method can ensure the stability of the service program code.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to an interface calling method and apparatus, a computer device, and a storage medium.
Background
With the development of computer technology, more and more services can be handled through a computer, and when different services are handled through the computer, in order to ensure the security and accuracy of the service handling, when a service interface corresponding to a server is called, different checks are required to be performed on the interface.
Conventionally, for different services, different check logic codes need to be configured in a service program corresponding to the service, so that the service program is strongly coupled with the different check logic codes, and when the check logic codes are modified, the service program also needs to be modified, which easily causes the instability of the service program.
Disclosure of Invention
In view of the foregoing, it is desirable to provide an interface calling method, an interface calling apparatus, a computer device, and a storage medium, which can improve program stability.
An interface call method, the method comprising:
receiving an interface calling request, wherein the interface calling request carries an interface identifier of an interface to be called;
judging whether the interface to be called has a check identifier or not through an interface interception program according to the interface identifier;
when a check identifier exists, acquiring a check logic corresponding to the interface calling request according to the interface identifier through the interface interception program;
verifying the interface calling request by adopting the verification logic through a verification program to obtain a verification result;
and generating an interface calling result according to the checking result.
In one embodiment, when there is a check identifier, acquiring, by the interface interception program according to the interface identifier, a check logic corresponding to the interface call request, includes:
when the check identification exists, inquiring whether a local cache library has the check logic corresponding to the interface identification through the interface interception program;
when the local cache library does not store the verification logic, sending an acquisition request for acquiring the verification logic to a rule server through the interface interception program;
and receiving the check logic which is returned by the rule server and corresponds to the acquisition request.
In one embodiment, after sending the obtaining request for obtaining the checking logic to the rule server through the interface interception program, the method includes:
when the check logic corresponding to the acquisition request returned by the rule server is not received, inquiring whether a service program contains a check function or not through the interface interception program;
and when the service program contains the check function, the interface calling request is sent to the service program through the interface interception program.
In an embodiment, the verifying, by the verifying program, the verifying, by using the verifying logic, the interface call request to obtain a verification result, includes:
loading the check logic and obtaining a loading result through a check program;
when the loading result is that the loading is successful, inquiring a service identifier corresponding to the interface calling request through the verification program;
and verifying the interface calling request by adopting the verification logic according to the service identifier through the verification program to obtain a verification result.
In one embodiment, the generating an interface invocation result according to the verification result includes:
sending the checking result to the interface interception program through the checking program;
inquiring the verification result through the interface interception program, and when the verification result is that the verification is passed, sending the interface calling request to a service program through the interface interception program;
and generating interface response information through the service program, and taking the interface response information as an interface calling result. In one embodiment, after querying the check result through the interface interceptor, the method includes:
when the verification result is that the verification fails, inquiring abnormal reason codes according to the verification result which fails to pass;
and sending the check result that the interface check fails and the abnormal reason code to the terminal through the interface interception program.
In one embodiment, the method further comprises:
receiving change prompt information sent by a rule server, wherein the change prompt information carries a change logic identifier;
generating a change inquiry request according to the change logic identifier, and sending the change inquiry request to the rule server;
and receiving the change logic corresponding to the change inquiry request returned by the rule server, and storing the change logic into a local cache library.
An interface invocation apparatus, said apparatus comprising:
the device comprises a request receiving module, a request sending module and a request receiving module, wherein the request receiving module is used for receiving an interface calling request, and the interface calling request carries an interface identifier of an interface to be called;
the query module is used for judging whether the interface to be called has a check identifier or not through the interface interception program according to the interface identifier;
the acquisition module is used for acquiring a check logic corresponding to the interface calling request according to the interface identifier through the interface interception program when the check identifier exists;
the verification module is used for verifying the interface calling request by adopting the verification logic through a verification program to obtain a verification result;
and the generating module is used for generating an interface calling result according to the checking result.
A computer device comprising a memory and a processor, the memory storing a computer program, the processor implementing the following steps when executing the computer program:
receiving an interface calling request, wherein the interface calling request carries an interface identifier of an interface to be called;
judging whether the interface to be called has a check identifier or not through an interface interception program according to the interface identifier;
when a check identifier exists, acquiring a check logic corresponding to the interface calling request according to the interface identifier through the interface interception program;
verifying the interface calling request by adopting the verification logic through a verification program to obtain a verification result;
and generating an interface calling result according to the checking result.
A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of:
receiving an interface calling request, wherein the interface calling request carries an interface identifier of an interface to be called;
judging whether the interface to be called has a check identifier or not through an interface interception program according to the interface identifier;
when a check identifier exists, acquiring a check logic corresponding to the interface calling request according to the interface identifier through the interface interception program;
verifying the interface calling request by adopting the verification logic through a verification program to obtain a verification result;
and generating an interface calling result according to the checking result.
The interface calling method, the device, the computer equipment and the storage medium receive the interface calling request, check and response are not directly carried out on the interface calling request through the service program, but whether the interface to be called has a check identifier or not is inquired through the interface interception program according to the interface identifier, when the check identifier exists, check logic corresponding to the interface calling request is obtained through the interface interception program according to the interface identifier, the interface calling request is checked through the check program by adopting the check logic to obtain a check result, the interface calling result is generated according to the check result, and the check logic and the service program can be decoupled, so that the stability of the service program code is ensured.
Drawings
FIG. 1 is a diagram of an application scenario in which a method is invoked by an interface in one embodiment;
FIG. 2 is a flow diagram illustrating a method for interface invocation in one embodiment;
FIG. 3 is a schematic flow chart of the check logic acquisition step in one embodiment;
FIG. 4 is a flowchart illustrating the verification logic altering step in one embodiment;
FIG. 5 is a flowchart illustrating an interface call method according to another embodiment;
FIG. 6 is a block diagram showing the structure of an interface calling apparatus according to one embodiment;
FIG. 7 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The interface calling method provided by the application can be applied to the application environment shown in fig. 1. Wherein the terminal 102, the service server 104 and the rule server 106 communicate over a network. The service server 104 receives an interface calling request sent by the terminal 102, the interface calling request carries an interface identifier of an interface to be called, the service server 104 judges whether the interface to be called has a check identifier through an interface interception program according to the interface identifier, when the check identifier exists, the service server 104 obtains a check logic corresponding to the interface calling request from the rule server 106 through the interface interception program according to the check identifier, then the service server 104 checks the interface calling request through the check program by adopting the check logic to obtain a check result, the service server 104 generates an interface calling result according to the check result, and sends the interface calling result to the terminal 102. The terminal 102 may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, the service server 104 may be implemented by an independent server or a server cluster formed by a plurality of servers, and the rule server 106 may be implemented by an independent server or a server cluster formed by a plurality of servers.
In the application, the check logic built in the service server is arranged on the external rule server, and the service program in the service server is separated from the check logic, so that the code readability of the service program can be improved. In addition, because only the service program is stored on the service server, the service program is more flexible to update or change. Finally, because the check logic is decoupled from the service program, the service program only needs to be independently modified when being changed, and therefore the cost of changing the service program can be reduced.
In an embodiment, as shown in fig. 2, an interface calling method is provided, which is described by taking the application of the method to the service server in fig. 1 as an example, and includes the following steps:
s202: and receiving an interface calling request, wherein the interface calling request carries the interface identifier of the interface to be called.
Specifically, the interface call request refers to a request sent by the terminal to the server to call a different interface on the server. The interface identifier refers to an interface identifier corresponding to an interface of the service server to be called by the terminal, and the interface identifier may be a pre-configured interface address, an interface name, an interface number, or the like.
Specifically, in the process of implementing a service, the terminal needs to call different interfaces in the server so as to implement different service flows, and therefore, the terminal can send an interface call request to the service server according to the configured interface identifier, the service server receives the interface call request sent by the terminal, and the interface call request carries different call parameters, such as the interface identifier corresponding to the called interface, and data parameters for requesting to obtain different response data, and the like. The service server can receive an interface calling request sent by the terminal through a preset interface interception program.
For example, a vehicle selling application program is installed in the terminal, so that the terminal installed with the vehicle selling application program can send an interface calling request for calling an order creating interface to a service server corresponding to the vehicle selling application program, and thus, order information can be stored in the service server through the order creating interface.
S204: and judging whether the interface to be called has a check identifier or not by an interface interception program according to the interface identifier.
Specifically, the interface interception program is a program segment that is preset in the service server and used for receiving an interface call request sent by the terminal and intercepting a response code and returning response information. The check identifier is a flag carried by the interface to be called and used for checking parameters included in the received interface call request, and may be that when the interface to be called carries the check identifier, different parameters included in the received interface call request sent by the terminal need to be checked.
Specifically, when the service server receives an interface calling request, the service server queries an interface identifier carried by the interface calling request through a preset interface interception program, queries an interface to be called according to the interface identifier, and queries interface description information corresponding to the interface to be called by the interface interception program, so as to determine whether a check identifier exists according to different information contained in the interface description information, that is, determine whether the interface description information contains a flag indicating that the interface needs to perform parameter check on the interface calling request. For example, when the service server receives an interface call request for calling an order creation interface sent by the terminal, the service server queries the corresponding interface as the order creation interface according to a call parameter included in the interface call request, and therefore, the service server obtains interface description information corresponding to the order creation interface through an interface interception program, so as to determine whether a check mark exists in the interface description information, that is, whether the order creation interface needs to start a parameter check process.
S206: and when the check identifier exists, acquiring the check logic corresponding to the interface calling request through the interface interception program according to the interface identifier.
Specifically, the check logic refers to a check policy that can check the interface call request, and the check logic may be a script file, so that the script file is received by the check program, and the script file is executed to complete the check of the interface call request.
Specifically, different check logics do not need to be configured in different service main codes corresponding to the service server, but different check logics are extracted and stored in the rule server, that is, when the service server receives an interface calling request, according to an interface identifier of an interface to be called carried by the interface calling request, when the interface to be called is judged to carry the check identifier, that is, the service server judges that the interface to be called starts a check flow needing parameter check on the interface calling request, the service server queries the check logic corresponding to the interface identifier from the rule server through an interface interception program, so that the service server can check the interface calling request through the obtained check logics. It should be noted that the rule server is a server storing different verification logics that can verify different interface call requests.
For example, the service server receives a call order creating interface, if the order creating interface responds, the interface call request needs to be verified first, then the interface interception program matches the interface identifier with different identifiers to be matched stored in the rule server according to the interface identifier, and when the matching is successful, the verification logic corresponding to the successfully matched identifier is used as the verification logic corresponding to the order creating interface.
S208: and verifying the interface calling request by adopting a verification logic through a verification program to obtain a verification result.
Specifically, the verification program refers to a code that is preset in the service server and can execute a verification logic to complete verification of the interface call request, and the verification program may be a code that is separated from the service program in the service server and can run different loaded script files, for example, the verification program may be a rule engine or the like. In a specific implementation, when the verification logic is different script files, the verification program can receive the script file sent by the interface interception program and run the script file, so as to verify the interface call request.
Specifically, when the service server receives an interface calling request, the service server inquires that the interface to be called carries a verification identifier through an interface interception program, then obtains a verification logic corresponding to the interface calling request from the rule server through the interface interception program, and sends the obtained script file to the verification program through the interface interception program, so that the verification program can run the verification logic, and different calling parameters contained in the interface calling request are verified through running the verification logic to obtain a verification result. The service server can obtain the verification logic which can be a script file through the interface interception program, the obtained script file is sent to the verification program through the interface interception program, the verification program operates the script file according to the received script file, and the call parameters contained in the interface call request are verified to obtain the verification result.
For example, when the service server receives an interface call request as a call order creation interface, and the called order creation interface carries a check identifier, the interface interception program acquires the check logic from the rule server, the acquired check logic may be a script file, and then the interface interception program sends the script file to the check program, and the check program runs the script file, for example, a call parameter is extracted from the interface call request, for example, the call parameter is a total amount of the order, a preferential amount of money, an actual amount of money, and the like, and further, according to the running script file, queries whether the call parameter included in the interface call request meets a condition for calling the order creation interface, so that a check result is obtained through the check program.
S210: and generating an interface calling result according to the checking result.
Specifically, the interface calling result refers to a final result of the terminal calling different interfaces of the service server, and may be that the interface calling result is a call failure or a call success. Specifically, when the service server verifies the interface call request through the verification program and obtains a verification result, the verification program sends the verification result to the interface interception program. Further, the interface interception program receives the verification result and sends the verification result to the terminal.
In the interface calling method, the check logic does not need to be configured independently in the service program, but the corresponding check logic is stored in the rule server, so that the decoupling of the check logic and the service program is ensured, the readability of the service program is high, the change along with the change of the check logic is not needed, the stability is enhanced, when the service server receives an interface calling request sent by the terminal, the check identifier of the interface to be called can be inquired through the interface interception program according to the interface identifier, and when the check identifier is inquired, the interface calling request can be required to be checked, so that the safety of interface calling is ensured.
In an embodiment, please refer to fig. 3, which provides a schematic flow chart of a check logic obtaining step, where the check logic obtaining step is that when a check identifier exists, the interface interception program obtains, according to the interface identifier, a check logic corresponding to the interface call request, and the method includes: when the check identification exists, inquiring whether a check logic corresponding to the interface identification exists in the local cache library or not through an interface interception program; when the local cache library does not store the verification logic, an acquisition request for acquiring the verification logic is sent to the rule server through the interface interception program; and receiving the check logic which is returned by the rule server and corresponds to the acquisition request.
Specifically, the local cache library is a database which is arranged in the service server and stores the check logic acquired from the rule server. Specifically, when the service server queries that the interface to be called carries the check identifier through the interface interception program, the check logic acquired from the rule server through the interface interception program is stored in the local cache library, so that the interface interception program matches the check identifier corresponding to the stored logic stored in the local cache library according to the interface identifier, when the matching is successful, the check logic is stored in the local cache library, the service server directly acquires the check logic from the local cache library through the interface interception program, sends the acquired check logic to the check program through the interface interception program, and operates the check logic through the check program to check the interface calling request.
In addition, when the program is intercepted through the interface and the checking logic is not inquired from the local cache library, an acquisition request for acquiring the check logic is sent to the rule server through the interface interception program, and the acquisition request carries the corresponding interface identification, when the rule server receives the acquisition request, then according to the interface identification carried by the acquisition request, matching with the interface identification corresponding to the pre-stored logic to be matched, when the matching is successful, the logic to be matched corresponding to the successfully matched interface identifier is sent to the service server as the check logic, and then the service server receives the check logic returned by the rule server through the interface interception program, the interface interception program sends the check logic received from the rule server to the check program so that the check program runs the check logic to complete the check on the interface call request.
In this embodiment, when receiving the interface call request, the service server may first query, through the interface interception program, whether the local cache library stores the check logic, without directly interacting with the rule server, so as to improve the check logic obtaining efficiency, and reduce the loads of the service server and the rule server.
In one embodiment, with continued reference to fig. 3, after sending the request for obtaining the verification logic to the rule server via the interface intercept program, the method includes: when the check logic corresponding to the acquisition request returned by the rule server is not received, inquiring whether the service program contains a check function or not through an interface interception program; and when the service program contains the check function, the interface interception program sends the interface calling request to the service program.
Specifically, the service program refers to a code that can implement different service logics in the service server, that is, a main code that implements different services. Specifically, when the rule server obtains the check logic according to the obtaining request and does not obtain the check logic in the rule server, the check logic corresponding to the interface is not decoupled from the service program, or the interface is not configured with the check logic, so that the service server queries whether the service program contains the check function through the interface interception program, wherein, whether the service program contains the check function through the interface interception program can be that the service server prestores function names of different check functions, the interface interception program matches the function names contained in the service program through different function names, when the matching is successful, the service program contains the check function, therefore, when the service program is queried through the interface interception program and contains the check function, the interface interception program directly sends the interface calling request to the service program, therefore, the service program directly checks the interface calling request according to the interface calling request, returns the interface calling result to the terminal according to the checking result and the interface calling request, and the service server can send decoupling prompt information to the rule server to prompt that the service program still contains the checking logic.
In addition, when the service program is not inquired in the interface interception program to contain a check function, that is, the interface to be called needs to be checked, but the service server does not inquire a check logic, in order to ensure the interface calling security, the prompt message of interface calling failure can be directly returned to the terminal through the interface interception program, and the service server can send the configuration information of the configuration check logic to the rule server, that is, the rule server displays the corresponding configuration information, so as to prompt the operation and maintenance personnel to add the check logic corresponding to the interface calling request, or the current interface does not need to check the interface calling request, and then the check identifier carried by the interface to be called is deleted.
In this embodiment, when the service server does not receive the check logic returned by the rule server, the service server may query, through the interface interception program, whether a check function is configured in the service program, and when the check function is included, the check may be directly performed through the service program, so that the security of interface call may be ensured.
In one embodiment, the verifying the interface call request by using a verifying logic through a verifying program to obtain a verification result includes: loading the check logic and obtaining a loading result through a check program; when the loading result is that the loading is successful, calling a service identifier corresponding to the request through a checking program query interface; and verifying the interface calling request by using a verification logic according to the service identifier through a verification program to obtain a verification result.
Specifically, the service identifier refers to an identifier of the service, such as a service name, a service code, and the like. When the interface interception program inquires the check logic, the check logic is sent to the check program, the check logic can be called through the check program, grammar check is conducted on the check logic, when the check program successfully calls the check logic and grammar check passes, the check logic can be operated through the check program, namely the check logic is successfully loaded through the check program, the call parameter in the interface call request is inquired through the check program, the service identification corresponding to the call request is inquired according to the call parameter, when the service identification is inquired through the check program, the corresponding check flow can be selected from the check logic according to the service identification, and therefore the corresponding check flow is executed through the check program, check on the interface call request is completed, and a check result is obtained.
It may be that, when the interface interceptor program queries the verification logic, the verification logic is a script file, the interface interceptor program sends the script file to the verification program, then the service server calls the script file through the checking program and runs the script file in advance so as to check whether grammar errors occur in the script file, and when the verification program can successfully call the script file and can run the script file in advance, the script file is used to check the interface call request, so that the service server queries the call parameter in the call request through the check program, and queries the service identifier from the call parameter, such as querying the service code, and executing a verification process corresponding to the service code in the script file according to the service code, thereby completing the verification of the interface calling request and obtaining a verification result.
In this embodiment, when the program is verified or the verification logic is obtained, the verification logic may be loaded first, so that when the loading is successful, the interface call request is verified, thereby ensuring the accuracy of the verification, and in the verification process, the service identifier may be received through querying, so that the corresponding verification logic is executed, thereby further ensuring the accuracy of the verification, and ensuring that the verification logic is executed only by executing the flow related to the service identifier, thereby improving the verification efficiency.
In one embodiment, generating the interface call result according to the verification result includes: sending the checking result to an interface interception program through the checking program; inquiring a verification result through the interface interception program, and when the verification result is that the verification is passed, sending an interface calling request to the service program through the interface interception program; and generating interface response information through the service program, and taking the interface response information as an interface calling result. .
Specifically, the interface response information refers to feedback information that corresponds to the interface call request and can call the relevant interface. The service program refers to a code corresponding to different service logics that can be implemented in the service server, that is, a main code for implementing different services.
Specifically, when the check program sends the check result to the interface interception program, the service server inquires the check result through the interface interception program, and when the check result is found to be a check pass, the interface interception program directly sends the interface calling request to the service program, so that the service server can respond according to the interface calling request and realize a subsequent service process. Furthermore, the interface response information is directly sent to the terminal through the service program, so that the terminal can realize subsequent service processes for the calling related interface.
For example, when the interface to be called corresponding to the interface calling request is an order creation interface, that is, when the interface interception program inquires that the verification result sent by the verification program is verification pass, the service server directly sends the verification result to the service program through the interface interception program, the service server generates interface response information corresponding to the verification pass through the service program, and the interface response information is the interface calling result. Further, the service server sends the interface response information to the terminal, so that the terminal can call the order creation interface, that is, the terminal can store the order data into the service server through the order creation interface.
In this embodiment, when the interface call request passes the verification, the interface response information is directly sent by the service program, so that the terminal completes the interface call to the service server, and the efficiency of the interface call is improved.
In one embodiment, after intercepting the program query check result through the interface, the method comprises the following steps: when the verification result is that the verification fails, inquiring abnormal reason codes according to the verification result which fails to pass; and sending the check result that the interface check fails and the abnormal reason code to the terminal through the interface interception program.
Specifically, the abnormal reason code is a code corresponding to a reason that the interface call request fails to be verified, so that the terminal can read a specific abnormal reason, for example, when the abnormal reason is that a parameter in the interface call request is missing, the parameter missing corresponds to the abnormal reason code, and when the terminal receives the abnormal reason code, the reason that the interface call request fails to be verified is obtained by analyzing as parameter missing. Specifically, when the interface interception program queries that the check result is that the check fails, the interface interception program queries an abnormal reason that the check fails and acquires an abnormal reason code corresponding to the abnormal reason, so that the interface interception program directly sends different check results and corresponding abnormal reason codes to the terminal.
In this embodiment, when the service server queries that the check result is a check-failed check result through the interface interception program, the service server queries the abnormal reason code according to the check result that the check-failed check result is a check-failed check result, and the interface interception program can directly send the check result that the check-failed check result and the abnormal reason code to the terminal, so that the service program is not needed, the processing efficiency of the interface calling request is improved, and the safety of the interface calling can be ensured.
In an embodiment, please refer to fig. 4, which provides a flowchart illustrating a step of verifying a logic change, that is, an interface calling method, further including: receiving change prompt information sent by a rule server, wherein the change prompt information carries a change logic identifier; generating a change inquiry request according to the change logic identifier, and sending the change inquiry request to a rule server; and receiving the change logic corresponding to the change inquiry request returned by the rule server, and storing the change logic into the local cache library.
Specifically, the change prompt information is prompt information that the check logic stored in the rule server changes and is received by the service server. The change logic identifier refers to an interface identifier and a service identifier corresponding to the verification logic with the change. The change inquiry request refers to request information generated by the business server and used for acquiring the verification logic with the change from the rule server. The change logic is check logic stored in the rule server and changed.
Specifically, when the check logic needs to be changed, the change logic is only stored in the rule server through the display interface of the rule server, and when the check logic stored in the rule server is changed, the rule server sends a change prompt message to the service server, that is, when the service server receives the change prompt message, the service server inquires a change logic identifier carried by the change prompt message, further, a change inquiry request is generated according to the interface identifier and the service identifier contained in the change logic identifier, the service server sends the change inquiry request to the rule server, when the rule server receives the change inquiry request, the change logic is inquired according to the change inquiry request and is sent to the service server, so that the service server can store the change logic in the local cache library.
The change prompt information sent by the rule server may be sent through a message queue, a redis (storage database), or a zookeeper (a reliable coordination system of a distributed system). When the service server finishes the change logic, the service server may query the logic attribute of the change logic, which may be that the service server queries the version number, the validation time, and the like of the change logic, so that the service server may replace the original check logic stored in the local cache library according to the validation time, or add a filtering identifier to the original check logic, where the filtering identifier is an identifier that does not call the check logic when the check logic is executed. It should be noted that, in this embodiment, the above steps may be executed by an interface interception program preset in the service server, or may be executed by a service program preset in the service server.
In this embodiment, when the check logic needs to be changed, only the change needs to be performed in the rule server, the service program does not need to be modified, the stability of the service program is ensured, and the service server generates a change query request according to the change logic identifier carried by the change prompt information, and the rule server does not directly send the change logic to the service server, so that the load increase caused by too much change logic received by the service server can be avoided.
In an embodiment, please refer to fig. 5, a timing diagram of an interface calling method in another embodiment is provided, that is, order creation is taken as an example for explanation, a terminal sends an interface calling request for calling an order creation interface to a service server, the service server queries, through an interface interception program, whether parameter verification is enabled for the order creation interface corresponding to the interface calling request, when parameter verification is enabled, the service server queries, through the interface interception program, whether verification logic is stored in a local cache library, and when verification logic is stored in the local cache library, the verification logic is directly sent to a verification program configured in the service server, that is, a rule engine performs verification using the verification logic; when the local cache library does not store the verification logic, the business server acquires the verification logic from the rule server through the interface interception program, when the rule server inquires the corresponding verification logic, the rule server sends the inquired verification logic to the business server, the business server can send the acquired verification logic to the rule engine through the interface interception program, and the verification logic is adopted to perform verification through the rule engine.
When the service server passes the verification of the interface calling request for calling the order establishing interface through the verification program, the interface calling request is sent to the service program through the interface interception program, the service logic is executed, and the execution result is sent to the terminal; and when the service server fails to check the interface calling request, directly sending a calling result that the check fails to pass to the terminal through the interface interception program.
It should be understood that although the various steps in the flow charts of fig. 2-5 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-5 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternating with other steps or at least some of the sub-steps or stages of other steps.
In one embodiment, as shown in fig. 6, there is provided an interface calling apparatus including: a request receiving module 601, a query module 602, an obtaining module 603, a check module 604, and a generating module 605, wherein:
the request receiving module 601 is configured to receive an interface call request sent by a terminal, where the interface call request carries an interface identifier of an interface to be called.
And the query module 602 is configured to determine, according to the interface identifier, whether the interface to be called has a check identifier through the interface interception program. .
An obtaining module 603, configured to obtain, by the interface interception program according to the interface identifier, a check logic corresponding to the interface call request when the check identifier exists.
The checking module 604 is configured to check the interface call request by using a checking logic through a checking program to obtain a checking result.
And a generating module 605, configured to generate an interface calling result according to the verification result.
In one embodiment, the obtaining module 603 includes:
and the logic query unit is used for querying whether the local cache library has the check logic corresponding to the interface identifier through the interface interception program when the check identifier exists.
And the first request sending unit is used for sending an acquisition request for acquiring the check logic to the rule server through the interface interception program when the check logic is not stored in the local cache library.
And the receiving unit is used for receiving the check logic which is returned by the rule server and corresponds to the acquisition request.
In one embodiment, the obtaining module 603 includes:
and the function query unit is used for querying whether the service program contains the check function or not through the interface interception program when the check logic corresponding to the acquisition request returned by the rule server is not received.
And the second request sending unit is used for sending the interface calling request to the service program through the interface interception program when the service program contains the check function.
In one embodiment, the verification module 604 includes:
and the loading unit is used for loading the verification logic and obtaining a loading result through the verification program.
And the identification query unit is used for querying the service identification corresponding to the interface call request through the verification program when the loading result is that the loading is successful.
And the checking unit is used for checking the interface calling request by adopting a checking logic according to the service identifier through a checking program to obtain a checking result.
In one embodiment, the generating module 605 includes:
and the result sending unit is used for sending the verification result to the interface interception program through the verification program.
And the forwarding unit is used for inquiring the verification result through the interface interception program, and sending the interface calling request to the service program through the interface interception program when the verification result is that the verification is passed.
And the information sending unit is used for generating interface response information through the service program and taking the interface response information as an interface calling result. In one embodiment, the generating module 605 includes:
and the code inquiring unit is used for inquiring the abnormal reason code according to the verification result which is not verified when the verification result is that the verification is not passed.
And the abnormal result sending unit is used for sending the check result which is not passed by the interface check and the abnormal reason code to the terminal through the interface interception program.
In one embodiment, the apparatus 600 further comprises:
and the information receiving module is used for receiving change prompt information sent by the rule server, and the change prompt information carries a change logic identifier.
And the generating module is used for generating a change inquiry request according to the change logic identifier and sending the change inquiry request to the rule server.
And the storage module is used for receiving the change logic corresponding to the change inquiry request returned by the rule server and storing the change logic into the local cache library.
For the specific definition of the interface calling device, reference may be made to the definition of the interface calling method above, and details are not described here. The modules in the interface calling device can be wholly or partially realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 7. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing interface call data. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement an interface call method.
Those skilled in the art will appreciate that the architecture shown in fig. 7 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, there is provided a computer device comprising a memory storing a computer program and a processor implementing the following steps when the processor executes the computer program: receiving an interface calling request, wherein the interface calling request carries an interface identifier of an interface to be called; judging whether the interface to be called has a check identifier or not through an interface interception program according to the interface identifier; when the check identifier exists, acquiring a check logic corresponding to the interface calling request through an interface interception program according to the interface identifier; verifying the interface calling request by adopting a verification logic through a verification program to obtain a verification result; and generating an interface calling result according to the checking result.
In one embodiment, when the processor executes the computer program, it is implemented that when the check identifier exists, the interface interception program obtains, according to the interface identifier, the check logic corresponding to the interface call request, including: when the check identification exists, inquiring whether a check logic corresponding to the interface identification exists in the local cache library or not through an interface interception program; when the local cache library does not store the verification logic, an acquisition request for acquiring the verification logic is sent to the rule server through the interface interception program; and receiving the check logic which is returned by the rule server and corresponds to the acquisition request.
In one embodiment, the processor, when executing the computer program, after sending an acquisition request for acquiring the check logic to the rule server through the interface interception program, includes: when the check logic corresponding to the acquisition request returned by the rule server is not received, inquiring whether the service program contains a check function or not through an interface interception program; and when the service program contains the check function, the interface interception program sends the interface calling request to the service program.
In one embodiment, when the processor executes the computer program, the verifying the interface call request by using a verifying logic through a verifying program to obtain a verifying result, including: loading the check logic and obtaining a loading result through a check program; when the loading result is that the loading is successful, calling a service identifier corresponding to the request through a checking program query interface; and verifying the interface calling request by using a verification logic according to the service identifier through a verification program to obtain a verification result.
In one embodiment, the processor, when executing the computer program, generates an interface call result according to the check result, including: sending the checking result to an interface interception program through the checking program; inquiring a verification result through the interface interception program, and when the verification result is that the verification is passed, sending an interface calling request to the service program through the interface interception program; and generating interface response information through the service program, and taking the interface response information as an interface calling result. In one embodiment, the processor, when executing the computer program, after intercepting the program query verification result through the interface, includes: when the verification result is that the verification fails, inquiring abnormal reason codes according to the verification result which fails to pass; and sending the check result that the interface check fails and the abnormal reason code to the terminal through the interface interception program.
In one embodiment, the processor, when executing the computer program, further performs the steps of: receiving change prompt information sent by a rule server, wherein the change prompt information carries a change logic identifier; generating a change inquiry request according to the change logic identifier, and sending the change inquiry request to a rule server; and receiving the change logic corresponding to the change inquiry request returned by the rule server, and storing the change logic into the local cache library.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: receiving an interface calling request, wherein the interface calling request carries an interface identifier of an interface to be called; judging whether the interface to be called has a check identifier or not through an interface interception program according to the interface identifier; when the check identifier exists, acquiring a check logic corresponding to the interface calling request through an interface interception program according to the interface identifier; verifying the interface calling request by adopting a verification logic through a verification program to obtain a verification result; and generating an interface calling result according to the checking result.
In one embodiment, when executed by a processor, a computer program implements that when a check identifier exists, the interface interception program obtains, according to the interface identifier, check logic corresponding to the interface call request, including: when the identifier exists, inquiring whether a verification logic corresponding to the interface identifier exists in a local cache library or not through an interface interception program; when the local cache library does not store the verification logic, an acquisition request for acquiring the verification logic is sent to the rule server through the interface interception program; and receiving the check logic which is returned by the rule server and corresponds to the acquisition request.
In one embodiment, the computer program when executed by the processor, after sending a get request for getting the check logic to the rule server via the interface intercept program, comprises: when the check logic corresponding to the acquisition request returned by the rule server is not received, inquiring whether the service program contains a check function or not through an interface interception program; and when the service program contains the check function, the interface interception program sends the interface calling request to the service program.
In one embodiment, the computer program when executed by the processor implements a verification procedure to verify the interface call request with a verification logic to obtain a verification result, including: loading the check logic and obtaining a loading result through a check program; when the loading result is that the loading is successful, calling a service identifier corresponding to the request through a checking program query interface; and verifying the interface calling request by using a verification logic according to the service identifier through a verification program to obtain a verification result.
In one embodiment, the computer program when executed by the processor implements generating an interface call result from the verification result, comprising: sending the checking result to an interface interception program through the checking program; inquiring a verification result through the interface interception program, and when the verification result is that the verification is passed, sending an interface calling request to the service program through the interface interception program; and generating interface response information through the service program, and taking the interface response information as an interface calling result. In one embodiment, the computer program when executed by the processor, after intercepting the program query verification result via the interface, includes: when the verification result is that the verification fails, inquiring abnormal reason codes according to the verification result which fails to pass; and sending the check result that the interface check fails and the abnormal reason code to the terminal through the interface interception program.
In one embodiment, the computer program when executed by the processor further performs the steps of: receiving change prompt information sent by a rule server, wherein the change prompt information carries a change logic identifier; generating a change inquiry request according to the change logic identifier, and sending the change inquiry request to a rule server; and receiving the change logic corresponding to the change inquiry request returned by the rule server, and storing the change logic into the local cache library.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. An interface call method, the method comprising:
receiving an interface calling request, wherein the interface calling request carries an interface identifier of an interface to be called;
judging whether the interface to be called has a check identifier or not through an interface interception program according to the interface identifier;
when a check identifier exists, acquiring a check logic corresponding to the interface calling request according to the interface identifier through the interface interception program;
verifying the interface calling request by adopting the verification logic through a verification program to obtain a verification result;
and generating an interface calling result according to the checking result.
2. The method according to claim 1, wherein when there is a check identifier, acquiring, by the interface interception program according to the interface identifier, a check logic corresponding to the interface call request, includes:
when the check identification exists, inquiring whether a local cache library has the check logic corresponding to the interface identification through the interface interception program;
when the local cache library does not store the verification logic, sending an acquisition request for acquiring the verification logic to a rule server through the interface interception program;
and receiving the check logic which is returned by the rule server and corresponds to the acquisition request.
3. The method according to claim 2, wherein after sending the obtaining request for obtaining the checking logic to the rule server through the interface interception program, the method comprises:
when the check logic corresponding to the acquisition request returned by the rule server is not received, inquiring whether a service program contains a check function or not through the interface interception program;
and when the service program contains the check function, the interface calling request is sent to the service program through the interface interception program.
4. The method according to claim 1, wherein the verifying the interface call request with the verification logic by the verification program to obtain a verification result includes:
loading the check logic and obtaining a loading result through a check program;
when the loading result is that the loading is successful, inquiring a service identifier corresponding to the interface calling request through the verification program;
and verifying the interface calling request by adopting the verification logic according to the service identifier through the verification program to obtain a verification result.
5. The method of claim 1, wherein generating an interface invocation result according to the verification result comprises:
sending the checking result to the interface interception program through the checking program;
inquiring the verification result through the interface interception program, and when the verification result is that the verification is passed, sending the interface calling request to a service program through the interface interception program;
and generating interface response information through the service program, and taking the interface response information as an interface calling result.
6. The method according to claim 5, wherein after querying the check result through the interface interceptor, the method comprises:
when the verification result is that the verification fails, inquiring abnormal reason codes according to the verification result which fails to pass;
and sending the check result that the interface check fails and the abnormal reason code to the terminal through the interface interception program.
7. The method of claim 1, further comprising:
receiving change prompt information sent by a rule server, wherein the change prompt information carries a change logic identifier;
generating a change inquiry request according to the change logic identifier, and sending the change inquiry request to the rule server;
and receiving the change logic corresponding to the change inquiry request returned by the rule server, and storing the change logic into a local cache library.
8. An interface invocation apparatus, characterized in that said apparatus comprises:
the device comprises a request receiving module, a request sending module and a request receiving module, wherein the request receiving module is used for receiving an interface calling request, and the interface calling request carries an interface identifier of an interface to be called;
the query module is used for judging whether the interface to be called has a check identifier or not through the interface interception program according to the interface identifier;
the acquisition module is used for acquiring a check logic corresponding to the interface calling request according to the interface identifier through the interface interception program when the check identifier exists;
the verification module is used for verifying the interface calling request by adopting the verification logic through a verification program to obtain a verification result;
and the generating module is used for generating an interface calling result according to the checking result.
9. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor implements the steps of the method of any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910779102.0A CN110633160A (en) | 2019-08-22 | 2019-08-22 | Interface calling method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910779102.0A CN110633160A (en) | 2019-08-22 | 2019-08-22 | Interface calling method and device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110633160A true CN110633160A (en) | 2019-12-31 |
Family
ID=68970497
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910779102.0A Pending CN110633160A (en) | 2019-08-22 | 2019-08-22 | Interface calling method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110633160A (en) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111258832A (en) * | 2020-01-22 | 2020-06-09 | 泰康保险集团股份有限公司 | Interface parameter checking method, device, equipment and medium |
| CN111314306A (en) * | 2020-01-17 | 2020-06-19 | 网易（杭州）网络有限公司 | Interface access method and device, electronic equipment and storage medium |
| CN111444224A (en) * | 2020-03-24 | 2020-07-24 | 政采云有限公司 | Service data verification method and device |
| CN111625301A (en) * | 2020-05-25 | 2020-09-04 | 泰康保险集团股份有限公司 | Idempotent processing method, apparatus, device and storage medium |
| CN112579340A (en) * | 2020-12-10 | 2021-03-30 | 潍柴动力股份有限公司 | Data verification method, device and equipment of electronic control unit and storage medium |
| CN113806111A (en) * | 2021-09-18 | 2021-12-17 | 平安普惠企业管理有限公司 | Front-end and back-end interactive interface scheduling optimization method, device, equipment and storage medium |
| CN114697396A (en) * | 2020-12-29 | 2022-07-01 | 北京国双科技有限公司 | Request processing method and device, electronic equipment and readable storage medium |
| CN115134113A (en) * | 2022-05-13 | 2022-09-30 | 山东鲁软数字科技有限公司 | Platform data security authentication method, system, terminal and storage medium |
| CN115185616A (en) * | 2022-09-14 | 2022-10-14 | 深圳依时货拉拉科技有限公司 | Business rule engine and processing method thereof |
| CN115499291A (en) * | 2022-09-14 | 2022-12-20 | 平安壹钱包电子商务有限公司 | Method and device for processing service zero-drop alarm information and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106909838A (en) * | 2015-12-22 | 2017-06-30 | 北京奇虎科技有限公司 | A kind of method and device of hooking system service call |
| CN107451460A (en) * | 2017-06-28 | 2017-12-08 | 努比亚技术有限公司 | Interface processing method, equipment, server and computer-readable recording medium |
| CN108683712A (en) * | 2018-04-25 | 2018-10-19 | 咪咕文化科技有限公司 | The generation method of application checks and check key, device and storage medium |
| CN109344642A (en) * | 2018-08-31 | 2019-02-15 | 平安科技（深圳）有限公司 | Interface rules method of calibration, device, computer equipment and storage medium |
| WO2019041859A1 (en) * | 2017-08-31 | 2019-03-07 | 平安科技（深圳）有限公司 | Method, device, and server for processing supervision information, and storage medium |
| CN109815013A (en) * | 2019-01-02 | 2019-05-28 | 深圳壹账通智能科技有限公司 | Business data processing method, device, computer equipment and storage medium |
-
2019
- 2019-08-22 CN CN201910779102.0A patent/CN110633160A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106909838A (en) * | 2015-12-22 | 2017-06-30 | 北京奇虎科技有限公司 | A kind of method and device of hooking system service call |
| CN107451460A (en) * | 2017-06-28 | 2017-12-08 | 努比亚技术有限公司 | Interface processing method, equipment, server and computer-readable recording medium |
| WO2019041859A1 (en) * | 2017-08-31 | 2019-03-07 | 平安科技（深圳）有限公司 | Method, device, and server for processing supervision information, and storage medium |
| CN108683712A (en) * | 2018-04-25 | 2018-10-19 | 咪咕文化科技有限公司 | The generation method of application checks and check key, device and storage medium |
| CN109344642A (en) * | 2018-08-31 | 2019-02-15 | 平安科技（深圳）有限公司 | Interface rules method of calibration, device, computer equipment and storage medium |
| CN109815013A (en) * | 2019-01-02 | 2019-05-28 | 深圳壹账通智能科技有限公司 | Business data processing method, device, computer equipment and storage medium |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111314306A (en) * | 2020-01-17 | 2020-06-19 | 网易（杭州）网络有限公司 | Interface access method and device, electronic equipment and storage medium |
| CN111258832B (en) * | 2020-01-22 | 2023-06-20 | 泰康保险集团股份有限公司 | Interface parameter verification method, device, equipment and medium |
| CN111258832A (en) * | 2020-01-22 | 2020-06-09 | 泰康保险集团股份有限公司 | Interface parameter checking method, device, equipment and medium |
| CN111444224A (en) * | 2020-03-24 | 2020-07-24 | 政采云有限公司 | Service data verification method and device |
| CN111444224B (en) * | 2020-03-24 | 2023-08-15 | 政采云有限公司 | Service data verification method and device |
| CN111625301A (en) * | 2020-05-25 | 2020-09-04 | 泰康保险集团股份有限公司 | Idempotent processing method, apparatus, device and storage medium |
| CN112579340A (en) * | 2020-12-10 | 2021-03-30 | 潍柴动力股份有限公司 | Data verification method, device and equipment of electronic control unit and storage medium |
| CN112579340B (en) * | 2020-12-10 | 2023-03-21 | 潍柴动力股份有限公司 | Data verification method, device and equipment of electronic control unit and storage medium |
| CN114697396A (en) * | 2020-12-29 | 2022-07-01 | 北京国双科技有限公司 | Request processing method and device, electronic equipment and readable storage medium |
| CN113806111A (en) * | 2021-09-18 | 2021-12-17 | 平安普惠企业管理有限公司 | Front-end and back-end interactive interface scheduling optimization method, device, equipment and storage medium |
| CN115134113A (en) * | 2022-05-13 | 2022-09-30 | 山东鲁软数字科技有限公司 | Platform data security authentication method, system, terminal and storage medium |
| CN115134113B (en) * | 2022-05-13 | 2024-04-09 | 山东鲁软数字科技有限公司 | Platform data security authentication method, system, terminal and storage medium |
| CN115185616A (en) * | 2022-09-14 | 2022-10-14 | 深圳依时货拉拉科技有限公司 | Business rule engine and processing method thereof |
| CN115185616B (en) * | 2022-09-14 | 2022-12-13 | 深圳依时货拉拉科技有限公司 | Business rule engine device and processing method of business rule engine |
| CN115499291A (en) * | 2022-09-14 | 2022-12-20 | 平安壹钱包电子商务有限公司 | Method and device for processing service zero-drop alarm information and storage medium |
| CN115499291B (en) * | 2022-09-14 | 2024-04-02 | 平安壹钱包电子商务有限公司 | Processing method and device for service zero-drop alarm information and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110633160A (en) | Interface calling method and device, computer equipment and storage medium | |
| CN109474578B (en) | Message checking method, device, computer equipment and storage medium | |
| CN108573371B (en) | Data approval method, device, computer equipment and storage medium | |
| CN110650186A (en) | Interface calling method and device, computer equipment and storage medium | |
| CN109039751B (en) | Method, device, computer equipment and storage medium for configuring route | |
| CN109361628B (en) | Message assembling method and device, computer equipment and storage medium | |
| CN109144487B (en) | Method, device, computer equipment and storage medium for developing business of parts | |
| CN110555769A (en) | Block chain transaction data processing method and device, computer equipment and storage medium | |
| CN108366132B (en) | Method and device for managing service between servers, computer equipment and storage medium | |
| CN112395202B (en) | Interface automation test method and device, computer equipment and storage medium | |
| CN109257426B (en) | Service line resource loading method and device, computer equipment and storage medium | |
| CN110727698A (en) | Database access method and device, computer equipment and storage medium | |
| CN112527357A (en) | Service hot loading updating method and device, computer equipment and storage medium | |
| CN110531984B (en) | Code compiling method, device, system, computer equipment and storage medium | |
| CN111831365A (en) | Interface route forwarding method, system, computer equipment and readable storage medium | |
| CN114003432A (en) | Parameter checking method and device, computer equipment and storage medium | |
| CN114115967A (en) | Service data processing method and device, computer equipment and storage medium | |
| CN111355800B (en) | Service processing method, device, equipment and storage medium | |
| CN111159025B (en) | Application program interface testing method and device, computer equipment and storage medium | |
| CN110727477B (en) | Component loading method and device, computer equipment and storage medium | |
| CN110516172B (en) | Resource calling method and device, computer equipment and storage medium | |
| CN112559352A (en) | Interface test method, device, equipment and storage medium | |
| CN111552989A (en) | Service data processing method, device, equipment and storage medium based on block chain | |
| CN115396221A (en) | Authorization processing method, device and system, electronic equipment and storage medium | |
| CN114003486A (en) | Plug-in debugging method, client, server and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20191231 |