CN111881102A - Method, device and readable medium for collecting audit logs based on AOP (automatic optical plane protocol) section - Google Patents
Method, device and readable medium for collecting audit logs based on AOP (automatic optical plane protocol) section Download PDFInfo
- Publication number
- CN111881102A CN111881102A CN202010741693.5A CN202010741693A CN111881102A CN 111881102 A CN111881102 A CN 111881102A CN 202010741693 A CN202010741693 A CN 202010741693A CN 111881102 A CN111881102 A CN 111881102A
- Authority
- CN
- China
- Prior art keywords
- annotation
- class
- log
- aop
- defining
- 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
- 238000000034 method Methods 0.000 title claims abstract description 76
- 238000012550 audit Methods 0.000 title claims abstract description 31
- 230000003287 optical effect Effects 0.000 title description 5
- 238000002372 labelling Methods 0.000 claims abstract description 4
- 230000005540 biological transmission Effects 0.000 claims description 3
- 238000005516 engineering process Methods 0.000 claims description 3
- 230000002688 persistence Effects 0.000 claims description 3
- 230000008878 coupling Effects 0.000 abstract description 7
- 238000010168 coupling process Methods 0.000 abstract description 7
- 238000005859 coupling reaction Methods 0.000 abstract description 7
- 230000006870 function Effects 0.000 description 9
- 230000008569 process Effects 0.000 description 6
- 238000012423 maintenance Methods 0.000 description 4
- 238000010276 construction Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
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/10—File systems; File servers
- G06F16/18—File system types
- G06F16/1805—Append-only file systems, e.g. using logs or journals to store data
- G06F16/1815—Journaling file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a method, a device and a readable medium for collecting an audit log based on an AOP section, belongs to the technical field of log audit, and aims to solve the technical problem of isolating audit diary records from service logic so as to reduce the coupling degree between the audit diary records and the service logic. The method comprises the following steps: s100, configuring a basic class, including defining an annotation class and declaring storage parameters of the annotation class, defining an AOP tangent class and a labeling method, self-defining an enumeration class for log storage of the annotation class, and defining a log recording object class; s200, defining a common public visitLog tool class according to service requirements, customizing an attribute value according to the service requirements, and customizing a corresponding get method and a set method; and S300, marking the name of the annotation class on the corresponding method body, wherein the parameter to be stored is a member variable defined by the annotation class.
Description
Technical Field
The invention relates to the technical field of log audit, in particular to a method and a device for collecting an audit log based on an AOP (automatic optical plane) section and a readable medium.
Background
The audit diary record is a basic function, all business processes related to users require the log record, if the block function is written into each business process, code redundancy is caused, and the maintenance is very troublesome. The method has the advantages that the log recording function is extracted to form an independent module, when the log is required to be recorded in the service process, the system automatically switches the recording function into the service process, and meanwhile, later-stage upgrading and maintenance are facilitated.
Based on the above, how to isolate the audit diary record from the business logic to reduce the coupling degree between the audit diary record and the business logic is a technical problem to be solved.
Disclosure of Invention
The technical task of the invention is to provide a method, a device and a readable medium for collecting audit logs based on an AOP section to solve the problem of how to isolate audit log records from business logic so as to reduce the coupling degree between the audit log records and the business logic.
In a first aspect, the present invention provides a method for collecting audit logs based on an AOP profile, which dynamically adds log records to a program without modifying source codes through a pre-compiling manner and a dynamic agent during a running period based on the AOP profile, and the method includes the following steps:
s100, configuring basic classes, including defining annotation classes and declaring storage parameters of the annotation classes, defining AOP section classes and marking methods, self-defining enumeration classes for parameter transmission of the annotation classes, and defining log recording object classes, wherein log storage logic is stored in the method body, and attributes defined by the log recording object classes are called by the AOP section classes for log storage;
s200, defining a common public visitLog tool class according to service requirements, customizing an attribute value according to the service requirements, and customizing a corresponding get method and a set method;
and S300, marking the name of the annotation class on the corresponding method body, wherein the parameter to be stored is a member variable defined by the annotation class.
Preferably, the AOP section includes, but is not limited to, Spring frame, Spring boot frame and Spring MVC frame,
Preferably, in step S100, by defining an annotation class by @ interface, one annotation is a class, the declaration period of the annotation is denoted as RUNTIME by the permission, and the use range of the annotation modified by Target is set as METHOD, it is indicated that the annotation is marked on the METHOD name;
the member variables include:
the attribute operation type is String and is used for recording the operation type of the log;
the attribute operationType type is a self-defined enumeration value and is used for recording operations of adding, deleting, modifying and checking;
the attribute module type is String and is used for recording the module name of the operation.
Preferably, the storage parameters of the annotation class include, but are not limited to, passed parameters, log level, operation type;
operation types include, but are not limited to, select, insert, update, delete.
Preferably, in step S100, a cut-surface class is defined by @ attribute, a cut point is defined by @ Pointcut annotation, the content is an annotation class full path, surround enhancement is performed by an @ Around labeling method, which is equivalent to a methodnterpretector, and a service logic is stored in the method and stored in an audit log; timing annotation using tangent point enhancement:
@Before,@Around,@AfterReturning,@AfterThrowing,@After。
preferably, in step S100, the enumeration type OperationType is defined by enum, including but not limited to the following business operations: LOGIN ("LOGIN"), LOGOUT ("LOGOUT"), INSERT ("INSERT"), DELETE ("DELETE"), UPDATE ("UPDATE"), and SELECT ("SELECT") for adding and deleting according to business needs.
Preferably, in step S100, in the method of @ Around labeling in the AOP profile class, a log storage logic is written according to business requirements to perform persistence in a database or file recording manner, and if Annotation information of the class method and the field is to be acquired, an Annotation object is acquired by using a Java reflection technology.
In a second aspect, the present invention provides an apparatus comprising: at least one memory and at least one processor;
the at least one memory to store a machine readable program;
the at least one processor is configured to invoke the machine-readable program to perform the method of any of the first aspects.
In a third aspect, the present invention provides a readable medium, which is a computer readable medium having stored thereon computer instructions, which, when executed by a processor, cause the processor to perform the method of any of the first aspects.
The method, the device and the readable medium for collecting the audit logs based on the AOP section have the following advantages that:
1. the unified maintenance of the program function is realized through a precompilation mode and a dynamic proxy during operation, and all parts of the business logic can be isolated by utilizing AOP (automatic optical plane processing), so that the coupling degree between all parts of the business logic is reduced, the reusability of the program is improved, and the development efficiency is improved;
2. in the actual business code research and development process, a large number of codes for repeatedly writing log records exist, which do not relate to business logic, if the codes are written into each business flow, code redundancy is caused, the codes are tightly coupled with the business codes, when the requirement change of a log module is required, the log records are divided from the business logic codes through the tangent plane idea of AOP, the actions can be separated into a method for non-guiding the business logic, the codes of the business logic are not influenced when the actions are changed, the easy maintenance of the codes is improved, and the coupling degree of the codes is greatly reduced.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed for the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on the drawings without creative efforts.
The invention is further described below with reference to the accompanying drawings.
FIG. 1 is a block flow diagram of a method for collecting audit logs based on an AOP section according to embodiment 1;
FIG. 2 is a block diagram of the working flow of the method for collecting audit logs based on AOP section in embodiment 1.
Detailed Description
The present invention is further described in the following with reference to the drawings and the specific embodiments so that those skilled in the art can better understand the present invention and can implement the present invention, but the embodiments are not to be construed as limiting the present invention, and the embodiments and the technical features of the embodiments can be combined with each other without conflict.
The embodiment of the invention provides a method for collecting audit logs based on an AOP section, which is used for solving the technical problem of how to isolate audit log records from business logic so as to reduce the coupling degree between the audit log records and the business logic.
Example 1:
the invention discloses a method for collecting audit logs based on an AOP (automatic instruction processing) section, which is based on the AOP section and realizes that log records are dynamically added to a program under the condition of not modifying source codes through a pre-compiling mode and a running-period dynamic proxy, and comprises the following steps:
s100, configuring basic classes, including defining annotation classes and declaring storage parameters of the annotation classes, defining AOP section classes and marking methods, self-defining enumeration classes for parameter transmission of the annotation classes, and defining log recording object classes, wherein log storage logic is stored in the method body, and attributes defined by the log recording object classes are called by the AOP section classes for log storage;
s200, defining a common public visitLog tool class according to service requirements, customizing an attribute value according to the service requirements, and customizing a corresponding get method and a set method;
and S300, marking the name of the annotation class on the corresponding method body, wherein the parameter needing to be stored is a member variable defined by the annotation class.
Establishing a basic dependence tool class and a related code in step S100, defining an annotation class by using @ interface, wherein one annotation is a class, marking the declaration period of the annotation as RUNTIME by the Retention, and marking the application range of the annotation as METHOD by Target modification, wherein the METHOD name is marked for marking; the member variables include:
the attribute operation type is String and is used for recording the operation type of the log;
the attribute operationType type is a self-defined enumeration value and is used for recording operations of adding, deleting, modifying and checking;
the attribute module type is String and is used for recording the module name of the operation.
Storage parameters of annotation classes include, but are not limited to, passed parameters, log level, operation type; operation types include, but are not limited to, select, insert, update, delete.
Defining a tangent class by @ Aspect, defining a tangent point by @ Pointcut annotation, wherein the content is an annotation class full path, performing surrounding enhancement by an @ arc marking method, which is equivalent to a MethodInterpreter, and storing service logic in a body of the method and storing the service logic in an audit log; timing annotation using tangent point enhancement:
@Before,@Around,@AfterReturning,@AfterThrowing,@After。
enumerating class OperationType by enum definition, including but not limited to the following business operations: LOGIN ("LOGIN"), LOGOUT ("LOGOUT"), INSERT ("INSERT"), DELETE ("DELETE"), UPDATE ("UPDATE"), and SELECT ("SELECT") for adding and deleting according to business needs.
In step S200, a common public visitLog tool class is defined according to a basic dependency writing service code, an attribute value is freely defined according to a service requirement, and a corresponding get and set method is defined, and a database or file record is performed in a method body of @ Around label in a section class according to a service requirement writing log storage logic for persistence, and it is noted that if a class method and Annotation information of a field need to be acquired, an Annotation object must be acquired by using a Java reflection technology because there is no other method for acquiring an Annotation object besides you.
As the two steps finish the construction of the AOP section self-defined annotation, when the business method needs to be used, the name of the annotation class is marked on the corresponding method body (the name of the @ annotation class), and the parameters needing to be stored and the member variables defined in the annotation class are required.
The log record and the applied service logic are separated through the AOP section thought in the three steps, the coupling degree between the log record and the applied service logic is reduced, and meanwhile, the development efficiency is improved.
Example 2:
an embodiment of the present invention provides an apparatus, including: at least one memory and at least one processor; the at least one memory for storing a machine-readable program; the at least one processor is used for calling the machine readable program and executing the method disclosed by the embodiment 1.
It is to be understood that the illustrated construction of the embodiments of the invention is not to be construed as limiting the apparatus in any way. In other embodiments of the invention, an apparatus may include more or fewer components than shown, or some components may be combined, some components may be separated, or a different arrangement of components may be used. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.
Because the information interaction, execution process, and other contents between the units in the device are based on the same concept as the method embodiment of the present invention, specific contents may refer to the description in the method embodiment of the present invention, and are not described herein again.
Example 3:
an embodiment of the present invention further provides a readable medium, which is a computer readable medium, where computer instructions are stored on the computer readable medium, and when the computer instructions are executed by a processor, the processor is caused to execute the method in embodiment 1 of the present invention. Specifically, a system or an apparatus equipped with a storage medium on which software program codes that realize the functions of any of the above-described embodiments are stored may be provided, and a computer (or a CPU or MPU) of the system or the apparatus is caused to read out and execute the program codes stored in the storage medium.
In this case, the program code itself read from the storage medium can realize the functions of any of the above-described embodiments, and thus the program code and the storage medium storing the program code constitute a part of the present invention.
Examples of the storage medium for supplying the program code include a floppy disk, a hard disk, a magneto-optical disk, an optical disk (e.g., CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD + RW), a magnetic tape, a nonvolatile memory card, and a ROM. Alternatively, the program code may be downloaded from a server computer via a communications network.
Further, it should be clear that the functions of any one of the above-described embodiments may be implemented not only by executing the program code read out by the computer, but also by causing an operating system or the like operating on the computer to perform a part or all of the actual operations based on instructions of the program code.
Further, it is to be understood that the program code read out from the storage medium is written to a memory provided in an expansion board inserted into the computer or to a memory provided in an expansion unit connected to the computer, and then causes a CPU or the like mounted on the expansion board or the expansion unit to perform part or all of the actual operations based on instructions of the program code, thereby realizing the functions of any of the above-described embodiments.
It should be noted that not all steps in the above flowcharts are necessary, and some steps may be omitted according to actual needs. The execution order of the steps is not fixed and can be adjusted as required. The system structure described in the above embodiments may be a physical structure or a logical structure, that is, some modules may be implemented by the same physical entity, or some modules may be implemented by a plurality of physical entities, or some components in a plurality of independent devices may be implemented together.
In the above embodiments, the hardware unit may be implemented mechanically or electrically. For example, a hardware element may comprise permanently dedicated circuitry or logic (such as a dedicated processor, FPGA or ASIC) to perform the corresponding operations. The hardware elements may also comprise programmable logic or circuitry, such as a general purpose processor or other programmable processor, that may be temporarily configured by software to perform the corresponding operations. The specific implementation (mechanical, or dedicated permanent, or temporarily set) may be determined based on cost and time considerations.
While the invention has been shown and described in detail in the drawings and in the preferred embodiments, it is not intended to limit the invention to the embodiments disclosed, and it will be apparent to those skilled in the art that various combinations of the code auditing means in the various embodiments described above may be used to obtain further embodiments of the invention, which are also within the scope of the invention.
Claims (9)
1. A method for collecting audit logs based on an AOP section is characterized in that log records are dynamically added to a program under the condition of not modifying source codes through a pre-compiling mode and a running-period dynamic proxy based on the AOP section, and the method comprises the following steps:
s100, configuring basic classes, including defining annotation classes and declaring storage parameters of the annotation classes, defining AOP section classes and marking methods, self-defining enumeration classes for parameter transmission of the annotation classes, and defining log recording object classes, wherein log storage logic is stored in the method body, and attributes defined by the log recording object classes are called by the AOP section classes for log storage;
s200, defining a common public visitLog tool class according to service requirements, customizing an attribute value according to the service requirements, and customizing a corresponding get method and a set method;
and S300, marking the name of the annotation class on the corresponding method body, wherein the parameter to be stored is a member variable defined by the annotation class.
2. The method for collecting audit logs based on AOP section according to claim 1, wherein the AOP section includes but is not limited to Spring frame, SpringBoot frame and SpringMVC frame.
3. The METHOD for collecting audit logs based on AOP section according to claim 1 or 2, wherein in step S100, an annotation class is defined by @ interface, one annotation is a class, the declaration period of the annotation is RUNTIME by extension, the scope of use of the annotation modified by Target is METHOD, and the annotation is marked on the name of the METHOD;
the member variables include:
the attribute operation type is String and is used for recording the operation type of the log;
the attribute operationType type is a self-defined enumeration value and is used for recording operations of adding, deleting, modifying and checking;
the attribute module type is String and is used for recording the module name of the operation.
4. The method for collecting audit logs based on AOP section according to claim 3, wherein the storage parameters of the annotation class include but are not limited to delivered parameters, log level, operation type;
operation types include, but are not limited to, select, insert, update, delete.
5. The method for collecting the audit log based on the AOP section according to the claim 1 or 2, wherein in the step S100, a section class is defined by @ Aspect, a section point is defined by @ Pointcut annotation, the content is an annotation class full path, the surrounding enhancement is performed by an @ Around annotation method, which is equivalent to a MethodInterpreter, and the method stores service logic in the body and stores the audit log; timing annotation using tangent point enhancement: @ Beform, @ Around, @ AfterReturning, @ AfterThrowing, @ AfterThrower.
6. The method for collecting audit logs based on AOP section according to claim 1 or 2, wherein in step S100, an enumeration type operationType is defined by enum, including but not limited to the following business operations: LOGIN ("LOGIN"), LOGOUT ("LOGOUT"), INSERT ("INSERT"), DELETE ("DELETE"), UPDATE ("UPDATE"), and SELECT ("SELECT") for adding and deleting according to business needs.
7. The method according to claim 1 or 2, wherein in step S100, in the method of @ Around labeling in the AOP profile class, a log storage logic is written according to business requirements to perform persistence in a database or file recording manner, and if Annotation information of class methods and fields is to be obtained, an Annotation object is obtained by using Java reflection technology.
8. An apparatus, comprising: at least one memory and at least one processor;
the at least one memory to store a machine readable program;
the at least one processor, configured to invoke the machine readable program to perform the method of any of claims 1 to 7.
9. A readable medium, being a computer readable medium, having computer instructions stored thereon, which, when executed by a processor, cause the processor to perform the method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010741693.5A CN111881102A (en) | 2020-07-29 | 2020-07-29 | Method, device and readable medium for collecting audit logs based on AOP (automatic optical plane protocol) section |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010741693.5A CN111881102A (en) | 2020-07-29 | 2020-07-29 | Method, device and readable medium for collecting audit logs based on AOP (automatic optical plane protocol) section |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111881102A true CN111881102A (en) | 2020-11-03 |
Family
ID=73200970
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010741693.5A Pending CN111881102A (en) | 2020-07-29 | 2020-07-29 | Method, device and readable medium for collecting audit logs based on AOP (automatic optical plane protocol) section |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111881102A (en) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112379871A (en) * | 2020-11-17 | 2021-02-19 | 广州小鹏汽车科技有限公司 | Data processing method and device |
| CN113221182A (en) * | 2021-06-10 | 2021-08-06 | 中国银行股份有限公司 | Bank log desensitization method and device |
| CN113419775A (en) * | 2021-05-31 | 2021-09-21 | 济南浪潮数据技术有限公司 | Firmware configuration method, system, equipment and medium |
| CN113448588A (en) * | 2021-07-09 | 2021-09-28 | 天津狮拓信息技术有限公司 | Data security processing method and device, electronic equipment and storage medium |
| CN113779638A (en) * | 2021-11-15 | 2021-12-10 | 浪潮软件股份有限公司 | Method and device for realizing interface caller authentication in dynamic proxy mode |
| CN113778779A (en) * | 2020-11-18 | 2021-12-10 | 北京京东拓先科技有限公司 | Data interface monitoring method, system, device, electronic equipment and medium |
| CN113867913A (en) * | 2021-09-27 | 2021-12-31 | 平安国际智慧城市科技股份有限公司 | Business request processing method, device, equipment and storage medium for microservice |
| CN114036017A (en) * | 2021-10-25 | 2022-02-11 | 苏州臻璇数据信息技术有限公司 | Reinforcing method and device based on tangent plane technology |
| CN116610532A (en) * | 2023-07-17 | 2023-08-18 | 山东浪潮数字商业科技有限公司 | Redis client monitoring method, system, electronic equipment and storage medium |
| CN117093286A (en) * | 2023-10-17 | 2023-11-21 | 腾讯科技（深圳）有限公司 | Plug-in generation method, device, equipment and computer readable storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102810057A (en) * | 2011-05-30 | 2012-12-05 | 中国银联股份有限公司 | Log recording method |
| CN109240665A (en) * | 2018-08-24 | 2019-01-18 | 北京北信源信息安全技术有限公司 | Log recording method, device and electronic equipment |
| CN110489310A (en) * | 2018-09-25 | 2019-11-22 | 北京数聚鑫云信息技术有限公司 | A kind of method, apparatus, storage medium and computer equipment recording user's operation |
-
2020
- 2020-07-29 CN CN202010741693.5A patent/CN111881102A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102810057A (en) * | 2011-05-30 | 2012-12-05 | 中国银联股份有限公司 | Log recording method |
| CN109240665A (en) * | 2018-08-24 | 2019-01-18 | 北京北信源信息安全技术有限公司 | Log recording method, device and electronic equipment |
| CN110489310A (en) * | 2018-09-25 | 2019-11-22 | 北京数聚鑫云信息技术有限公司 | A kind of method, apparatus, storage medium and computer equipment recording user's operation |
Non-Patent Citations (1)
| Title |
|---|
| HOLLIS: "一个简单的例子，学习自定义注解和AOP", 《微信文章》 * |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112379871A (en) * | 2020-11-17 | 2021-02-19 | 广州小鹏汽车科技有限公司 | Data processing method and device |
| CN113778779B (en) * | 2020-11-18 | 2024-04-16 | 北京京东拓先科技有限公司 | Monitoring method, system, device, electronic equipment and medium of data interface |
| CN113778779A (en) * | 2020-11-18 | 2021-12-10 | 北京京东拓先科技有限公司 | Data interface monitoring method, system, device, electronic equipment and medium |
| CN113419775A (en) * | 2021-05-31 | 2021-09-21 | 济南浪潮数据技术有限公司 | Firmware configuration method, system, equipment and medium |
| CN113221182A (en) * | 2021-06-10 | 2021-08-06 | 中国银行股份有限公司 | Bank log desensitization method and device |
| CN113448588B (en) * | 2021-07-09 | 2024-04-16 | 天津狮拓信息技术有限公司 | Data security processing method and device, electronic equipment and storage medium |
| CN113448588A (en) * | 2021-07-09 | 2021-09-28 | 天津狮拓信息技术有限公司 | Data security processing method and device, electronic equipment and storage medium |
| CN113867913A (en) * | 2021-09-27 | 2021-12-31 | 平安国际智慧城市科技股份有限公司 | Business request processing method, device, equipment and storage medium for microservice |
| CN114036017A (en) * | 2021-10-25 | 2022-02-11 | 苏州臻璇数据信息技术有限公司 | Reinforcing method and device based on tangent plane technology |
| CN113779638A (en) * | 2021-11-15 | 2021-12-10 | 浪潮软件股份有限公司 | Method and device for realizing interface caller authentication in dynamic proxy mode |
| CN116610532A (en) * | 2023-07-17 | 2023-08-18 | 山东浪潮数字商业科技有限公司 | Redis client monitoring method, system, electronic equipment and storage medium |
| CN116610532B (en) * | 2023-07-17 | 2023-10-27 | 山东浪潮数字商业科技有限公司 | Redis client monitoring method, system, electronic equipment and storage medium |
| CN117093286A (en) * | 2023-10-17 | 2023-11-21 | 腾讯科技（深圳）有限公司 | Plug-in generation method, device, equipment and computer readable storage medium |
| CN117093286B (en) * | 2023-10-17 | 2024-01-12 | 腾讯科技（深圳）有限公司 | Plug-in generation method, device, equipment and computer readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111881102A (en) | Method, device and readable medium for collecting audit logs based on AOP (automatic optical plane protocol) section | |
| CA2777443C (en) | Automated enterprise software development | |
| US7539985B2 (en) | Systems and methods for dynamic component versioning | |
| US7607126B2 (en) | System and method for external override of annotations | |
| US9104794B2 (en) | Automatic incremental application dependency discovery through code instrumentation | |
| US7913245B2 (en) | Apparatus, system and method for modular distribution and maintenance of non-“object code only” dynamic components | |
| US20080270974A1 (en) | Enterprise JavaBeans Metadata Model | |
| US20050262475A1 (en) | System and method for descriptor classes | |
| US20130111457A1 (en) | Systems and methods for composing or decomposing a composite image for firmware update images | |
| KR20080084966A (en) | Conforming web services to an updated contract | |
| US20080065664A1 (en) | Computer-implemented method, tool, and program product for more efficiently utilizing java resource bundles | |
| US20060117298A1 (en) | Stacked file systems and methods | |
| CN110941443B (en) | Method and device for modifying file name in SDK (software development kit) and electronic equipment | |
| US7506068B2 (en) | Method, apparatus and system for transforming, converting and processing messages between multiple systems | |
| US10782944B2 (en) | Optimizing a cache of compiled expressions by removing variability | |
| CN117008934A (en) | Method, device, equipment and medium for automatically making mirror image of information creation operating system | |
| CN114398102B (en) | Application package generation method and device, compiling server and computer readable storage medium | |
| US20050273755A1 (en) | Scripting engine for network communication software | |
| US7007273B2 (en) | Object oriented model of preloading software | |
| CN115268861A (en) | Introduction method, system, equipment and storage medium of custom component | |
| CN111427581B (en) | Method, device, equipment and medium for realizing type multi-inheritance | |
| CN114895880A (en) | Code generation method and device and computer readable medium | |
| CN114138777A (en) | Database and table dividing method and device, electronic equipment and storage medium | |
| US20040216140A1 (en) | Method and system for accessing system operations through an interface layer | |
| US20100061382A1 (en) | Method, apparatus and computer program for processing a message using a message processing node |
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: 20201103 |