CN113360138A

CN113360138A - Operation log processing method and device, electronic equipment and storage medium

Info

Publication number: CN113360138A
Application number: CN202110678833.3A
Authority: CN
Inventors: 詹昭吉
Original assignee: WeBank Co Ltd
Current assignee: WeBank Co Ltd
Priority date: 2021-06-18
Filing date: 2021-06-18
Publication date: 2021-09-07

Abstract

The embodiment of the application provides an operation log processing method, an operation log processing device, electronic equipment and a computer storage medium, wherein the method comprises the following steps: determining a target persistent layer interface, wherein the target persistent layer interface is called when editing operation is carried out on target data; obtaining an operation log annotation corresponding to a target persistent layer interface; the operation log annotation is used for representing a persistent layer query interface corresponding to the target data; before editing operation is carried out on target data, acquiring pre-operation data of the target data according to the operation log annotation; and/or after editing operation is carried out on the target data, acquiring operated data of the target data according to the operation log annotation; and storing the data before the operation of the target data and/or the data after the operation of the target data into an operation log. The operation log processing method based on the application can reduce the coupling of different functional modules in a software system and improve the reliability of the data snapshot recorded by the operation log.

Description

Operation log processing method and device, electronic equipment and storage medium

Technical Field

The embodiment of the application relates to the technical field of financial technology (Fintech), in particular to an operation log processing method and device, electronic equipment and a computer storage medium.

Background

With the development of computer technology, more and more technologies are applied in the financial field, and the traditional financial industry is gradually changing to financial technology, but higher requirements are also put forward on the technologies due to the requirements of the financial industry on safety and real-time performance.

A Service Oriented Architecture (SOA) splits a software system into a presentation layer, a Service layer and a persistence layer, wherein the presentation layer, the Service layer and the persistence layer correspond to different functional modules. The service layer is mainly responsible for processing business logic, interaction between the processing and the page, and service is provided for users. Business logic can be set in the service layer, and the business logic can call the service of the service layer. The persistence layer is responsible for calling a bottom layer interface of the framework and performing access operation on the database, and the method comprises the following steps: add, delete, modify, and query.

The Operation Log (Operation Log) pays attention to time information and network address information when a user performs Data Operation on Data in the database, and records Data snapshots (Data Snapshot) before and after the user performs Data Operation on the Data. Before the user operates the data, the user inquires the inquiry record of the acquired data in the database. When a user operates data, the presentation layer initiates an editing operation request to the service layer, wherein the editing operation request comprises last inquiry record and operated data. The service layer adds a record in the operation log and updates the data record in the operation log; and saving the value of the last query record and the value of the data after the operation in an operation log.

In the related art, when the operation log function is implemented, it is necessary to write corresponding business code logic of a front record and a back record for each editing service in the service layer, and thus, the intrusiveness on the business code of the service layer is strong. The program function of the presentation layer needs to additionally store the query result of the target data, and additionally carries the query result of the target data when the editing operation request is initiated, so that the intrusion on the service code of the presentation layer is strong. When the service code has strong intrusiveness, the coupling of different functional modules in the software system is high, and the development and maintenance costs of the software system are increased. Therefore, how to reduce the coupling of different functional modules in a software system becomes an important issue to be solved urgently.

Disclosure of Invention

The embodiment of the application provides an operation log processing method and device, electronic equipment and a computer storage medium, which can reduce the coupling of different functional modules in a software system.

An operation log processing method provided by an embodiment of the present application includes:

determining a target persistent layer interface, wherein the target persistent layer interface is called when editing operation is carried out on target data; obtaining an operation log annotation corresponding to the target persistent layer interface; the operation log annotation is used for representing a persistent layer query interface corresponding to the target data;

before editing operation is carried out on the target data, acquiring pre-operation data of the target data according to the operation log annotation; and/or after the target data is edited, acquiring the operated data of the target data according to the operation log annotation;

and storing the data before the operation of the target data and/or the data after the operation of the target data into an operation log.

In one implementation, before performing an editing operation on the target data, acquiring pre-operation data of the target data according to the operation log annotation includes:

obtaining semantic information of the target persistent layer interface;

and when the semantic information of the target persistent layer interface belongs to deletion or modification of the target data, before editing operation is carried out on the target data, acquiring pre-operation data of the target data according to the operation log annotation.

In one implementation, after the editing operation is performed on the target data, acquiring post-operation data of the target data according to the operation log annotation includes:

obtaining semantic information of the target persistent layer interface;

and when the semantic information of the target persistent layer interface is the semantic information for inserting or modifying the target data, after editing operation is carried out on the target data, obtaining the operated data of the target data according to the operation log annotation.

In one implementation, the method further comprises:

and generating an operation log annotation corresponding to the target persistent layer interface, wherein the operation log annotation comprises the identification information of the target data and the mapping relation between the persistent layer query interfaces corresponding to the target data.

In one implementation, obtaining pre-operation data of the target data and/or post-operation data of the target data according to the operation log annotation includes:

analyzing the operation log annotation to obtain the mapping relation between the identification information of the target data and a persistent layer query interface corresponding to the target data;

determining a persistent layer query interface corresponding to the target data according to the identification information of the target data and the mapping relation;

and acquiring the data before the operation of the target data and/or the data after the operation of the target data according to the persistent layer query interface corresponding to the target data.

In one implementation, the obtaining of the operation log annotation corresponding to the target persistent layer interface includes:

determining a database statement executed when the target data is edited; acquiring a mapping statement corresponding to the database statement, wherein the mapping statement is used for setting an operation log annotation corresponding to the target persistent layer interface;

analyzing the mapping statement corresponding to the database statement according to the grammar rule of the mapping statement, and acquiring an operation log annotation corresponding to the target persistent layer interface;

and when an operation log annotation corresponding to the target persistent layer interface is acquired, determining that pre-operation data of the target data and/or post-operation data of the target data need to be stored in the operation log.

In one implementation, the step of obtaining pre-operation data of the target data and/or post-operation data of the target data according to the operation log annotation is implemented on the basis of a plug-in.

An operation log processing apparatus provided in an embodiment of the present application includes:

the device comprises a determining module, a judging module and a judging module, wherein the determining module is used for determining a target persistent layer interface, and the target persistent layer interface is called when editing operation is carried out on target data; obtaining an operation log annotation corresponding to the target persistent layer interface; the operation log annotation is used for representing a persistent layer query interface corresponding to the target data;

the processing module is used for acquiring the pre-operation data of the target data according to the operation log annotation before the target data is edited; and/or after the target data is edited, acquiring the operated data of the target data according to the operation log annotation;

and the storage module is used for storing the data before the operation of the target data and/or the data after the operation of the target data into an operation log.

In one implementation, the processing module, configured to obtain pre-operation data of the target data according to the operation log annotation before performing an editing operation on the target data, includes:

obtaining semantic information of the target persistent layer interface;

In one implementation manner, the processing module, configured to obtain post-operation data of the target data according to the operation log annotation after performing an editing operation on the target data, includes:

obtaining semantic information of the target persistent layer interface;

In one implementation, the processing module is further configured to: and generating an operation log annotation corresponding to the target persistent layer interface, wherein the operation log annotation comprises the identification information of the target data and the mapping relation between the persistent layer query interfaces corresponding to the target data.

In one implementation, the processing module is configured to obtain pre-operation data of the target data and/or post-operation data of the target data according to the operation log annotation, and includes:

In an implementation manner, the processing module is configured to obtain the pre-operation data of the target data and/or the post-operation data of the target data according to the operation log annotation based on a plug-in.

An embodiment of the present application provides an electronic device, where the electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the method for processing an operation log according to one or more of the foregoing technical solutions is implemented.

The embodiment of the application provides a computer storage medium, wherein a computer program is stored in the computer storage medium; the computer program can implement the operation log processing method provided by one or more of the above technical solutions after being executed.

Based on the operation log processing method, operation log annotations corresponding to the target persistent layer interface are obtained; the operation log annotation is used for representing a persistent layer query interface corresponding to the target data; acquiring pre-operation data of the target data and/or post-operation data of the target data according to the operation log annotation; and storing the data before the operation of the target data and/or the data after the operation of the target data into an operation log. The method has the advantages that program codes for realizing the functions of front recording and back recording in the operation log are not required to be written in the service layer, the program codes for realizing the function of storing the query record of the data are written in the presentation layer, and the intrusiveness of the operation log function to the service codes of the service layer is reduced, so that the coupling of different functional modules in the software system is reduced. The method and the device do not depend on the editing operation request sent by the presentation layer to carry out value transfer calling, can reduce the potential safety hazard that the data is falsified by the packet capturing, and therefore improve the reliability of the data snapshot recorded by the operation log.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

Fig. 1 is an application scenario diagram of an operation log processing method provided in the related art;

fig. 2 is a schematic flowchart of an operation log processing method according to an embodiment of the present application;

fig. 3 is a schematic flowchart of obtaining pre-operation data and/or post-operation data of target data according to an embodiment of the present application;

fig. 4 is a schematic flowchart of obtaining an operation log annotation corresponding to a target persistent layer interface according to an embodiment of the present application;

fig. 5 is an application scenario diagram of the operation log processing method according to the embodiment of the present application;

fig. 6 is another application scenario diagram of the operation log processing method according to the embodiment of the present application;

fig. 7 is a diagram of another application scenario of the operation log processing method according to the embodiment of the present application;

fig. 8 is a schematic diagram of an operation log processing apparatus according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

The present application will be described in further detail below with reference to the accompanying drawings and examples. It should be understood that the examples provided herein are merely illustrative of the present application and are not intended to limit the present application. In addition, the following examples are provided as partial examples for implementing the present application, not all examples for implementing the present application, and the technical solutions described in the examples of the present application may be implemented in any combination without conflict.

In a service-oriented architecture, a software system is split into a presentation layer, a service layer, and a persistence layer. Wherein, the presentation layer belongs to a front-end system in the software system, and the service layer and the persistence layer belong to a back-end system of the software system. The service layer may be implemented by SpringMVC. The SpringMVC is a request-driven type lightweight Web framework based on Java, accords with a Model-View-Controller architecture mode idea, and realizes decoupling of foreground page display, control logic and data storage.

Fig. 1 is a diagram illustrating an application scenario of an operation log processing method provided in the related art. Referring to fig. 1, in the related art, a data processing flow of a user when initiating an editing operation request may include: step 101: a user initiates a data query request; step 102: the service layer inquires target data in a database; step 103: the database returns target data to the user; step 104: the service layer assembles target data and returns the target data to the presentation layer; step 105: and storing the target data in the memory of the presentation layer.

Step 106: the presentation layer acquires target data from the memory; step 107: a user initiates an editing operation request for target data; step 108: taking data obtained by inquiring the target data as pre-operation data of the target data, and recording the pre-operation data of the target data in an operation log in a database; step 109: modifying the database table record; step 110: taking data obtained after editing operation is carried out on the target data as operated data of the target data, and recording the operated data of the target data in an operation log in a database; step 111: and returning a modification result of the editing operation on the target data to the user.

In the related art, when the operation log function is implemented, it is necessary to write corresponding business code logic of a front record and a back record for each editing service in the service layer, and thus, the intrusiveness on the business code of the service layer is strong. The program function of the presentation layer needs to additionally store the query result of the target data, and additionally carries the query result of the target data when the editing operation request is initiated, so that the intrusion on the service code of the presentation layer is strong.

Fig. 2 shows a schematic flowchart of an operation log processing method provided in an embodiment of the present application. Referring to fig. 2, the operation log processing method provided in the embodiment of the present application may include the following steps:

step A201: and determining a target persistent layer interface, wherein the target persistent layer interface is called when the target data is edited.

Here, the target data may be at least one item of data presented in the front-end interface. The operation type of the editing operation on the target data may include any one of: add, delete, modify, query.

It should be understood that the persistence layer is a hierarchical concept in enterprise level system programming, and the persistence layer is a database operation interface.

In an example, the database operations of the persistence layer may be completed by the MyBatis framework when editing operations are performed on the target data. The Mybatis framework is a Java-based persistent layer framework.

In an example, a target persistent layer interface may correspond to a table operation when performing an editing operation on target data.

Step A202: obtaining an operation log annotation corresponding to a target persistent layer interface; and the operation log annotation is used for representing a persistent layer query interface corresponding to the target data.

Here, the operation log annotation is a description of a code level for adding the operation log annotation to a certain section of program entry.

In an example, according to the definition of the expression of the parameter mapping relation corresponding to the target persistent layer interface, the operation log annotation corresponding to the target persistent layer interface is obtained.

In an example, when an operation log annotation corresponding to a target persistent layer interface is obtained, it indicates that the operation log about the target data needs to be recorded in the database operation this time, and the following step a203 is executed. Otherwise, the following step a203 is not performed, and the flow may be ended.

Step A203: before editing operation is carried out on target data, acquiring pre-operation data of the target data according to the operation log annotation; and/or after editing operation is carried out on the target data, acquiring operated data of the target data according to the operation log annotation.

Here, the pre-operation data of the target data corresponds to a pre-operation database data record, and may be a value of one field or a record in a complete database table. The operated data of the target data corresponds to the operated database data record, and can be a field value or a record in a complete database table.

In an example, the oplog of the target data can include pre-operation data of the target data and/or post-operation data of the target data. And determining whether to record pre-operation data of the target data and/or post-operation data of the target data according to the operation log annotation corresponding to the target persistent layer interface.

In an example, when pre-operation data and/or post-operation data of target data need to be recorded is determined, a persistent layer query interface corresponding to the target data is analyzed according to an operation log annotation, and the persistent layer query interface corresponding to the target data is called to obtain the pre-operation data and/or the post-operation data of the target data.

In an example, pre-operation data and/or post-operation data of the target data is obtained according to a persistent layer query interface defined by the execution of the oplog annotation.

Step A204: and storing the data before the operation of the target data and/or the data after the operation of the target data into an operation log.

Here, the operation log focuses on time information and network address information when a user performs data operation on data in the database, and records data snapshots before and after the user performs data operation on the data.

In an example, a table structure of the operation log is created, in which any of the following information may be included: the identification information of the target data, the user information corresponding to the target data, the operation time of the target data, the data before the operation of the target data and the data after the operation corresponding to the target data.

In an example, identifying information for target data is automatically generated by a database; acquiring user information corresponding to target data according to the context of an editing operation request sent by a user; the machine time when the editing operation is performed on the target data is taken as the operation time of the target data.

In an example, identification information of target data is acquired according to a context of an editing operation request sent by a user, and an operation log record about the target data is acquired depending on the identification information of the target data.

Based on the operation log processing method, operation log annotations corresponding to the target persistent layer interface are obtained; the operation log annotation is used for representing a persistent layer query interface corresponding to the target data; acquiring pre-operation data of the target data and/or post-operation data of the target data according to the operation log annotation; and storing the data before the operation of the target data and/or the data after the operation of the target data into an operation log. The program codes for realizing the functions of front recording and back recording in the operation log are not required to be written in the service layer, and the program codes for realizing the function of saving the query record of the data are not required to be written in the presentation layer, so that the intrusiveness of the operation log function to the service codes of the service layer can be reduced, and the coupling of different functional modules in the software system is reduced. The method and the device do not depend on the editing operation request sent by the presentation layer to carry out value transfer calling, can reduce the potential safety hazard that the data is falsified by the packet capturing, and therefore improve the reliability of the data snapshot recorded by the operation log.

In practical applications, the steps a201 to a204 may be implemented by a Processor, and the Processor may be at least one of an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Digital Signal Processing Device (DSPD), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a Central Processing Unit (CPU), a controller, a microcontroller, and a microprocessor.

In one implementation, in step a203, before performing an editing operation on the target data, acquiring pre-operation data of the target data according to the operation log annotation may include the following steps:

obtaining semantic information of a target persistent layer interface; when the semantic information of the target persistent layer interface belongs to deletion or modification of target data, before editing operation is carried out on the target data, pre-operation data of the target data is obtained according to the operation log annotation.

In an example, in the Mybatis framework, an interceptor may intercept a target persistent layer interface, and determine whether an SQL statement of the target persistent layer interface is an "update" semantic or an "insert" semantic by parsing a Structured Query Language (SQL) template corresponding to the target interface.

Here, the Mybatis framework is a persistent layer framework supporting dynamic modification of a structured query statement, and implements a mapping function using Extensible Markup Language (XML) or annotation, and maps a persistent layer interface into a record in a database.

In an example, when the SQL statement of the target persistent layer interface is the "update" semantic or the "insert" semantic, the post-operation data corresponding to the target data is recorded in the operation log.

Here, the SQL statement of the target persistent layer interface corresponds to the persistent layer interface called when the target data is edited.

In an example, when the SQL statement of the target persistent layer interface is the "update" semantic, pre-operation data of the target data is recorded, a warehoused operation log record is acquired according to the identification information of the target data, and post-operation data of the target data is updated in the operation log. When the SQL statement of the target persistent layer interface is the 'insert' semantic, an operation log record is newly added in the operation log record table, and the operated data of the target data is recorded.

In one implementation, in step a203, after performing an editing operation on the target data, acquiring post-operation data of the target data according to the operation log annotation may include the following steps:

obtaining semantic information of a target persistent layer interface; when the semantic information of the target persistent layer interface is inserted or modified into the target data, after the target data is edited, the operated data of the target data is obtained according to the operation log annotation.

In an example, in the Mybatis framework, the interceptor may intercept the target persistent layer interface, and determine whether the SQL statement of the target persistent layer interface is the "update" semantic or the "delete" semantic by analyzing the SQL template corresponding to the target interface. When the SQL statement of the target persistent layer interface is the 'update' semantic or the 'delete' semantic, recording data before operation in the operation log.

In one implementation, the method further comprises: and generating an operation log annotation corresponding to the target persistent layer interface, wherein the operation log annotation comprises the identification information of the target data and the mapping relation between the persistent layer query interfaces corresponding to the target data.

In an example, the semantic information of the target persistent layer interface may include any one of: the "update" semantics, the "insert" semantics, and the "delete" semantics.

In practical application, a user can add an operation log annotation corresponding to the persistent layer interface according to business needs. In the annotation of the operation log, the expression of the parameter mapping relation corresponding to the target persistent layer interface can be customized by a user.

Here, when defining an expression of a parameter mapping relationship corresponding to a target persistent layer interface, a mapping statement (MappingStatement) corresponding to the target persistent layer interface may be set in the Mybatis framework.

In an example, an el (expression language) expression may be used to form an oplog annotation, which may be in the form of:

@LogMapping(

SelectSql ═ name of persistent layer query interface "

paramMapping ═ expression of parameter mapping relationship "

)

Here, the parameter paramMapping is used to define an expression of the parameter mapping relationship.

In an example, the expression of the parameter mapping relationship may use an EL expression to define a mapping relationship between the identification information of the target data and the persistent layer query interface corresponding to the target data.

It should be understood that the EL expression is a Spring expression language, supporting expressions that define parameter mapping relationships in oplog annotations.

In one implementation, in the step a203, obtaining pre-operation data of the target data and/or post-operation data of the target data according to the operation log annotation, referring to fig. 3, may include the following steps:

step A301: and analyzing the operation log annotation to obtain the mapping relation between the identification information of the target data and the persistent layer query interface corresponding to the target data.

In an example, based on the identification information of the target persistent layer interface, a database statement executed when the target data is subjected to editing operation is read, and an operation log annotation of the target persistent layer interface is determined.

In an example, the operation log annotation of the target persistent layer interface is analyzed based on a syntax rule of an EL expression adopted by a mapping statement in the operation log annotation, and a mapping relation between identification information of target data and a persistent layer query interface corresponding to the target data is obtained.

Step A302: and determining a persistent layer query interface corresponding to the target data according to the identification information and the mapping relation of the target data.

In an example, a persistent layer query interface corresponding to the target data is determined according to the identification information of the target data and a mapping relationship between the identification information of the target data and the persistent layer query interface corresponding to the target data.

Step A303: and acquiring pre-operation data of the target data and/or post-operation data of the target data according to the persistent layer query interface corresponding to the target data.

In an example, based on a persistent layer query interface corresponding to target data, pre-operation data of the target data and/or post-operation data of the target data are queried in a database according to identification information of the target data, and the pre-operation data of the target data and/or the post-operation data of the target data are acquired.

In the related art, when the editing operation request sent by the user does not carry the operated data of the target data, the service layer cannot record the operated data of the target data in the operation log. For example, for a batch processing instruction "increase the age of each client by one year", the editing operation request does not carry the post-operation data corresponding to "the age of the client is modified to a specific value", and the editing operation request does not specify the identification information of the target data corresponding to the age of the client ", so that the service layer cannot obtain the pre-operation data and the post-operation data related to" the age of the client ", and cannot obtain the data snapshot of the operation log record related to" the age of the client "when the batch processing and data editing operation corresponding to" increase the age of each client by one year "is performed.

In the embodiment of the application, the operated data of the target data is obtained according to the persistent layer query interface of the target data. For the batch processing instruction of the service layer, namely 'increasing the age of each client by one year', when batch processing and data editing operation corresponding to 'increasing the age of each client by one year' is executed, pre-operation data of target data and/or post-operation data of the target data can be acquired according to operation log annotation of a target persistent layer interface called by the target data to which the 'age of the client' belongs during editing operation, and therefore reliability of data snapshot recorded by the operation log is improved.

In one implementation, in the step a202, obtaining an operation log annotation corresponding to the target persistent layer interface, referring to fig. 4, may include the following steps:

step A401: determining a database statement executed when the target data is edited; and acquiring a mapping statement corresponding to the database statement, wherein the mapping statement is used for setting an operation log annotation corresponding to the target persistent layer interface.

In an example, the editing operation of a user on target data is detected, a called persistent layer interface when the user edits the target data is determined, and a database statement executed when the editing operation is performed on the target data is determined according to an operation type of a data operation executed by the called persistent layer interface.

In an example, a database statement executed when the target data is edited is encapsulated, and a mapping statement corresponding to the database statement is obtained.

In an example, the mapping statement may define, by using an EL expression, a mapping relationship between identification information of the target data and a persistent layer query interface corresponding to the target data. Thus, the mapping statement may be used to set an oplog annotation corresponding to the target persistent layer interface.

In an example, the software system may intercept the Executor by using an interface of an mtbastis framework, and detect expressions of parameter mapping relationships of all target persistent layer interfaces to be executed, so that mapping statements corresponding to database statements executed when editing operation is performed on target data may be obtained.

Here, the Interceptor is the name of the Interceptor in the Mybatis frame, and the executer is the Executor for executing the mapping statement MappingStatement in the Mybatis frame.

Step A402: and analyzing the mapping statement corresponding to the database statement according to the grammar rule of the mapping statement, and acquiring the operation log annotation corresponding to the target persistent layer interface.

In an example, the mapping statement corresponding to the database statement is parsed according to the syntax rule of the mapping statement, and the operation log annotation corresponding to the target persistent layer interface is obtained in an attempt.

Step A403: when an operation log annotation corresponding to the target persistent layer interface is obtained, it is determined that pre-operation data of the target data and/or post-operation data of the target data need to be stored in the operation log.

In an example, when an operation log annotation corresponding to a target persistent layer interface is obtained, it indicates that pre-operation data of the target data and/or post-operation data of the target data need to be saved in an operation log. That is, the operation log is required to be recorded in the database operation on the target data.

In an example, when the operation log annotation corresponding to the target persistent layer interface is not obtained, it indicates that the pre-operation data of the target data and/or the post-operation data of the target data do not need to be saved in the operation log. Namely, the database operation on the target data does not need to record an operation log.

In an example, a general program plug-in is adopted to obtain pre-operation data of target data and/or post-operation data of the target data according to an operation log annotation corresponding to a target persistent layer interface, and the pre-operation data of the target data and/or the post-operation data of the target data are stored in an operation log. Thus, the function of recording the operation log is realized.

It should be understood that the concept of "oplog code sinks from the service layer to the persistence layer" is such that the logging function of the oplog is defined as a generic program plug-in. And aggregating the recording function of the operation log to a back-end system, so that the recording function of the operation log is decoupled from the service code of the service layer.

In order to improve the robustness of the program design, the internal logic of the plug-in can be subjected to exception capture processing, so that the plug-in does not influence the original service function, and therefore, a target persistent layer interface is guaranteed to be called when the target data is edited.

In the related technology, the service scenarios expressed by the service layer are not exhaustive, different service scenarios correspond to different service codes, and the different service scenarios lack commonality. When the operation log function is implemented, the service layer needs to analyze the service code and write a program code for implementing the front record and the back record functions in the operation log. Therefore, the intrusion of the business code into the presentation layer is strong.

In the embodiment of the application, the recording function of the operation log is realized by adopting a general program plug-in, and the recording function of the operation log is gathered to the back-end system, so that the recording function of the operation log is decoupled from the service code of the service layer, and the invasion of the operation log function to the service code of the service layer is reduced.

Fig. 5 is an application scenario diagram illustrating an operation log processing method according to an embodiment of the present application. Referring to fig. 5, an operation log processing method provided in an embodiment of the present application based on a network architecture of a persistence layer, a plug-in, and a database may include the following steps: step 501: the persistent layer calls the database; step 502: when the persistent layer calls the database, a pre-recorder is adopted to analyze and obtain which persistent layer query interface needs to be called by the data before operation, and the persistent layer query interface is called to query target data; step 503: the database returns the query result of the target data to the user; step 504: and saving the query result of the target data to an operation log. Step 505: executing SQL sentences of the target persistent layer interface; step 506: the post-recorder analyzes which persistent layer query interface needs to be called in order to obtain the operated data corresponding to the target data, and calls the persistent layer query interface corresponding to the target data; step 507: the database returns the query result of the target data to the user; step 508: and saving the query result of the target data to a database operation log.

In an example, the persistent layer interface provides an insertByX function, a deleteByX function, an updateByX function, a selectByX function, where X is identification information of a user. The role of the user may include any of: database administrators, database operators.

Based on the same technical concept as the foregoing embodiment, referring to fig. 6, the operation log processing apparatus provided in the embodiment of the present application may include the following steps:

step A601: a target persistent layer interface is determined.

Step A602: it is determined whether an oplog annotation exists for the target persistent layer interface.

In an example, upon determining that an oplog annotation exists for the target persistent layer interface, the following step a603 is performed.

In an example, upon determining that the oplog annotation does not exist for the target persistent layer interface, the following step a607 is performed.

Step A603: and judging whether the SQL statement of the target persistent layer interface is a delete \ update statement.

In an example, when the SQL statement of the target persistent layer interface belongs to the delete \ update statement, the following step A604 is performed.

In an example, when the SQL statement of the target persistent layer interface does not belong to the delete \ update statement, the following step a607 is performed.

Step A604: and analyzing the operation log annotation corresponding to the target persistent layer interface.

Step A605: calling the operation log to annotate the persistent layer interface described by the selectSql, and acquiring the pre-operation data corresponding to the target data.

Step A606: and storing the data before operation corresponding to the target data in an operation log.

Step A607: and calling the target persistent layer interface when the target data is subjected to editing operation.

Step A608: it is determined whether an oplog annotation exists for the target persistent layer interface.

In an example, upon determining that an oplog annotation exists for the target persistent layer interface, the following step a609 is performed.

In an example, upon determining that the oplog annotation is not present for the target persistent layer interface, the following step a613 is performed.

Step A609: and judging whether the SQL statement of the target persistent layer interface is an insert \ update statement.

In an example, when the SQL statement of the target persistent layer interface belongs to the insert \ update statement, the following step A610 is performed.

In an example, when the SQL statement of the target persistent layer interface does not belong to the insert \ update statement, the following step a613 is performed.

Step A610: and analyzing the operation log annotation corresponding to the target persistent layer interface.

Step A611: and calling the operation log to annotate the persistent layer interface described by the selectSql, and acquiring the operated data corresponding to the target data.

Step A612: and storing the operated data corresponding to the target data in an operation log.

Step A613: and (6) ending.

Fig. 7 is an application scenario diagram illustrating an operation log processing method according to an embodiment of the present application. Referring to fig. 7, an operation log processing method provided in an embodiment of the present application based on a network architecture of a persistence layer, a plug-in, and a database may include the following steps:

step 701: a user query request for a data sample is received.

For example, a user initiates a query request for a data sample at a presentation layer of a front-end system to a back-end system. The presentation layer receives a user query request for a data sample.

Step 702: the back-end system queries the database for data samples.

For example, the service layer of the back-end system receives a query request of a user for the data sample, and queries the data sample in the database according to the identification information of the data sample.

Step 703: the database returns data samples to the back-end system.

For example, the database returns query results regarding the data sample to a service layer of the backend system.

Step 704: and the back-end system assembles the data sample and returns the assembled data sample to the front end.

For example, the service layer of the backend system assembles the data sample and returns the assembled data sample to the presentation layer of the frontend system.

It is to be understood that the data sample may comprise data of at least one sample. When reading the data samples, the user can select target data from the data of at least one sample as an operation object of the data editing operation. The target data may be data of any one sample, some or all of the data samples.

In an example, the operation type of the data editing operation includes any one of: insert, delete, update, modify.

Step 705: and the back-end system receives an editing operation request of a user on the target data.

For example, the presentation layer of the front-end system presents the target data, and the user can edit the target data to generate an editing operation request for the target data when reading the target data. And the back-end system receives an editing operation request of a user on the target data.

Here, the edit operation request may include identification information of the target data and information of a target persistent layer interface called when the edit operation is performed on the target data.

Step 706: and the back-end system modifies the target data in the database, and the operation log plug-in records the data snapshots before and after the target data is edited.

For example, the persistent layer of the back-end system modifies the target data in the database according to the target persistent layer interface called when the target data is edited. And the persistent layer of the back-end system acquires pre-operation data before editing operation is carried out on the target data and post-operation data after editing operation is carried out on the target data according to the operation log annotation corresponding to the target persistent layer interface, and records the pre-operation data and/or the post-operation data of the target data in the operation log.

Step 707: the back-end system returns the result of the modification of the target data to the front-end system.

For example, the persistent layer of the back-end system obtains the post-operation data after the editing operation is performed on the target data, and returns the post-operation data of the target data to the presentation layer of the front-end system.

In the related art, when the operation log function is realized, the service layer relies on the edit operation request sent by the presentation layer to perform value transfer calling, however, parameters in the edit operation request have a potential safety hazard of being tampered by a captured packet in the value transfer calling process. For the case where a change has occurred to data in the database, the pre-operation data recorded in the operation log is not a data snapshot of the real pre-operation data. Therefore, the reliability of the data snapshot of the operation log record cannot be guaranteed.

In the embodiment of the application, when the operation log function is realized, pre-operation data of target data and/or post-operation data of the target data are/is acquired according to the operation log annotation, value transfer calling is performed without depending on an editing operation request sent by a presentation layer, so that the potential safety hazard that the data are falsified by a packet capturing can be reduced, and the reliability of a data snapshot recorded by the operation log is improved.

In the following, the operation log processing method and the related art provided by the present application are contrastively analyzed with respect to a request for modifying client information.

In the related art, the presentation layer provides a query service for the client information, stores the client information in a memory space, and carries the client information obtained by the last query in an editing operation request initiated by a user. The back-end system provides the editing service of the client information, and positions and modifies the service codes of the client information table when the client information is edited. Pre-operation data is assembled, and pre-operation data of target data is newly added in an operation log; thereafter, the post-operation data is assembled, and the post-operation data of the target data is updated in the operation log. The service code of the service layer is modified and therefore, it is necessary to retest whether the service layer functions normally.

In the related art, when the presentation layer sends an editing operation request to the backend system, the editing operation request may be divided into a non-parameter request and a parameter request. When the editing operation request does not carry the operated data, the operated data cannot be recorded in the operation log. For the participatory request, the parameters in the editing operation request have the potential safety hazard of being tampered by the captured packet, so that the reliability of the data snapshot recorded by the operation log cannot be ensured by carrying out value transfer calling by relying on the editing operation request sent by the presentation layer.

In an example, an operation log annotation is added at the persistent layer interface of the updated client information table, and the operation log annotation is in the form as follows:

@LogMapping(selectSql＝"selectById",paramMapping＝"{id＝id}")

int updateCustomer(CustomerEntity entity)；

int selectById(String id)；

wherein, LogMapping indicates that the operation log needs to be recorded when the interface is called. updateCustomer () is a function of updating a persistent layer interface of the client information table, and the customerenity entry represents a Java entity class (entry) corresponding to the client information table.

In an example, when performing parameter mapping relationship parsing on the operation log annotation, the identification information of the target data in the client information table may be obtained from the Java entity class, and the identification information of the target data may be used as a selectById main key to perform parameter calling.

In an example, the oplog function is more easily implemented in a scenario of "one user requests multiple data table changes". The developer adds operation log annotation in the interface of the persistent layer, so that whether the service layer belongs to the database operation of a single operation type can be no longer concerned.

In the embodiment of the application, in the service code of the back-end system, the business code logics of a plurality of front records and back records corresponding to target data when the operation log function is realized do not need to be considered, and the operation log code is highly aggregated into the operation log plug-in. In the service code of the presentation layer, the service code logic for realizing the operation log function does not need to be considered, and the function of the presentation layer does not need to be modified when the operation log function is realized. The data before operation and the data after operation do not depend on the transmission value of the presentation layer, so the reliability of the data snapshot recorded by the operation log can be improved.

Based on the same technical concept as the foregoing embodiment, referring to fig. 8, the operation log processing apparatus provided in the embodiment of the present application may include:

a determining module 801, configured to determine a target persistent layer interface, where the target persistent layer interface is a persistent layer interface that is called when editing operation is performed on target data;

an obtaining module 802, configured to obtain an operation log annotation corresponding to the target persistent layer interface; the operation log annotation is used for representing a persistent layer query interface corresponding to the target data;

the processing module 803 is configured to, before editing operation is performed on the target data, obtain pre-operation data of the target data according to the operation log annotation; and/or after the target data is edited, acquiring the operated data of the target data according to the operation log annotation;

a storage module 804, configured to store the pre-operation data of the target data and/or the post-operation data of the target data in an operation log.

In one implementation manner, the processing module 803, configured to obtain pre-operation data of the target data according to the operation log annotation before performing an editing operation on the target data, includes:

obtaining semantic information of the target persistent layer interface;

In one implementation manner, the processing module 803, configured to obtain the post-operation data of the target data according to the operation log annotation after performing an editing operation on the target data, includes:

obtaining semantic information of the target persistent layer interface;

In one implementation, the processing module 803 is further configured to: and generating an operation log annotation corresponding to the target persistent layer interface, wherein the operation log annotation comprises the identification information of the target data and the mapping relation between the persistent layer query interfaces corresponding to the target data.

In an implementation manner, the processing module 803 is configured to obtain pre-operation data of the target data and/or post-operation data of the target data according to the operation log annotation, and includes:

In an implementation manner, the obtaining module 802 is configured to obtain an operation log annotation corresponding to the target persistent layer interface, and includes:

In an implementation manner, the processing module 803 is configured to obtain the pre-operation data of the target data and/or the post-operation data of the target data according to the operation log annotation based on a plug-in implementation.

In practical applications, the determining module 801, the obtaining module 802, the processing module 803, and the storing module 804 may all be implemented by a processor of an electronic device, where the processor may be at least one of an ASIC, a DSP, a DSPD, a PLD, an FPGA, a CPU, a controller, a microcontroller, and a microprocessor, and the embodiment of the present application is not limited thereto.

In some embodiments, functions of or modules included in the apparatus provided in the embodiments of the present application may be used to execute the method described in the above method embodiments, and specific implementation thereof may refer to the description of the above method embodiments, and for brevity, will not be described again here.

Based on the same technical concept as the foregoing embodiment, referring to fig. 9, an electronic device 900 provided in an embodiment of the present application may include: a memory 910 and a processor 920; wherein the content of the first and second substances,

a memory 910 for storing computer programs and data;

a processor 920, configured to execute the computer program stored in the memory to implement any one of the operation log processing methods in the foregoing embodiments.

In practical applications, the memory 910 may be a volatile memory (volatile memory), such as RAM; or a non-volatile memory (non-volatile memory), illustratively a ROM, a flash memory, a Hard Disk Drive (HDD) or a Solid-State Drive (SSD); or a combination of the above types of memories. The memory 910 may provide instructions and data to the processor 920.

The foregoing descriptions of the various embodiments are intended to highlight different aspects of the various embodiments, which have the same or similar aspects, and thus, for brevity, detailed descriptions thereof are omitted

The methods disclosed in the method embodiments provided by the present application can be combined arbitrarily without conflict to obtain new method embodiments.

Features disclosed in various product embodiments provided by the application can be combined arbitrarily to obtain new product embodiments without conflict.

The features disclosed in the various method or apparatus embodiments provided herein may be combined in any combination to arrive at new method or apparatus embodiments without conflict.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described device embodiments are merely illustrative, and for example, the division of the unit is only one logical function division, and there may be other division ways in actual implementation, such as: multiple units or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication between the components shown or discussed may be through some interfaces, and the indirect coupling or communication between the devices or units may be electrical, mechanical or other forms.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of grid units; some or all of the units can be selected according to actual conditions to achieve the purpose of the scheme of the embodiment.

In addition, all functional units in the embodiments of the present application may be integrated into one processing module, or each unit may be separately regarded as one unit, or two or more units may be integrated into one unit; the integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. An operation log processing method, comprising:

determining a target persistent layer interface, wherein the target persistent layer interface is called when editing operation is carried out on target data;

obtaining an operation log annotation corresponding to the target persistent layer interface; the operation log annotation is used for representing a persistent layer query interface corresponding to the target data;

2. The method of claim 1, wherein obtaining pre-operation data of the target data from the operation log annotation before performing the editing operation on the target data comprises:

obtaining semantic information of the target persistent layer interface;

3. The method of claim 1, wherein obtaining post-operation data of the target data according to the operation log annotation after the editing operation is performed on the target data comprises:

obtaining semantic information of the target persistent layer interface;

4. The method of claim 1, further comprising:

5. The method of claim 4, wherein obtaining pre-operation data of the target data and/or post-operation data of the target data from the operation log annotation comprises:

6. The method of claim 1, wherein the obtaining of the operation log annotation corresponding to the target persistent layer interface comprises:

analyzing the mapping statement corresponding to the database statement according to the grammar rule of the mapping statement to obtain an operation log annotation corresponding to the target persistent layer interface;

7. The method of claim 1, wherein the step of obtaining pre-operational data of the target data and/or post-operational data of the target data from the oplog annotation is implemented on a plug-in basis.

8. An operation log processing apparatus characterized by comprising:

9. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements the oplog processing method of any one of claims 1 to 7 when executing the program.

10. A computer storage medium storing a computer program; characterized in that the computer program is capable of implementing the oplog processing method of any one of claims 1 to 7 when executed.