CN105912455B - Business executes method and server - Google Patents
Business executes method and server Download PDFInfo
- Publication number
- CN105912455B CN105912455B CN201610272164.9A CN201610272164A CN105912455B CN 105912455 B CN105912455 B CN 105912455B CN 201610272164 A CN201610272164 A CN 201610272164A CN 105912455 B CN105912455 B CN 105912455B
- Authority
- CN
- China
- Prior art keywords
- log
- service
- server
- annotation
- execution
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 48
- 230000002159 abnormal effect Effects 0.000 claims description 6
- 230000005540 biological transmission Effects 0.000 claims description 4
- 230000008878 coupling Effects 0.000 abstract description 10
- 238000010168 coupling process Methods 0.000 abstract description 10
- 238000005859 coupling reaction Methods 0.000 abstract description 10
- 230000008569 process Effects 0.000 description 17
- 230000007246 mechanism Effects 0.000 description 6
- 239000000284 extract Substances 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 238000005538 encapsulation Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000004806 packaging method and process Methods 0.000 description 2
- 238000003672 processing method Methods 0.000 description 2
- 230000009467 reduction Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002035 prolonged effect Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
-
- 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
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/48—Indexing scheme relating to G06F9/48
- G06F2209/483—Multiproc
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Software Systems (AREA)
- Computing Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a kind of business to execute method, including：The service server executes the corresponding main business of the service request when receiving service request, by preset main thread, judges that corresponding execute in step of each operation layer is explained with the presence or absence of the daily record for executing auxiliary business successively；If in the presence of the relevant information that the daily record is explained is sent to the preset branch thread task pool asynchronous with the main thread of the service server；While the main thread executes the main business, the data that the relevant information that the branch thread task pool explains the daily record received is encapsulated as preset format are controlled, the data of the preset format are stored into preset storage database.The invention also discloses a kind of servers.Present invention reduces the couplings between main business and auxiliary business, improve performance and expansibility that server executes business.
Description
Technical Field
The present invention relates to the technical field of servers, and in particular, to a service execution method and a server.
Background
Generally, when an Application program (APP), a Wireless Application Protocol (WAP), a Website (Website, WEB), or the like executes important business operations, a server divides an executed business into a main business and an auxiliary business, and needs to log changes of business data of each business link in the execution process of the main business, where the log recording is the execution of the auxiliary business, so as to perform track tracking or recover the business data after a business system crashes according to the recorded log. Taking an example of a service of uploading and operating an Android Package (APK) in an application store system, when an operator uploads a new version APK of an application to a server, the server needs to execute main services such as APK information analysis, application new version data creation, application main table information modification, and the like, and when the execution of the main service starts and ends, an auxiliary service needs to be executed to record changes of service data, that is, log recording is performed. Through the recorded logs, the change of the service data during APK uploading can be clearly known, and once a service system executing the service crashes suddenly, data recovery and cleaning can be carried out according to the logs.
Currently, in the process of executing the main service and the auxiliary service by the server, the main service and the auxiliary service are mixed and executed on the same thread, that is, the main service and the log record are mixed and executed on the same thread. By the method, on one hand, the high coupling of the main service and the auxiliary service is caused, and the later expansion of a service system corresponding to the server is not facilitated; on the other hand, the log recording needs to be crossed with the database, so that the service processing time is prolonged, and the performance of the server for executing the service is lost.
Disclosure of Invention
The invention mainly aims to provide a service execution method and a server, aiming at reducing the coupling between a main service and an auxiliary service and improving the service execution performance and the easy expandability of the server.
In order to achieve the above object, the present invention provides a server, including a service server, the service server including:
the judging module is used for executing the main service corresponding to the service request through a preset main thread when the service request is received, and sequentially judging whether log annotation for executing the auxiliary service exists in the executing steps corresponding to each service layer;
the transmission module is used for transmitting the related information of the log annotation to a branch thread task pool which is preset by the business server and is asynchronous with the main thread if the log annotation for executing the auxiliary business exists in the execution step corresponding to each business layer;
and the control module is used for controlling the branch thread task pool to package the received related information of the log annotation into data in a preset format while the main thread executes the main service, and storing the data in the preset format into a preset storage database.
Optionally, the server further includes a log server, and the log server includes:
and the recording module is used for starting a corresponding task thread to write the data in the preset format into a preset log database when detecting that the data in the preset format is stored in the storage database so as to record the log corresponding to the log annotation.
Optionally, each service layer includes a control layer, a service layer, and a data logic layer, where the control layer, the service layer, and the data logic layer are in a parallel relationship, and the determining module is further configured to determine whether a log annotation for executing an auxiliary service exists in an executing step corresponding to the control layer, and determine whether a log annotation for executing an auxiliary service exists in an executing step corresponding to the service layer when the service layer is called inside the control layer; and then judging whether log annotation for executing the auxiliary service exists in the execution step corresponding to the data logic layer when the data logic layer is called in the service layer.
Optionally, the related information includes parameter information and a structured query language template, the preset format includes a structured query language statement format, and the control module is further configured to control the branch thread task pool to package the parameter information into data in the structured query language statement format according to the received structured query language template.
Optionally, the annotation of the log includes inserting a log before the current step is executed, inserting a log after the current step is executed, inserting a log before and after the current step is executed, inserting a log when an exception occurs in the current step, and inserting a log after the current step is executed when a result needs to be returned.
In addition, to achieve the above object, the present invention further provides a service execution method, where the service execution method is applied to a server, the server includes a service server, the service includes a main service and an auxiliary service, and the service execution method includes the following steps:
when the business server receives a business request, executing a main business corresponding to the business request through a preset main thread, and sequentially judging whether log annotation for executing auxiliary business exists in the execution steps corresponding to each business layer;
if the log annotation exists, the related information of the log annotation is transmitted to a branch thread task pool which is preset by the business server and is asynchronous with the main thread;
and controlling the branch thread task pool to package the received related information of the log annotation into data in a preset format while the main thread executes the main service, and storing the data in the preset format into a preset storage database.
Optionally, the server further includes a log server, and the controlling the branch thread task pool to package the received related information of the log annotation into data in a preset format, and after storing the data in the preset format in a preset storage database, the controlling includes:
and when detecting that the data in the preset format is stored in the storage database, the log server starts a corresponding task thread to write the data in the preset format into a preset log database so as to record a log corresponding to the log annotation.
Optionally, each service layer includes a control layer, a service layer, and a data logic layer, where the control layer, the service layer, and the data logic layer are in a parallel relationship, and the sequentially determining whether there is a log annotation for executing the auxiliary service in the execution step corresponding to each service layer includes:
judging whether log annotation for executing the auxiliary service exists in the execution step corresponding to the control layer, and judging whether the log annotation for executing the auxiliary service exists in the execution step corresponding to the service layer when the service layer is called in the control layer; and then judging whether log annotation for executing the auxiliary service exists in the execution step corresponding to the data logic layer when the data logic layer is called in the service layer.
Optionally, the related information includes parameter information and a structured query language template, the preset format includes a structured query language statement format, and the controlling the branch thread task pool to package the received related information annotated by the log into data in the preset format includes:
and controlling the branch thread task pool to package the parameter information into data in a structured query language statement format according to the received structured query language template.
Optionally, the annotation of the log includes inserting a log before the current step is executed, inserting a log after the current step is executed, inserting a log before and after the current step is executed, inserting a log when an exception occurs in the current step, and inserting a log after the current step is executed when a result needs to be returned.
The business server executes the main business corresponding to the business request through the main thread, and transmits the related information of the log annotation to the branch thread task pool when the log annotation for executing the auxiliary business exists in the execution step corresponding to each business layer. And while the main thread executes the main service, the control branch thread task pool packages the relevant information of the log annotation into data in a preset format and stores the data in a storage database so that the log server acquires the data from the storage database and writes the data into the log database. Therefore, the main service and the auxiliary service can be executed on the main thread and the branch thread respectively, and the service server, the log server and the corresponding database are respectively arranged to store corresponding data. Compared with the prior art that the main service and the auxiliary service are mixed and executed on the same thread, the coupling between the main service and the auxiliary service is reduced, and the service execution performance and the expandability of the server are improved.
Drawings
FIG. 1 is a functional block diagram of a server according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a server executing a service according to the present invention;
FIG. 3 is a functional block diagram of another embodiment of a server according to the present invention;
fig. 4 is a flowchart illustrating a service execution method according to an embodiment of the present invention;
fig. 5 is a flowchart illustrating a service execution method according to another embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
As shown in fig. 1, a first embodiment of a server of the present invention is shown. The server of this embodiment includes a service server, which includes:
the system comprises a judging module 10, a service layer and a service layer, wherein the judging module is used for executing a main service corresponding to a service request through a preset main thread when the service request is received, and sequentially judging whether log annotation for executing an auxiliary service exists in an execution step corresponding to each service layer;
in this embodiment, the service execution method is applied to a server, where the service includes a main service and an auxiliary service, the main service is a core service of the service, and the auxiliary service is a secondary service such as a log. Optionally, in order to reduce the coupling between the main service and the auxiliary service, the main service is executed by the main thread, and the auxiliary service is executed by the branch thread, which do not interfere with each other. Meanwhile, the server is divided into a service server, a log server and the like, and the service server is correspondingly provided with a service database for storing relevant data of the core service; the log server is correspondingly provided with a log database for storing data related to log recording.
Specifically, the service server detects whether an HTTP request (i.e., a service request) from a client is received, where the HTTP request refers to a request message from the client to the server, and includes: in the message head line, the request method for the resource, the identifier of the resource and the protocol used. When the service server receives a service request sent by the client, the service server executes a main service corresponding to the service request through a preset main thread, and the judging module 10 sequentially judges whether log annotation for executing an auxiliary service exists in execution steps corresponding to each service layer, such as a control layer, a service layer, a data logic layer and the like, so as to form an annotation mode facing to a tangent plane.
Note that the annotation of the log includes inserting a log before the current step is executed, inserting a log after the current step is executed, inserting a log before and after the current step is executed, inserting a log when an exception occurs in the current step, and inserting a log after the current step is executed when a result needs to be returned.
Each log annotation corresponds to a tag, and the tags of the log annotations can be set to selectively mark the logic steps of each business layer according to the actual needs of the business. For example, the tags of the journal annotation include @ LogBeform, @ LogAfter, @ LogAround, @ LogThrow and @ LogReturn, the tags of different journal annotations have different meanings, and the tags of the same or different journal annotations can be used in an overlapping manner. Wherein,
@ LogBeform denotes inserting a log before the current step is performed;
@ LogAfter indicates that a log is inserted after the execution of the current step is finished;
@ LogAround indicates that a log is inserted before and after the current step is executed;
@ LogThrow indicates that a log is inserted when the current step execution is abnormal;
@ LogReturn indicates that if the current step needs to return a result, a log is inserted after the execution is finished.
A transmission module 20, configured to transmit, if there is a log annotation for executing an auxiliary service in an execution step corresponding to each service layer, relevant information of the log annotation to a branch thread task pool, which is preset by the service server and is asynchronous with the main thread;
after judging whether the execution step corresponding to each service layer has the log annotation for executing the auxiliary service, if the execution step corresponding to each service layer does not have the log annotation for executing the auxiliary service, the service server does not need to execute the auxiliary service through the branch thread, namely, the subsequent related steps do not need to be executed. If the execution step corresponding to each service layer has the log annotation for executing the auxiliary service, the service server calls the transmission module 20 to transmit the related information of the log annotation to a preset branch thread task pool asynchronous with the main thread. The related information of the log annotation includes annotation configuration, parameter information, SQL (structured query Language) template, Cache and other information.
The control module 30 is configured to control the branch thread task pool to package the received related information of the log annotation into data in a preset format while the main thread executes the main service, and store the data in the preset format in a preset storage database.
After the service server transmits the related information of the log annotation to the branch thread task pool, the main service is executed in the main thread, and the control module 30 controls the branch thread to execute the auxiliary service, wherein the main service and the auxiliary service are synchronously executed without mutual interference. After receiving the annotation configuration, the parameter information, the SQL template, the Cache and other information, the control module 30 controls the task pool to package the received log annotation related information into data in a preset format according to the reflection mechanism, so as to assemble the log corresponding to the log annotation. The preset format data can comprise data in SQL statement format, and the reflection mechanism can be defined as dynamically extracting the related information of the log annotation to write the log. The control module 30 then stores the data in the preset format in a preset storage database, which may be a Redis storage queue. Therefore, the main thread is concentrated in the core service processing, the core service is not damaged, the asynchronous branch thread processes the log data, the time consumption of service processing can be reduced to a great extent, and the service processing performance of the server is improved. It should be noted that the storage database (i.e., the Redis storage queue) may be set in the service server, or may be set separately, corresponding to the storage database, for storing data in a preset format.
For example, as shown in fig. 2, the server includes a service server and a log server, the service server is configured with a main service database, the log server is configured with a log storage database, and the storage database (i.e., a Redis storage queue) is separately configured. Specifically, when a service request arrives at a service server, the control layer is entered first, the main thread executes corresponding steps, and whether log annotation exists in the corresponding steps is judged in the process of executing the steps; if the log annotation exists, the related information of the log annotation is obtained in a log annotation mode facing to the tangent plane, and the related information of the log annotation is transmitted to the branch thread task pool. When the internal part of the control layer relates to the calling of the service layer, whether log annotation exists in the step corresponding to the service layer or not is judged in the process of triggering and executing the related step of the service layer, if so, the related information of the log annotation is obtained in a log annotation mode facing to the tangent plane, and the related information of the log annotation is transmitted to the branch thread task pool. Similarly, when the service layer refers to the call of the data logic layer, the processing method of the log annotation is the same as that of the service layer. Data generated by the main thread executing the main business operation is stored in the main business database. And after receiving the related information of the log annotation, the branch thread task pool encapsulates the log in the SQL statement format according to the related information to form data in the SQL statement format according to a reflection mechanism, and pushes the data in the SQL statement format into a storage database, wherein the branch thread task pool is equivalent to a class producer. And a thread task pool of the log server monitors whether data exists in a storage database in real time, wherein the thread task pool is equivalent to a class consumer. When data exists in the storage database, the thread task pool starts corresponding number of branch threads, takes out the data in the SQL statement format in the storage database, and executes the operation of writing the log into the log storage database.
The service server monitors the log annotation of the three service levels when the main thread executes the main service, so as to realize the decoupling of the main service and the auxiliary service execution, and the package of the log information corresponding to the log annotation is processed by the branch thread task pool; the packaged log information is transmitted to a storage database in a producer mode. The log recording server continuously extracts the running log information from the storage database in a consumer mode and writes the running log information into an independent log storage database. Therefore, on the basis of decoupling the execution of the main service and the auxiliary service by using a section-oriented annotation mode, the main service database is separated from the log storage database, and the processing speed of the main service can be accelerated; and the execution of the main service, the encapsulation of the log information and the reading and writing of the log by the log server are synchronously executed, so that the time consumption for executing the service is shortened, and the integral execution efficiency of the service function is accelerated.
The business server executes the main business corresponding to the business request through the main thread, and transmits the related information of the log annotation to the branch thread task pool when the log annotation for executing the auxiliary business exists in the execution step corresponding to each business layer. And while the main thread executes the main service, the control branch thread task pool packages the relevant information of the log annotation into data in a preset format and stores the data in a storage database so that the log server acquires the data from the storage database and writes the data into the log database. Therefore, the main service and the auxiliary service can be executed on the main thread and the branch thread respectively, and the service server, the log server and the corresponding database are respectively arranged to store corresponding data. Compared with the prior art that the main service and the auxiliary service are mixed and executed on the same thread, the coupling between the main service and the auxiliary service is reduced, the service execution performance and the expandability of the server are improved, and the purpose of improving the user experience is achieved.
Further, as shown in fig. 3, a second embodiment of the server of the present invention is proposed based on the first embodiment of the server, and the second embodiment is different from the first embodiment in that the server further includes a log server in the second embodiment, where the log server includes:
and the recording module 40 is configured to, when it is detected that the data in the preset format is stored in the storage database, start a corresponding task thread to write the data in the preset format into a preset log database, so as to record a log corresponding to the log annotation.
In this embodiment, the server further includes a log server, and the log server detects data in a storage database (i.e., a Redis storage queue) in real time. After the business server stores the data in the preset format in the preset storage database, and when the log server detects that the data in the preset format is stored in the storage database, the recording module 40 starts a corresponding number of task threads to write the data in the preset format into the preset log database, so as to record the log corresponding to the log annotation, an embodiment of a specification for recording the log in the log storage database is shown in table 1, it can be understood that the specification for recording the log in table 1 can also be set according to actual needs, and the invention is not limited thereto.
It should be noted that the number of branch threads in the task thread pool of the log server is limited, the maximum threshold of the number of task threads in the task thread pool can be flexibly set according to specific situations, and the log server can only start the number of branch threads up to the maximum threshold. In the process of starting the branch thread, the corresponding branch thread can be recycled along with the reduction of the data in the storage database. For example, when the data in the preset format is the data in the SQL statement format, the recording module 40 starts a branch thread to fetch the data in the SQL statement format in the database when detecting that the data in the SQL statement format is stored in the database, and stores the data in the log storage database.
TABLE 1 specification of logging in a Log storage database
In the process of executing the service by the existing server, the main service and the auxiliary service are coupled and staggered together and executed in a serial mode, so the time consumed by the execution of the auxiliary service invisibly increases the processing time of the whole service, and the performance of the corresponding execution system of the server is lost. For example, the time T0 required for the service execution to be completed is 5 seconds, where the time T1 for the main service execution is 3.3 seconds, and the time T2 for the auxiliary service execution is 1.7 seconds.
In the embodiment, on the basis of decoupling the execution of the main service and the auxiliary service by using the section-oriented annotation mode, the main service and the auxiliary service are asynchronously executed, so that the time consumption for executing the auxiliary service is shortened or even eliminated, and the overall execution efficiency of the service function is accelerated. For example, the time T1 consumed for the main service execution is 3.3 seconds, and the time T2 consumed for the auxiliary service execution is 1.7 seconds, which do not interfere with each other.
In this embodiment, the log server extracts data in the storage database, and starts a corresponding task thread to write the data into the log database, so as to record a log corresponding to the log annotation. The coupling between the main service and the auxiliary service is reduced, so that the main thread is concentrated in executing the main service, the branch thread executes the auxiliary service, the time consumption of the whole service processing is reduced, and the service processing performance of the server is improved.
Further, a third embodiment of the server according to the present invention is provided based on the first embodiment of the server, where the third embodiment is different from the first embodiment in that the determining module 10 in the third embodiment is further configured to determine whether a log annotation for executing the auxiliary service exists in the executing step corresponding to the control layer, and when the service layer is called inside the control layer, determine whether a log annotation for executing the auxiliary service exists in the executing step corresponding to the service layer; and then judging whether log annotation for executing the auxiliary service exists in the execution step corresponding to the data logic layer when the data logic layer is called in the service layer.
In this embodiment, each service layer includes a control layer, a service layer, and a data logic layer, and in the process that the determining module 10 determines whether there is a log annotation for executing the auxiliary service in the execution step corresponding to each service layer, when a service request reaches the service server, the service server first enters the control layer (i.e., a Controller layer) and calls a preset monitoring program to determine whether there is a log annotation in the corresponding step. If the log annotation exists, the related information of the log annotation is obtained in a log annotation mode facing to the section, and the related information of the log annotation, such as annotation configuration, parameter information, an SQL template, Cache and the like, is transmitted to a branch thread task pool asynchronous with the main thread. When the inside of the Controller layer relates to the calling of a Service layer (namely, the Service layer), before and after the step of triggering the Service layer is executed, the monitoring program can judge whether log annotation exists in the step corresponding to the Service layer, if so, the related information of the log annotation is obtained in a log annotation mode facing to a tangent plane, and the related information of the log annotation, such as annotation configuration, parameter information, an SQL template, Cache and the like, is transmitted into a branch thread task pool. Similarly, when the Service layer relates to the calling of a data logic layer (namely, a Dao layer), whether log annotation exists in the step corresponding to the Dao layer is judged, if so, the related information of the log annotation is obtained in a log annotation mode facing to a tangent plane, and the related information of the log annotation such as annotation configuration, parameter information, an SQL template, Cache and the like is transmitted to the branch thread task pool. For example, during the execution of a step at the Controller layer, when there is a @ logbeform annotation, a log is inserted before the current step is executed. In the step execution process of the Service layer, when the @ LogThrow annotation exists, a log is inserted when the current step execution is abnormal. During the execution of the steps of the Dao layer, when the @ LogAround note exists, a log is inserted before and after the execution of the current step.
In the embodiment, in the execution steps corresponding to each service layer, such as the control layer, the service layer, the data logic layer and the like, whether log annotation for executing the auxiliary service exists in the execution steps corresponding to each service layer is judged, so that the related information of the log annotation is transmitted to the branch thread task pool, the execution of the main service and the auxiliary service is decoupled in a section-oriented log annotation mode, and the convenience of service execution of the service server is improved.
Further, a fourth embodiment of the server according to the present invention is provided based on the first embodiment of the server, and the difference between the fourth embodiment and the first embodiment is that the control module 30 in the fourth embodiment is further configured to control the branch thread task pool to encapsulate the parameter information into data in an SQL statement format according to the received SQL template.
In this embodiment, the log annotation related information includes annotation configuration, parameter information, an SQL template, Cache, and the like, and the preset format data includes data in an SQL statement format. The service server controls the branch thread to execute the auxiliary service while the main thread executes the main service. Specifically, after the control module 30 controls the sub-thread task pool to receive the annotation configuration, the parameter information, the SQL template, the Cache, and the like, the corresponding log annotation can be obtained according to the received annotation configuration, and corresponding operation is executed according to the log annotation. And packaging the parameter information into data in an SQL statement format according to the received SQL template. And then transmitting the data in the format of the SQL statement into a storage database.
In the embodiment, the branch thread task pool encapsulates relevant parameter information into data in an SQL statement format according to the SQL template, so that the main thread executes the main service and the branch thread executes the auxiliary task asynchronously without mutual interference, thereby greatly reducing the time consumption of service processing and improving the performance of the server on the service processing.
Correspondingly, as shown in fig. 4, a first embodiment of a service execution method according to the present invention is provided. The service execution method of the embodiment comprises the following steps:
step S10, when receiving a service request, the service server executes a main service corresponding to the service request through a preset main thread, and sequentially judges whether log annotation for executing auxiliary services exists in the execution steps corresponding to each service layer;
in this embodiment, the service execution method is applied to a server, where the service includes a main service and an auxiliary service, the main service is a core service of the service, and the auxiliary service is a secondary service such as a log. Optionally, in order to reduce the coupling between the main service and the auxiliary service, the main service is executed by the main thread, and the auxiliary service is executed by the branch thread, which do not interfere with each other. Meanwhile, the server is divided into a service server, a log server and the like, and the service server is correspondingly provided with a service database for storing relevant data of the core service; the log server is correspondingly provided with a log database for storing data related to log recording.
Specifically, the service server detects whether an HTTP request (i.e., a service request) from a client is received, where the HTTP request refers to a request message from the client to the server, and includes: in the message head line, the request method for the resource, the identifier of the resource and the protocol used. When the business server receives a business request sent by a client, the business server executes a main business corresponding to the business request through a preset main thread, and sequentially judges whether log annotation for executing auxiliary business exists in execution steps corresponding to business layers such as a control layer, a service layer, a data logic layer and the like, so that an annotation mode facing a tangent plane is formed.
Note that the annotation of the log includes inserting a log before the current step is executed, inserting a log after the current step is executed, inserting a log before and after the current step is executed, inserting a log when an exception occurs in the current step, and inserting a log after the current step is executed when a result needs to be returned.
Each log annotation corresponds to a tag, and the tags of the log annotations can be set to selectively mark the logic steps of each business layer according to the actual needs of the business. For example, the tags of the journal annotation include @ LogBeform, @ LogAfter, @ LogAround, @ LogThrow and @ LogReturn, the tags of different journal annotations have different meanings, and the tags of the same or different journal annotations can be used in an overlapping manner. Wherein,
@ LogBeform denotes inserting a log before the current step is performed;
@ LogAfter indicates that a log is inserted after the execution of the current step is finished;
@ LogAround indicates that a log is inserted before and after the current step is executed;
@ LogThrow indicates that a log is inserted when the current step execution is abnormal;
@ LogReturn indicates that if the current step needs to return a result, a log is inserted after the execution is finished.
Step S20, if the log annotation exists, the related information of the log annotation is transmitted to a branch thread task pool which is preset by the business server and is asynchronous with the main thread;
after judging whether the execution step corresponding to each service layer has the log annotation for executing the auxiliary service, if the execution step corresponding to each service layer does not have the log annotation for executing the auxiliary service, the service server does not need to execute the auxiliary service through the branch thread, namely, the subsequent related steps do not need to be executed. And if the log annotation for executing the auxiliary service exists in the execution step corresponding to each service layer, the service server transmits the related information of the log annotation to a preset branch thread task pool asynchronous with the main thread. The log annotation related information comprises annotation configuration, parameter information, an SQL template, Cache and other information.
Step S30, while the main thread executes the main service, controlling the branch thread task pool to package the received related information of the log annotation into data in a preset format, and storing the data in the preset format in a preset storage database.
After the service server transmits the related information of the log annotation to the branch thread task pool, the main service is executed in the main thread, and the auxiliary service is executed by the branch thread, wherein the main service and the auxiliary service are synchronously performed and do not interfere with each other. After receiving the information such as annotation configuration, parameter information, SQL template, Cache and the like, the task pool packages the received log annotation related information into data in a preset format according to a reflection mechanism, and realizes the assembly of the log corresponding to the log annotation. The preset format data can comprise data in SQL statement format, and the reflection mechanism can be defined as dynamically extracting the related information of the log annotation to write the log. And then the service server stores the data in the preset format into a preset storage database, wherein the storage database can be a Redis storage queue. Therefore, the main thread is concentrated in the core service processing, the core service is not damaged, the asynchronous branch thread processes the log data, the time consumption of service processing can be reduced to a great extent, and the service processing performance of the server is improved. It should be noted that the storage database (i.e., the Redis storage queue) may be set in the service server, or may be set separately, corresponding to the storage database, for storing data in a preset format.
For example, as shown in fig. 2, the server includes a service server and a log server, the service server is configured with a main service database, the log server is configured with a log storage database, and the storage database (i.e., a Redis storage queue) is separately configured. Specifically, when a service request arrives at a service server, the control layer is entered first, the main thread executes corresponding steps, and whether log annotation exists in the corresponding steps is judged in the process of executing the steps; if the log annotation exists, the related information of the log annotation is obtained in a log annotation mode facing to the tangent plane, and the related information of the log annotation is transmitted to the branch thread task pool. When the internal part of the control layer relates to the calling of the service layer, whether log annotation exists in the step corresponding to the service layer or not is judged in the process of triggering and executing the related step of the service layer, if so, the related information of the log annotation is obtained in a log annotation mode facing to the tangent plane, and the related information of the log annotation is transmitted to the branch thread task pool. Similarly, when the service layer refers to the call of the data logic layer, the processing method of the log annotation is the same as that of the service layer. Data generated by the main thread executing the main business operation is stored in the main business database. And after receiving the related information of the log annotation, the branch thread task pool encapsulates the log in the SQL statement format according to the related information to form data in the SQL statement format according to a reflection mechanism, and pushes the data in the SQL statement format into a storage database, wherein the branch thread task pool is equivalent to a class producer. And a thread task pool of the log server monitors whether data exists in a storage database in real time, wherein the thread task pool is equivalent to a class consumer. When data exists in the storage database, the thread task pool starts corresponding number of branch threads, takes out the data in the SQL statement format in the storage database, and executes the operation of writing the log into the log storage database.
The service server monitors the log annotation of the three service levels when the main thread executes the main service, so as to realize the decoupling of the main service and the auxiliary service execution, and the package of the log information corresponding to the log annotation is processed by the branch thread task pool; the packaged log information is transmitted to a storage database in a producer mode. The log recording server continuously extracts the running log information from the storage database in a consumer mode and writes the running log information into an independent log storage database. Therefore, on the basis of decoupling the execution of the main service and the auxiliary service by using a section-oriented annotation mode, the main service database is separated from the log storage database, and the processing speed of the main service can be accelerated; and the execution of the main service, the encapsulation of the log information and the reading and writing of the log by the log server are synchronously executed, so that the time consumption for executing the service is shortened, and the integral execution efficiency of the service function is accelerated.
The business server executes the main business corresponding to the business request through the main thread, and transmits the related information of the log annotation to the branch thread task pool when the log annotation for executing the auxiliary business exists in the execution step corresponding to each business layer. And while the main thread executes the main service, the control branch thread task pool packages the relevant information of the log annotation into data in a preset format and stores the data in a storage database so that the log server acquires the data from the storage database and writes the data into the log database. Therefore, the main service and the auxiliary service can be executed on the main thread and the branch thread respectively, and the service server, the log server and the corresponding database are respectively arranged to store corresponding data. Compared with the prior art that the main service and the auxiliary service are mixed and executed on the same thread, the coupling between the main service and the auxiliary service is reduced, the service execution performance and the expandability of the server are improved, and the purpose of improving the user experience is achieved.
Further, as shown in fig. 5, a second embodiment of the service execution method of the present invention is proposed based on the first embodiment of the service execution method, and the difference between the second embodiment and the first embodiment is that the second embodiment includes, after the step S30, the following steps: and when detecting that the data in the preset format is stored in the storage database, the log server starts a corresponding task thread to write the data in the preset format into a preset log database so as to record a log corresponding to the log annotation.
In this embodiment, the server further includes a log server, and the log server detects data in a storage database (i.e., a Redis storage queue) in real time. After the business server stores the data in the preset format in the preset storage database, when the log server detects that the data in the preset format is stored in the storage database, the log server starts a corresponding number of task threads to write the data in the preset format into the preset log database so as to record the log corresponding to the log annotation, and an embodiment of a specification for recording the log in the log storage database is shown in table 1.
It should be noted that the number of branch threads in the task thread pool of the log server is limited, the maximum threshold of the number of task threads in the task thread pool can be flexibly set according to specific situations, and the log server can only start the number of branch threads up to the maximum threshold. In the process of starting the branch thread, the corresponding branch thread can be recycled along with the reduction of the data in the storage database. For example, when the data in the preset format is the data in the SQL statement format, and the log server detects that one piece of data in the SQL statement format is stored in the storage database, the log server starts a branch thread to take out the data in the SQL statement format in the storage database, and stores the data in the log storage database.
In the process of executing the service by the existing server, the main service and the auxiliary service are coupled and staggered together and executed in a serial mode, so the time consumed by the execution of the auxiliary service invisibly increases the processing time of the whole service and loses the performance of the corresponding execution system of the server. For example, the time T0 required for the service execution to be completed is 5 seconds, where the time T1 for the main service execution is 3.3 seconds, and the time T2 for the auxiliary service execution is 1.7 seconds.
In the embodiment, on the basis of decoupling the execution of the main service and the auxiliary service by using the section-oriented annotation mode, the main service and the auxiliary service are asynchronously executed, so that the time consumption for executing the auxiliary service is shortened or even eliminated, and the overall execution efficiency of the service function is accelerated. For example, the time T1 consumed for the main service execution is 3.3 seconds, and the time T2 consumed for the auxiliary service execution is 1.7 seconds, which do not interfere with each other.
In this embodiment, the log server extracts data in the storage database, and starts a corresponding task thread to write the data into the log database, so as to record a log corresponding to the log annotation. The coupling between the main service and the auxiliary service is reduced, so that the main thread is concentrated in executing the main service, the branch thread executes the auxiliary service, the time consumption of the whole service processing is reduced, and the service processing performance of the server is improved.
Further, based on the first embodiment of the service execution method, a third embodiment of the service execution method of the present invention is provided, where the difference between the third embodiment and the first embodiment is that the step of sequentially determining whether there is a log annotation for executing the auxiliary service in the execution steps corresponding to each service layer in the third embodiment includes: judging whether log annotation for executing the auxiliary service exists in the execution step corresponding to the control layer, and judging whether the log annotation for executing the auxiliary service exists in the execution step corresponding to the service layer when the service layer is called in the control layer; and then judging whether log annotation for executing the auxiliary service exists in the execution step corresponding to the data logic layer when the data logic layer is called in the service layer.
In this embodiment, each service layer includes a control layer, a service layer, and a data logic layer, and in the process that the service server determines whether there is a log annotation for executing the auxiliary service in the execution step corresponding to each service layer, when a service request reaches the service server, the service server first enters the control layer (i.e., a Controller layer) and calls a preset monitoring program to determine whether there is a log annotation in the corresponding step. If the log annotation exists, the related information of the log annotation is obtained in a log annotation mode facing to the section, and the related information of the log annotation, such as annotation configuration, parameter information, an SQL template, Cache and the like, is transmitted to a branch thread task pool asynchronous with the main thread. When the inside of the Controller layer relates to the calling of a Service layer (namely, the Service layer), before and after the step of triggering the Service layer is executed, the monitoring program can judge whether log annotation exists in the step corresponding to the Service layer, if so, the related information of the log annotation is obtained in a log annotation mode facing to a tangent plane, and the related information of the log annotation, such as annotation configuration, parameter information, an SQL template, Cache and the like, is transmitted into a branch thread task pool. Similarly, when the Service layer relates to the calling of a data logic layer (namely, a Dao layer), whether log annotation exists in the step corresponding to the Dao layer is judged, if so, the related information of the log annotation is obtained in a log annotation mode facing to a tangent plane, and the related information of the log annotation such as annotation configuration, parameter information, an SQL template, Cache and the like is transmitted to the branch thread task pool. For example, during the execution of a step at the Controller layer, when there is a @ logbeform annotation, a log is inserted before the current step is executed. In the step execution process of the Service layer, when the @ LogThrow annotation exists, a log is inserted when the current step execution is abnormal. During the execution of the steps of the Dao layer, when the @ LogAround note exists, a log is inserted before and after the execution of the current step.
In the embodiment, in the execution steps corresponding to each service layer, such as the control layer, the service layer, the data logic layer and the like, whether log annotation for executing the auxiliary service exists in the execution steps corresponding to each service layer is judged, so that the related information of the log annotation is transmitted to the branch thread task pool, the execution of the main service and the auxiliary service is decoupled in a section-oriented log annotation mode, and the convenience of service execution of the service server is improved.
Further, based on the first embodiment of the service execution method, a fourth embodiment of the service execution method of the present invention is provided, where a difference between the fourth embodiment and the first embodiment is that the step of controlling the branch thread task pool to encapsulate the received related information of the log annotation into data in a preset format includes: and controlling the branch thread task pool to package the parameter information into data in an SQL statement format according to the received SQL template.
In this embodiment, the log annotation related information includes annotation configuration, parameter information, an SQL template, Cache, and the like, and the preset format data includes data in an SQL statement format. The service server controls the branch thread to execute the auxiliary service while the main thread executes the main service. Specifically, after receiving the annotation configuration, the parameter information, the SQL template, the Cache and other information, the branch thread task pool may obtain the corresponding log annotation according to the received annotation configuration, and execute the corresponding operation according to the log annotation. And packaging the parameter information into data in an SQL statement format according to the received SQL template. And then transmitting the data in the format of the SQL statement into a storage database.
In the embodiment, the branch thread task pool encapsulates relevant parameter information into data in an SQL statement format according to the SQL template, so that the main thread executes the main service and the branch thread executes the auxiliary task asynchronously without mutual interference, thereby greatly reducing the time consumption of service processing and improving the performance of the server on the service processing.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only an alternative embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A server, comprising a service server, the service server comprising:
the judging module is used for executing the main service corresponding to the service request through a preset main thread when the service request is received, and sequentially judging whether log annotation for executing the auxiliary service exists in the executing steps corresponding to each service layer;
the transmission module is used for transmitting the related information of the log annotation to a branch thread task pool which is preset by the business server and is asynchronous with the main thread if the log annotation for executing the auxiliary business exists in the execution step corresponding to each business layer;
and the control module is used for controlling the branch thread task pool to package the received related information of the log annotation into data in a preset format while the main thread executes the main service, and storing the data in the preset format into a preset storage database.
2. The server of claim 1, wherein the server further comprises a log server, the log server comprising:
and the recording module is used for starting a corresponding task thread to write the data in the preset format into a preset log database when detecting that the data in the preset format is stored in the storage database so as to record the log corresponding to the log annotation.
3. The server according to claim 1, wherein each service layer includes a control layer, a service layer, and a data logic layer, wherein the control layer, the service layer, and the data logic layer are in a parallel relationship, and the determining module is further configured to determine whether a log annotation for executing the auxiliary service exists in the executing step corresponding to the control layer, and determine whether a log annotation for executing the auxiliary service exists in the executing step corresponding to the service layer when the service layer is called inside the control layer; and then judging whether log annotation for executing the auxiliary service exists in the execution step corresponding to the data logic layer when the data logic layer is called in the service layer.
4. The server according to claim 1, wherein the related information includes parameter information and a structured query language template, the preset format includes a structured query language statement format, and the control module is further configured to control the branch thread task pool to encapsulate the parameter information into data in the structured query language statement format according to the received structured query language template.
5. The server according to any one of claims 1 to 4, wherein the annotation of the log comprises inserting a log before the execution of the current step, inserting a log after the execution of the current step is finished, inserting a log before and after the execution of the current step, inserting a log when the execution of the current step is abnormal, and inserting a log after the execution is finished when the execution of the current step needs to return a result.
6. A service execution method is applied to a server, the server comprises a service server, the service comprises a main service and an auxiliary service, and the service execution method comprises the following steps:
when the business server receives a business request, executing a main business corresponding to the business request through a preset main thread, and sequentially judging whether log annotation for executing auxiliary business exists in the execution steps corresponding to each business layer;
if the log annotation exists, the related information of the log annotation is transmitted to a branch thread task pool which is preset by the business server and is asynchronous with the main thread;
and controlling the branch thread task pool to package the received related information of the log annotation into data in a preset format while the main thread executes the main service, and storing the data in the preset format into a preset storage database.
7. The business execution method of claim 6, wherein the server further comprises a log server, and the controlling the branch thread task pool packages the received related information of the log annotation into data in a preset format, and after storing the data in the preset format in a preset storage database, the controlling comprises:
and when detecting that the data in the preset format is stored in the storage database, the log server starts a corresponding task thread to write the data in the preset format into a preset log database so as to record a log corresponding to the log annotation.
8. The service execution method of claim 6, wherein each service layer comprises a control layer, a service layer and a data logic layer, wherein the control layer, the service layer and the data logic layer are in a parallel relationship, and the sequentially determining whether there is a log annotation for executing the auxiliary service in the execution step corresponding to each service layer comprises:
judging whether log annotation for executing the auxiliary service exists in the execution step corresponding to the control layer, and judging whether the log annotation for executing the auxiliary service exists in the execution step corresponding to the service layer when the service layer is called in the control layer; and then judging whether log annotation for executing the auxiliary service exists in the execution step corresponding to the data logic layer when the data logic layer is called in the service layer.
9. The business execution method of claim 6, wherein the related information comprises parameter information and a structured query language template, the preset format comprises a structured query language statement format, and the controlling the branch thread task pool to package the received related information of the log annotation into data of the preset format comprises:
and controlling the branch thread task pool to package the parameter information into data in a structured query language statement format according to the received structured query language template.
10. The business execution method of any one of claims 6 to 9, wherein the annotation of the log comprises inserting a log before the execution of the current step, inserting a log after the execution of the current step is finished, inserting a log before and after the execution of the current step, inserting a log when the execution of the current step is abnormal, and inserting a log after the execution is finished when the execution of the current step needs to return a result.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610272164.9A CN105912455B (en) | 2016-04-27 | 2016-04-27 | Business executes method and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610272164.9A CN105912455B (en) | 2016-04-27 | 2016-04-27 | Business executes method and server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105912455A CN105912455A (en) | 2016-08-31 |
| CN105912455B true CN105912455B (en) | 2018-11-02 |
Family
ID=56753037
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610272164.9A Active CN105912455B (en) | 2016-04-27 | 2016-04-27 | Business executes method and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105912455B (en) |
Families Citing this family (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106776803A (en) * | 2016-11-24 | 2017-05-31 | 北京锐安科技有限公司 | The update method and device of a kind of log recording |
| CN106649744B (en) * | 2016-12-26 | 2019-11-05 | 金蝶软件（中国）有限公司 | Log recording method and device |
| CN108628891A (en) * | 2017-03-21 | 2018-10-09 | 北京京东尚科信息技术有限公司 | Realize method, apparatus, electronic equipment and the readable storage medium storing program for executing of data buffer storage layer |
| CN107291493A (en) * | 2017-05-27 | 2017-10-24 | 北京思特奇信息技术股份有限公司 | The building method and system of a kind of Batch Processing processing framework |
| CN107766101B (en) * | 2017-09-30 | 2021-02-19 | 五八有限公司 | Method, device and equipment for processing App starting event |
| CN108011966B (en) * | 2017-12-14 | 2021-07-06 | 广东金赋科技股份有限公司 | Optimization method for compressing and uploading logs of self-service terminal |
| CN108460078B (en) * | 2018-01-08 | 2020-10-13 | 平安科技（深圳）有限公司 | Auxiliary function execution method and device, storage medium and terminal |
| CN109086034B (en) * | 2018-07-13 | 2021-07-02 | 山东恒云信息科技有限公司 | Method for realizing automatic backup of application data by AOP and Spring dependent injection |
| CN109446175A (en) * | 2018-11-12 | 2019-03-08 | 郑州云海信息技术有限公司 | A kind of method and apparatus for the log object constructing key operation |
| CN111241125B (en) * | 2020-01-08 | 2023-06-02 | 北京数培通网络科技有限公司 | Method and device for recording operation log, electronic equipment and storage medium |
| CN113661484A (en) * | 2021-08-25 | 2021-11-16 | 商汤国际私人有限公司 | Log recording method and device, electronic equipment and computer readable storage medium |
| CN114579212A (en) * | 2022-02-24 | 2022-06-03 | 北京航星永志科技有限公司 | System log recording method and device, electronic equipment and storage medium |
| CN115794195B (en) * | 2023-02-08 | 2023-04-28 | 湖南三湘银行股份有限公司 | Banking business management and maintenance method and device based on Viper framework |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103873276A (en) * | 2012-12-12 | 2014-06-18 | 中国移动通信集团浙江有限公司 | Business processing method under J2EE framework and system thereof |
| CN105119752A (en) * | 2015-09-08 | 2015-12-02 | 北京京东尚科信息技术有限公司 | Distributed log acquisition method, device and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10078575B2 (en) * | 2013-03-13 | 2018-09-18 | Microsoft Technology Licensing, Llc | Diagnostics of state transitions |
-
2016
- 2016-04-27 CN CN201610272164.9A patent/CN105912455B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103873276A (en) * | 2012-12-12 | 2014-06-18 | 中国移动通信集团浙江有限公司 | Business processing method under J2EE framework and system thereof |
| CN105119752A (en) * | 2015-09-08 | 2015-12-02 | 北京京东尚科信息技术有限公司 | Distributed log acquisition method, device and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105912455A (en) | 2016-08-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105912455B (en) | Business executes method and server | |
| CN109992465B (en) | Service tracking method, device and computer readable storage medium | |
| US8468124B2 (en) | Debugging workflows | |
| KR101986481B1 (en) | Method for automatic monitoring end to end performance of end-user and apparatus for using the same | |
| CN107171825B (en) | Repeated log filtering method for terminal | |
| CN110727581B (en) | Crash positioning method and electronic equipment | |
| CN103198007A (en) | Multi-process log output method and system | |
| CN112235396B (en) | Content processing link adjustment method, content processing link adjustment device, computer equipment and storage medium | |
| CN108920260B (en) | Interaction method and device for heterogeneous system | |
| CN105160018A (en) | Method, device and system for image copy/paste | |
| CN111984346A (en) | Method, system, device and storage medium for call chain tracking in micro-service environment | |
| CN107862040B (en) | Method and device for updating data in cache of application instance and cluster | |
| CN111200654A (en) | Client request error processing method and device | |
| CN113992644B (en) | Internet of things system based on no-service technology and data processing method thereof | |
| CN108021459B (en) | Method and device for sending dotting logs across processes | |
| CN108153597B (en) | LINUX equipment management device and method | |
| CN114201701B (en) | Method and device for identifying operating environment, storage medium, server and client | |
| CN112511609B (en) | Data transmission method, device and storage medium | |
| CN110609822A (en) | Data stream processing method, device and computer program product | |
| CN114895851A (en) | Data processing method, data processing device, storage medium and electronic equipment | |
| CN106469108A (en) | A kind of onboard system exception handling device and method | |
| CN111142960B (en) | Interface providing method, device and system | |
| CN113472878A (en) | Method and device for realizing file dragging transmission in VNC by using browser plug-in | |
| CN105204866A (en) | Equipment command calling method and system | |
| CN111541747A (en) | Data check point setting method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |