CN111522836A - Data query method and device, electronic equipment and storage medium - Google Patents
Data query method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN111522836A CN111522836A CN202010322859.XA CN202010322859A CN111522836A CN 111522836 A CN111522836 A CN 111522836A CN 202010322859 A CN202010322859 A CN 202010322859A CN 111522836 A CN111522836 A CN 111522836A
- Authority
- CN
- China
- Prior art keywords
- service request
- result
- concurrent
- request
- response result
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2453—Query optimisation
- G06F16/24532—Query optimisation of parallel queries
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24552—Database cache management
Abstract
The embodiment of the application provides a data query method, a data query device, electronic equipment and a storage medium, wherein the method comprises the following steps: determining a result identifier of a response result of the concurrent service request according to a resource address and service parameters of a service requested by the concurrent service request, inquiring whether the response result of the concurrent service request is cached in a cache space, if so, obtaining the response result of the concurrent service request from the cache space, if not, selecting a service request from the concurrent service request, inquiring data for responding to the selected service request according to the resource address and the service parameters, generating the response result of the concurrent service request according to the inquired data, and caching the response result and the result identifier of the concurrent service request in the cache space. By adopting the scheme provided by the embodiment of the application to carry out data query, the consumption of data processing resources and network resources when the server side responds to the concurrent service request can be reduced.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a data query method and apparatus, an electronic device, and a storage medium.
Background
As the user demand is more and more abundant, various service terminals can provide various services for the user. After receiving a service request sent by a user through a client, a server needs to generate a response result for the service request and send the response result to the client, so that the user obtains the requested service.
When the server generates the response result, the server needs to query data for responding to the service request, and the data that needs to be queried may exist not only in the server but also in other servers, for example, a database for providing database services.
However, when the server receives the concurrent service requests, that is, when the server receives a large number of service requests in a short time, the server may need to connect to other servers to obtain data for responding to the service requests for each service request, so that the server frequently establishes a connection with other servers and frequently performs data transmission with other servers, thereby requiring high data processing resources and network resources when the server responds to the concurrent service requests.
Disclosure of Invention
An object of the embodiments of the present application is to provide a data query method, an apparatus, an electronic device, and a storage medium, so as to reduce consumption of data processing resources and network resources when a server responds to a concurrent service request.
The specific technical scheme is as follows:
in a first aspect, an embodiment of the present application provides a data query method, which is applied to a server, and the method includes:
receiving a concurrent service request;
determining a result identifier of a response result of the concurrent service request according to the resource address and the service parameter of the service requested by the concurrent service request;
inquiring whether a response result of the concurrent service request is cached in a cache space according to the determined result identification, wherein the cache space is used for caching the response result and the result identification;
if so, obtaining a response result of the concurrent service request from the cache space;
if not, selecting one service request from the concurrent service requests, inquiring data for responding to the selected service request according to the resource address and the service parameter, generating a response result of the concurrent service request according to the inquired data, and caching the response result and the result identification of the concurrent service request in the cache space.
Optionally, after the receiving the concurrent service request, the method further includes:
determining whether the same service request has been received before the concurrent service request is received;
if the same service request is received, judging whether a response result of the same service request is successfully generated or not;
if the response result of the same service request is not successfully generated, determining the generated response result as the response result of the concurrent request after monitoring that the response result of the same service request is successfully generated; if the response results of the same service request are successfully generated, determining the response results which are successfully generated as the response results of the concurrent request;
and if the same service request is not received, executing the step of determining a result identifier of a response result of the concurrent service request according to the resource address and the service parameter of the service requested by the concurrent service request.
Optionally, the determining whether the same service request has been received before the concurrent service request is received includes:
generating a request identifier of the concurrent service request according to the resource address and the service parameter of the service requested by the concurrent service request;
judging whether the cache space has the request identification;
if the service request does not exist, storing the request identification in the cache space, and confirming that the same service request is not received;
if so, the same service request is confirmed to be received.
Optionally, the determining whether the response result of the same service request has been successfully generated includes:
judging whether the attribute value of the request identifier of the same service request is a first preset value, if so, confirming that the response result of the same service request is successfully generated, and if not, confirming that the response result of the same service request is not successfully generated, wherein the first preset value is as follows: a value representing a response result that the service request has been successfully generated;
after the generating the response result of the concurrent service request according to the queried data, the method further includes:
and setting the attribute value of the request identifier of the concurrent service request as the first preset value.
Optionally, after the setting the attribute value of the request identifier of the concurrent service request to the first preset value, the method further includes:
setting a first effective duration for the request identifier of the concurrent service request, and setting the attribute value of the request identifier of the concurrent service request to be a second preset value after the duration in which the attribute value of the request identifier of the concurrent service request is the first preset value reaches the first effective duration, wherein the second preset value is as follows: a value representing a result of a response to the unsuccessfully generated service request.
Optionally, the method further includes:
and when the storage duration of the request identifier of the concurrent service request in the cache space reaches a second effective duration, deleting the request identifier of the concurrent service request from the cache space.
Optionally, the method further includes:
and stopping monitoring when the monitoring duration for monitoring whether the response results of the same service request are successfully generated reaches the third effective duration.
Optionally, the method further includes:
and deleting the response result of the concurrent service request after the storage duration of the response result of the concurrent service request in the cache space reaches a fourth effective duration.
In a second aspect, an embodiment of the present application further provides a data query apparatus, which is applied to a server, where the apparatus includes:
a request receiving unit, configured to receive a concurrent service request;
a result identifier determining unit, configured to determine, according to the resource address and the service parameter of the service requested by the concurrent service request, a result identifier of a response result of the concurrent service request;
a result query unit, configured to query, according to the determined result identifier, whether a response result of the concurrent service request is cached in a cache space, where the cache space is used for caching the response result and the result identifier;
a result obtaining unit, configured to obtain a response result of the concurrent service request from the cache space when a query result of the result querying unit is yes;
and the data query unit is used for selecting one service request from the concurrent service requests when the query result of the result query unit is negative, querying data for responding to the selected service request according to the resource address and the service parameter, generating a response result of the concurrent service request according to the queried data, and caching the response result and the result identification of the concurrent service request in the cache space.
Optionally, the apparatus further comprises:
a request judgment unit that judges whether the same service request has been received before the concurrent service request is received;
a result judging unit configured to judge whether a response result of the same service request has been successfully generated when the judgment result of the request judging unit is yes; if the judgment result of the result judgment unit is negative, triggering the result identification determination unit to start operation;
a response result determining unit, configured to determine, when the determination result of the result determining unit is yes, the generated response result as the response result of the concurrent request after monitoring that the response result of the same service request is successfully generated; and when the judgment result of the result judgment unit is negative, determining the response result which is successfully generated as the response result of the concurrent request.
Optionally, the request determining unit includes:
an identifier generating subunit, configured to generate a request identifier of the concurrent service request according to a resource address and a service parameter of a service requested by the concurrent service request;
the identifier judging subunit is used for judging whether the cache space has the request identifier or not;
the first request confirmation subunit is used for storing the request identifier in the cache space and confirming that the same service request is not received when the judgment result of the identifier judgment subunit is negative;
and the second request confirmation subunit is used for confirming that the same service request is received when the judgment result of the identification judgment subunit is yes.
Optionally, the result determining unit is specifically configured to:
judging whether the attribute value of the request identifier of the same service request is a first preset value, if so, confirming that the response result of the same service request is successfully generated, and if not, confirming that the response result of the same service request is not successfully generated, wherein the first preset value is as follows: a value representing a response result that the service request has been successfully generated;
the device further comprises:
and the attribute value setting unit is used for setting the attribute value of the request identifier of the concurrent service request as the first preset value after the data query unit finishes executing the response result of the concurrent service request generated according to the queried data.
Optionally, the apparatus further comprises:
a duration setting unit, configured to set a first valid duration for the request identifier of the concurrent service request after the attribute value setting unit sets the attribute value of the request identifier of the concurrent service request to the first preset value, and set the attribute value of the request identifier of the concurrent service request to a second preset value after the duration in which the attribute value of the request identifier of the concurrent service request is the first preset value reaches the first valid duration, where the second preset value is: a value representing a result of a response to the unsuccessfully generated service request.
Optionally, the apparatus further comprises:
and the identifier deleting unit is used for deleting the request identifier of the concurrent service request from the cache space after the storage duration of the request identifier of the concurrent service request in the cache space reaches a second effective duration.
Optionally, the apparatus further comprises:
and the operation stop control unit is used for stopping monitoring when the monitoring time length for monitoring whether the response results of the same service request are successfully generated reaches the third effective time length.
Optionally, the apparatus further comprises:
and the result deleting unit is used for deleting the response result of the concurrent service request after the storage duration of the response result of the concurrent service request in the cache space reaches a fourth effective duration.
In a third aspect, an embodiment of the present application further provides an electronic device, including a processor, a communication interface, a memory, and a communication bus;
wherein the processor, the communication interface and the memory complete mutual communication through the communication bus,
the memory is used for storing a computer program;
the processor is configured to implement the data query method according to any one of the first aspect when executing the program stored in the memory.
In a fourth aspect, this application further provides a computer-readable storage medium, in which a computer program is stored, and when the computer program is executed by a processor, the data query method according to any one of the first aspect is implemented.
According to the technical scheme provided by the embodiment of the application, after the concurrent service request is received, the result identification of the response result of the concurrent service request is determined according to the resource address and the service parameter of the service requested by the concurrent service request, if the response result of the concurrent service request is cached in the cache space according to the result identification, the response result of the concurrent service request is obtained from the cache space, if the response result of the concurrent service request is not cached in the cache space, one service request is selected from the concurrent service request, and the data of the selected service request is inquired according to the resource address and the service parameter of the selected service request, so that the response result of the concurrent service request is obtained, and the response result and the result identification of the concurrent service request are cached in the cache space.
In the solution provided in the embodiment of the present application, after the response result and the result identifier of the concurrent service request are cached in the cache space, if a service request with a response result identical to that of the concurrent service request is received, the response result of the received service request can be directly obtained from the cache space, and it is not necessary to connect other service terminals to obtain data for responding to the received service request, so that the response speed of the service request is faster, the requirement for querying the data for responding to the service request from other service terminals is also reduced, and thus the consumption of data processing resources and network resources when the service terminal responds to the concurrent service request is reduced. In addition, because the response results of a plurality of service requests included in the concurrent service request are the same, the data query is performed on one service request in the concurrent service request, so that the response results of each service request in the concurrent service request can be obtained.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flowchart of a data query method according to an embodiment of the present application;
fig. 2 is another schematic flow chart of a data query method according to an embodiment of the present application;
fig. 3 is a flowchart illustrating a method for determining whether the same service request has been received according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a data query device according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a data query device according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a request determining unit according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In order to reduce consumption of data processing resources and network resources when a server side responds to a concurrent service request, embodiments of the present application provide a data query method, an apparatus, and an electronic device.
In one embodiment of the present application, a data query method is provided, which includes the following steps:
receiving a concurrent service request;
determining a result identifier of a response result of the concurrent service request according to the resource address and the service parameter of the service requested by the concurrent service request;
inquiring whether a response result of the concurrent service request is cached in a cache space according to the determined result identification, wherein the cache space is used for caching the response result and the result identification;
if so, obtaining a response result of the concurrent service request from the cache space;
if not, selecting one service request from the concurrent service requests, inquiring data for responding to the selected service request according to the resource address and the service parameter, generating a response result of the concurrent service request according to the inquired data, and caching the response result and the result identification of the concurrent service request in the cache space.
According to the method provided by the embodiment of the application, when data is inquired, after the response result and the result identification of the concurrent service request are cached in the cache space, if the service request with the response result identical to that of the concurrent service request is received, the response result of the received service request can be directly obtained from the cache space, other service terminals do not need to be connected to obtain data for responding to the received service request, the response speed of the service request is higher, the requirement for inquiring the data for responding to the service request from other service terminals is reduced, and therefore the consumption of data processing resources and network resources when the service terminals respond to the concurrent service request is reduced. In addition, because the response results of a plurality of service requests included in the concurrent service request are the same, the data query is performed on one service request in the concurrent service request, so that the response results of each service request in the concurrent service request can be obtained.
First, a data query method provided in the embodiment of the present application is described below.
The execution main body of the data query method provided by the embodiment of the application is the server side. The server may be a server, for example.
As shown in fig. 1, the data query method provided in the embodiment of the present application includes the following steps S110 to S150.
S110: a concurrent service request is received.
The concurrent service request includes a plurality of identical service requests, wherein the identical service requests refer to: and the resource address and the service parameter of the requested service are the same.
S120: and determining a result identifier of a response result of the concurrent service request according to the resource address of the service requested by the concurrent service request and the service parameter.
The resource address is an address in which data responding to the service request is stored, and the service parameter is a parameter required for responding to the service request.
Before determining the resource address and the service parameter of the service requested by the concurrent service request according to the resource address and the service parameter of the service requested by the concurrent service request, the server may determine the resource address and the service parameter of the service requested by the concurrent service request. In an embodiment, the concurrent service request may carry a resource address and a service parameter of the requested service, and in this case, the service end may obtain the resource address and the service parameter carried in the concurrent service request as the resource address and the service parameter of the requested service of the concurrent service request. In another embodiment, the concurrent service request may carry service parameters of the requested service, and in this case, the server may determine a resource address to be accessed by the service requested by the concurrent service request, determine the determined resource address as the resource address of the service requested by the concurrent service request, and the server may obtain the service parameters carried in the concurrent service request and determine the obtained service parameters as the service parameters of the service requested by the concurrent service request.
The Resource address may be, for example, a Uniform Resource Locator (URL).
For example, if the service requested by the concurrent service request is a profile inquiring about "zhang three", then the resource address of the service requested by the concurrent service request may be the resource address storing the profile information of "zhang three", and the service parameter may be "zhang three". The service requested by the concurrent service request is the sum of query 1 and query 2, and the resource address of the service requested by the concurrent service request may be the resource address stored with the summation calculation function, and the service parameters are 1 and 2.
In one embodiment, the result identification of the response result of the concurrent service request may be determined as follows: and carrying out hash operation on the resource address of the requested service and the service parameter to obtain a hash value, and determining the obtained hash value as a result identifier of a response result of the concurrent service request. In another embodiment, the resource address and the service parameter of the requested service may also be determined as a result identification of a response result of the concurrent service request. Other ways of determining the result identification of the result of the response of the concurrent service request may be used by those skilled in the art.
For example, the resource address of the requested service is: http:// www.sssswww.com.cn, service parameters are: and if the result is the result identifier of the response result of the concurrent service request, the hash value obtained by carrying out the hash operation on the http:// www.sssswww.com.cn zhang can be determined as the result identifier of the response result of the concurrent service request, and the result identifier of the response result of the concurrent service request can also be determined as the result identifier of the response result of the http:// www.sssswww.com.cn zhang.
Since the result identifier of the response result of the concurrent service request is determined according to the resource address and the service parameter, the result identifiers of the response results of the service requests with the same resource address and service parameter are also the same. The result identification of the response result of the service request for different resource addresses or service parameters is also different. The result identifier may be an identifier formed by any character, and the embodiment of the present application does not limit a specific representation form of the result identifier.
S130: and inquiring whether a response result of the concurrent service request is cached in the cache space or not according to the determined result identification.
The cache space is used for caching the response result and the result identification.
The cache space may be a Remote data service (Redis) database, where Redis is a key-value database of an in-memory cache, which supports rich data types, such as: string, list, set, zset, hash, and the like. According to the embodiment of the application, when the cache space is a Redis database, the response result and the result identification are more conveniently stored.
The response result and the result identifier of the response result are stored in the cache space in a corresponding relationship, that is, the response result and the result identifier corresponding to the response result are stored in the cache space.
The step S130 can be implemented as the following steps: and searching whether a result identifier which is the same as the determined result identifier exists in the cache space, if so, determining that the response result of the concurrent service request is cached in the cache space, and if not, determining that the response result of the concurrent service request is not cached in the cache space.
S140: if the determination result in step S130 is yes, a response result of the concurrent service request is obtained from the cache space.
In step S140, the response result of the concurrent service request may be obtained from the cache space according to the following steps:
and acquiring a response result corresponding to the result identifier which is the same as the determined result identifier from the cache space, and determining the acquired response result as the response result of the concurrent service request.
S150: if the judgment result in the step S130 is negative, selecting a service request from the concurrent service requests, querying data for responding to the selected service request according to the resource address and the service parameter of the service requested by the concurrent service request, generating a response result of the concurrent service request according to the queried data, and caching the response result and the result identifier of the concurrent service request in the cache space.
After the data for responding to the selected service request is queried, since each service request included in the concurrent service request is the same service request, and the data for responding to other service requests in the concurrent service request is the same as the queried data, the queried data can be determined as a response result of the concurrent service request.
In one embodiment of the present application, a service request may be randomly selected from the service requests included in the concurrent service request.
In another embodiment of the present application, an optimistic lock may be used to select a service request from the various service requests included in the concurrent service requests. According to the embodiment, the optimistic lock is used for selecting the service request, so that the database overhead can be reduced, and the overall performance of the server under large concurrency is improved.
In the data query method provided by the embodiment of the application, one service request is selected from the concurrent service requests, and data used for responding to the selected service request is queried, that is, only one service request in the concurrent service requests captures a query right, other service requests in the concurrent service requests do not capture the query right, and the service end only queries the service request used for responding to the query right captured.
According to the data query method provided by the embodiment of the application, after the response result and the result identification of the concurrent service request are cached in the cache space, if the service request with the response result identical to that of the concurrent service request is received, the response result of the received service request can be directly obtained from the cache space, other service terminals do not need to be connected to obtain data for responding to the received service request, the response speed of the service request is higher, the requirement for querying the data for responding to the service request from the other service terminals is reduced, and therefore the consumption of data processing resources and network resources when the service terminals respond to the concurrent service request is reduced. In addition, because the response results of a plurality of service requests included in the concurrent service request are the same, the data query is performed on one service request in the concurrent service request, so that the response results of each service request in the concurrent service request can be obtained.
In one embodiment, as shown in fig. 2, after step S110, the method may further include the following steps S160 to S190.
S160: it is determined whether the same service request has been received before the concurrent service request is received.
The same service request as above refers to: and the resource address of the requested service is the same as that of the service requested by the concurrent service request, and the service parameter is the same as that of the concurrent service request.
In one embodiment, step S160 can be further implemented as the following steps: and judging whether a service request which is the same as the received concurrent service request and has the receiving time not longer than the time of receiving the concurrent service request by the preset time length exists in the cache space, if so, confirming that the same service request is received before the concurrent service request is received, and if not, confirming that the same service request is not received before the concurrent service request is received. The preset time may be any time from 30 seconds to 2 minutes, for example, and a person skilled in the art may set the preset time to other specific times, and when the preset time is longer, the number of times of acquiring data from other servers may be reduced, so that the consumption of the server for data processing resources and network resources when responding to the concurrent service request is reduced, and when the preset time is shorter, the real-time performance and accuracy of data query may be higher.
In one embodiment, as shown in fig. 3, step S160 can also be implemented as the following steps S161 to S164:
s161: and generating a request identifier of the concurrent service request according to the resource address of the service requested by the concurrent service request and the service parameter.
The request identifier generation method may refer to the result identifier generation method described above. The generation method of the request identifier may be the same as or different from the generation method of the result identifier. When the result identifier and the request identifier are generated by using the same method, a first identifier may be added to the request identifier, and a second identifier may be added to the result identifier, where the first identifier is an identifier representing the request identifier, and the second identifier is an identifier representing the result identifier, so that the request identifier and the result identifier may be distinguished. When the result identifier and the request identifier are generated by using the same method, the result identifier and the request identifier may also be stored in different locations of the cache space, so that the request identifier and the result identifier may also be distinguished. For example, the result identifier is stored in the folder a, the request identifier is stored in the folder B, after the service request is received, if the query is the result identifier, the query is performed from the folder a, and if the query is the request identifier, the query is performed from the folder B.
In the present embodiment, since the request identifier of the concurrent service request is generated according to the resource address and the service parameter, the request identifiers of the service requests having the same resource address and service parameter are also the same. In particular embodiments, the request identification of service requests for different resource addresses or service parameters may also differ. The request identifier may be an identifier formed by any character, and the embodiment of the present application does not limit a specific representation form of the request identifier.
S162: and judging whether the cache space has the request identifier.
The cache space may also be used for caching the request identifier.
S163: if the determination result in step S162 is negative, the request identifier is stored in the cache space, and it is confirmed that the same service request has not been received.
S164: if the determination result in step S162 is yes, it is confirmed that the same service request has been received.
The embodiment can more quickly judge whether the same service request is received before the concurrent service request is received by generating the request identifier for the concurrent service request.
S170: if the determination result in step S160 is yes, it is determined whether the response result of the same service request has been successfully generated.
In one embodiment, the step S170 of determining whether the response result of the same service request has been successfully generated may be implemented as the following steps: and judging whether the cache space has the same result identification of the service request, if so, confirming that the response result of the same service request is successfully generated, and if not, confirming that the response result of the same service request is not successfully generated.
S180: if the determination result in the step S170 is negative, after it is monitored that the response result of the same service request is successfully generated, the generated response result is determined as the response result of the concurrent request.
When the same service request is received before the concurrent service request is received, but the response result of the same service request is not successfully generated, it indicates that data for responding to the same service request is being queried, that is, the response result of the same service request is being generated, in this case, before the response result of the same service request is generated, whether the response result of the same service request is successfully generated or not may be monitored, and when it is monitored that the response result of the same service request is successfully generated, the generated response result is directly determined as the response result of the concurrent request. In this way, there is no need to query data for responding to concurrent service requests.
In one embodiment, step S180 can be implemented as the following steps: if the determination result of the step S170 is negative, whether the response result of the same service request is successfully generated is monitored, and after the response result of the same service request is successfully generated, the generated response result is determined as the response result of the concurrent request. And stopping the monitoring operation after monitoring the response result of successfully generating the same service request.
In a specific embodiment, the server may monitor whether the response result of the same service request is successfully generated in a timing monitoring manner. For example, the server may periodically monitor whether the response result of the same service request is successfully generated at preset time intervals. The preset time interval may be, for example, any one of 0.5 seconds to 2 seconds, and for example, the preset time interval may be 1 second. The interval duration of the preset time interval is not specifically limited in the embodiment of the present application.
S190: if the determination result in step S170 is yes, the response result that has been successfully generated is determined as the response result of the concurrent request.
If the determination result in step S160 is no, step S120 is executed.
In this embodiment, if the same service request is received before the concurrent service request is received, for the same service request, the response result of the same service request has been successfully generated or is being generated, so that the response result of the same service request can be directly determined as the response result of the concurrent service request, data for responding to the service request in the concurrent service request does not need to be queried, and consumption of data processing resources and network resources by the service end in responding to the concurrent service request is reduced.
In another embodiment, if the determination result in step S160 is negative, the step S150 of selecting a service request from the concurrent service requests, querying data for responding to the selected service request according to the resource address and the service parameter, generating a response result of the concurrent service request according to the queried data, and caching the response result and the result identifier of the concurrent service request in the cache space may also be performed.
In one embodiment, after step S110, the method may further include the following steps a to B.
Step A: it is determined whether the same service request has been received before the concurrent service request is received.
And B: if the same service request is received, after the response result of the same service request is successfully generated, the generated response result is determined as the response result of the concurrent request. If not, go to step S120.
In one embodiment, the step S170 of determining whether the response result of the same service request has been successfully generated may be implemented as the following step C:
and C: judging whether the attribute value of the request identifier of the same service request is a first preset value, if so, determining that the response result of the same service request is successfully generated, and if not, determining that the response result of the same service request is not successfully generated, wherein the first preset value is as follows: a value representing a response result that the service request has been successfully generated;
accordingly, after generating a response result of the concurrent service request according to the queried data in step S150, the method may further include the following step D:
step D: and setting the attribute value of the request identifier of the concurrent service request as a first preset value.
The first preset value may be any value, for example, 1, 0, 2, 12, etc.
According to the embodiment, whether the same response result of the service request is successfully generated can be judged more conveniently and quickly through the attribute value of the identifier.
In one embodiment, after step D, the method may further comprise the following step F:
step F: setting a first effective duration for a request identifier of a concurrent service request, and setting an attribute value of the request identifier of the concurrent service request as a second preset value after the duration in which the attribute value of the request identifier of the concurrent service request is set as the first preset value reaches the first effective duration, wherein the second preset value is as follows: a value representing a result of a response to the unsuccessfully generated service request.
The second preset value is a value different from the first preset value. The first effective time period may be any one of 30 seconds to 2 minutes, or other time periods. When the state of the service request is the state of the response result of the successfully generated service request, and the first effective time length is reached, the response result of the service request is usually updated, at this time, after the attribute value of the request identifier of the service request is set to the second preset value, the updated response result can be obtained after the same request as the service request is received, and therefore the real-time performance and the accuracy of data query are higher.
When the first effective duration is set to be longer, the times of acquiring data from other servers can be reduced, so that the consumption of data processing resources and network resources when the servers respond to concurrent service requests is reduced, and when the first effective duration is set to be shorter, the real-time performance and the accuracy of data query can be higher.
In one embodiment, the method may further include the steps of: and when the storage duration of the request identifier of the concurrent service request in the cache space reaches the second effective duration, deleting the request identifier from the cache space.
The second effective time period may be any one of 30 seconds to 2 minutes, or other time periods. In this embodiment, after the storage duration of the request identifier of the concurrent service request in the cache space reaches the second effective duration, it indicates that the duration from the time of receiving the concurrent service request is longer, and at this time, the concurrent request identifier is deleted, and after other service requests identical to the concurrent service request are received, the probability that the response result determined for the received service request is a result with poor real-time performance can be reduced.
In one embodiment, the monitoring is stopped when the monitoring duration for monitoring whether the response results of the same service request have been successfully generated reaches the third validity duration.
The third effective time period may be any one of 30 seconds to 2 minutes, or other time periods. In this embodiment, if the response result that the same service request is successfully generated is not monitored after the third validity duration, it indicates that the response result that the same service request is generated fails, or even if the response result that the same service request can be generated, the real-time performance of the generated response result is poor, and at this time, the monitoring is stopped, so that the probability that the real-time performance of the obtained response result is poor can be reduced, and the invalid monitoring operation can also be reduced.
In one embodiment, the method may further include the steps of: and deleting the response result of the concurrent service request after the storage duration of the response result of the concurrent service request in the cache space reaches the fourth effective duration.
The fourth effective time period may be any one of 30 seconds to 2 minutes, or other time periods. In an embodiment, when the storage duration of the response result of the concurrent service request in the cache space reaches the fourth effective duration, it indicates that the actual response result of the concurrent service request may have been updated, and at this time, deleting the response result of the concurrent service request may reduce the probability that the response result determined for the received service request is a result with poor real-time performance after receiving other service requests identical to the concurrent service request.
In an embodiment, the first valid duration, the second valid duration, the third valid duration, and the fourth valid duration may be different durations. In order to make the real-time performance and accuracy of the response result generated by the data query higher, the first valid duration, the second valid duration, the third valid duration, and the fourth valid duration may be the same duration.
In one embodiment, the method may further include the steps of: and setting an overtime duration, and stopping data query if a response result of the concurrent service request is not queried after the time duration from the time of receiving the concurrent service request reaches the overtime duration. Therefore, the real-time performance and the effectiveness of data query can be ensured.
In an embodiment, the first valid duration, the second valid duration, the third valid duration, and the fourth valid duration may be the same as the timeout duration.
An embodiment of the present application further provides a data query device, which is applied to a server, as shown in fig. 4, the device includes:
a request receiving unit 410, configured to receive a concurrent service request;
a result identifier determining unit 420, configured to determine a result identifier of a response result of the concurrent service request according to the resource address and the service parameter of the service requested by the concurrent service request;
a result query unit 430, configured to query, according to the determined result identifier, whether a response result of the concurrent service request is cached in a cache space, where the cache space is used for caching the response result and the result identifier;
a result obtaining unit 440, configured to obtain a response result of the concurrent service request from the cache space when the query result of the result querying unit 430 is yes;
a data query unit 450, configured to select a service request from the concurrent service requests when the query result of the result query unit 430 is negative, query data for responding to the selected service request according to the resource address and the service parameter, generate a response result of the concurrent service request according to the queried data, and cache the response result and the result identifier of the concurrent service request in the cache space.
According to the data query device provided by the embodiment of the application, after the response result and the result identification of the concurrent service request are cached in the cache space, if a service request with the response result identical to that of the concurrent service request is received, the response result of the received service request can be directly obtained from the cache space, other service terminals do not need to be connected to obtain data for responding to the received service request, the response speed of the service request is higher, the requirement for querying the data for responding to the service request from the other service terminals is reduced, and therefore the consumption of data processing resources and network resources when the service terminals respond to the concurrent service request is reduced. In addition, because the response results of a plurality of service requests included in the concurrent service request are the same, the embodiment of the application performs data query on one service request in the concurrent service request, and can obtain the response result of each service request in the concurrent service request.
In one embodiment, as shown in fig. 5, the apparatus may further include:
a request judging unit 460 that judges whether the same service request has been received before the concurrent service request is received;
a result judging unit 470, configured to, when the judgment result of the request judging unit 460 is yes, judge whether the response result of the same service request has been successfully generated; if the judgment result of the result judgment unit is negative, triggering the result identification determination unit to start operation;
a response result determining unit 480, configured to, when the determination result of the result determining unit 460 is yes, determine, after monitoring that the response result of the same service request is successfully generated, the generated response result as the response result of the concurrent request; and when the judgment result of the result judgment unit is negative, determining the response result which is successfully generated as the response result of the concurrent request.
In one embodiment, as shown in fig. 6, the request determining unit 460 includes:
an identifier generating subunit 461, configured to generate a request identifier of the concurrent service request according to the resource address and the service parameter of the service requested by the concurrent service request;
an identifier determining subunit 462, configured to determine whether the cache space has the request identifier;
a first request confirmation subunit 463, configured to, when the determination result of the identifier determining subunit 462 is negative, store the request identifier in the cache space, and confirm that the same service request has not been received;
a second request confirmation subunit 464, configured to confirm that the same service request is received when the determination result of the identification determining subunit 462 is yes.
In an embodiment, the result determining unit 470 is specifically configured to:
judging whether the attribute value of the request identifier of the same service request is a first preset value, if so, confirming that the response result of the same service request is successfully generated, and if not, confirming that the response result of the same service request is not successfully generated, wherein the first preset value is as follows: a value representing a response result that the service request has been successfully generated;
the device further comprises:
and the attribute value setting unit is used for setting the attribute value of the request identifier of the concurrent service request as the first preset value after the data query unit finishes executing the response result of the concurrent service request generated according to the queried data.
In one embodiment, the apparatus further comprises:
a duration setting unit, configured to set a first valid duration for the request identifier of the concurrent service request after the attribute value setting unit sets the attribute value of the request identifier of the concurrent service request to the first preset value, and set the attribute value of the request identifier of the concurrent service request to a second preset value after the duration in which the attribute value of the request identifier of the concurrent service request is the first preset value reaches the first valid duration, where the second preset value is: a value representing a result of a response to the unsuccessfully generated service request.
In one embodiment, the apparatus further comprises:
and the identifier deleting unit is used for deleting the request identifier of the concurrent service request after the storage duration of the request identifier in the cache space reaches a second effective duration.
In one embodiment, the apparatus further comprises:
and the operation stop control unit is used for stopping the monitoring operation when the monitoring time length for monitoring whether the response results of the same service request are successfully generated reaches a third effective time length.
In one embodiment, the apparatus further comprises:
and the result deleting unit is used for deleting the response result of the concurrent service request after the storage duration of the response result of the concurrent service request in the cache space reaches a fourth effective duration.
The embodiment of the present application further provides an electronic device, as shown in fig. 7, including a processor 701, a communication interface 702, a memory 703 and a communication bus 704, where the processor 701, the communication interface 702 and the memory 703 complete mutual communication through the communication bus 704,
a memory 703 for storing a computer program;
the processor 701 is configured to implement any one of the data query methods provided above when executing the program stored in the memory 703.
The communication bus mentioned in the above electronic device may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.
The communication interface is used for communication between the electronic equipment and other equipment.
The Memory may include a Random Access Memory (RAM) or a Non-Volatile Memory (NVM), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component.
The embodiment of the application provides a computer-readable storage medium, wherein a computer program is stored in the storage medium, and when being executed by a processor, the computer program realizes the data query method provided by any one of the above items.
The embodiment of the present application further provides a computer program product containing instructions, which when run on a computer, causes the computer to execute any one of the data query methods provided above.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, as for the apparatus/electronic device/storage medium embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant points can be referred to the partial description of the method embodiment.
The above description is only for the preferred embodiment of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application are included in the protection scope of the present application.
Claims (11)
1. A data query method is applied to a server side, and comprises the following steps:
receiving a concurrent service request;
determining a result identifier of a response result of the concurrent service request according to the resource address and the service parameter of the service requested by the concurrent service request;
inquiring whether a response result of the concurrent service request is cached in a cache space according to the determined result identification, wherein the cache space is used for caching the response result and the result identification;
if so, obtaining a response result of the concurrent service request from the cache space;
if not, selecting one service request from the concurrent service requests, inquiring data for responding to the selected service request according to the resource address and the service parameter, generating a response result of the concurrent service request according to the inquired data, and caching the response result and the result identification of the concurrent service request in the cache space.
2. The method of claim 1, wherein after the receiving a concurrent service request, the method further comprises:
determining whether the same service request has been received before the concurrent service request is received;
if the same service request is received, judging whether a response result of the same service request is successfully generated or not;
if the response result of the same service request is not successfully generated, determining the generated response result as the response result of the concurrent request after monitoring that the response result of the same service request is successfully generated; if the response results of the same service request are successfully generated, determining the response results which are successfully generated as the response results of the concurrent request;
and if the same service request is not received, executing the step of determining a result identifier of a response result of the concurrent service request according to the resource address and the service parameter of the service requested by the concurrent service request.
3. The method of claim 2, wherein determining whether the same service request has been received before the concurrent service request is received comprises:
generating a request identifier of the concurrent service request according to the resource address and the service parameter of the service requested by the concurrent service request;
judging whether the cache space has the request identification;
if the service request does not exist, storing the request identification in the cache space, and confirming that the same service request is not received;
if so, the same service request is confirmed to be received.
4. The method of claim 3, wherein the determining whether the response result of the same service request has been successfully generated comprises:
judging whether the attribute value of the request identifier of the same service request is a first preset value, if so, confirming that the response result of the same service request is successfully generated, and if not, confirming that the response result of the same service request is not successfully generated, wherein the first preset value is as follows: a value representing a response result that the service request has been successfully generated;
after the generating the response result of the concurrent service request according to the queried data, the method further includes:
and setting the attribute value of the request identifier of the concurrent service request as the first preset value.
5. The method of claim 4, wherein after the setting the attribute value of the request identifier of the concurrent service request to the first preset value, the method further comprises:
setting a first effective duration for the request identifier of the concurrent service request, and setting the attribute value of the request identifier of the concurrent service request to be a second preset value after the duration in which the attribute value of the request identifier of the concurrent service request is the first preset value reaches the first effective duration, wherein the second preset value is as follows: a value representing a result of a response to the unsuccessfully generated service request.
6. The method of claim 3, further comprising:
and when the storage duration of the request identifier of the concurrent service request in the cache space reaches a second effective duration, deleting the request identifier of the concurrent service request from the cache space.
7. The method of claim 2, further comprising:
and stopping monitoring when the monitoring duration for monitoring whether the response results of the same service request are successfully generated reaches the third effective duration.
8. The method according to any one of claims 1 to 7, further comprising:
and deleting the response result of the concurrent service request after the storage duration of the response result of the concurrent service request in the cache space reaches a fourth effective duration.
9. A data query device, applied to a server, the device comprising:
a request receiving unit, configured to receive a concurrent service request;
a result identifier determining unit, configured to determine, according to the resource address and the service parameter of the service requested by the concurrent service request, a result identifier of a response result of the concurrent service request;
a result query unit, configured to query, according to the determined result identifier, whether a response result of the concurrent service request is cached in a cache space, where the cache space is used for caching the response result and the result identifier;
a result obtaining unit, configured to obtain a response result of the concurrent service request from the cache space when a query result of the result querying unit is yes;
and the data query unit is used for selecting one service request from the concurrent service requests when the query result of the result query unit is negative, querying data for responding to the selected service request according to the resource address and the service parameter, generating a response result of the concurrent service request according to the queried data, and caching the response result and the result identification of the concurrent service request in the cache space.
10. An electronic device comprising a processor, a communication interface, a memory, and a communication bus;
wherein the processor, the communication interface and the memory complete mutual communication through the communication bus,
the memory is used for storing a computer program;
the processor is configured to implement the data query method according to any one of claims 1 to 8 when executing the program stored in the memory.
11. A computer-readable storage medium, in which a computer program is stored, which, when being executed by a processor, implements the data query method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010322859.XA CN111522836B (en) | 2020-04-22 | 2020-04-22 | Data query method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010322859.XA CN111522836B (en) | 2020-04-22 | 2020-04-22 | Data query method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111522836A true CN111522836A (en) | 2020-08-11 |
| CN111522836B CN111522836B (en) | 2023-10-10 |
Family
ID=71903088
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010322859.XA Active CN111522836B (en) | 2020-04-22 | 2020-04-22 | Data query method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111522836B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112395316A (en) * | 2020-11-10 | 2021-02-23 | 杭州萤石软件有限公司 | Data query method and device |
| CN113051076A (en) * | 2021-03-23 | 2021-06-29 | 湖南快乐阳光互动娱乐传媒有限公司 | Request data processing method and device |
| CN115168690A (en) * | 2022-09-06 | 2022-10-11 | 深圳市明源云科技有限公司 | Data query method and device based on browser plug-in, electronic equipment and medium |
Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102880557A (en) * | 2012-09-13 | 2013-01-16 | 浙江金大科技有限公司 | Multistage distribution type high-speed cache of heterogeneous data source |
| EP2833307A1 (en) * | 2013-07-30 | 2015-02-04 | Google, Inc. | Handling search queries |
| CN104391862A (en) * | 2014-10-23 | 2015-03-04 | 北京锐安科技有限公司 | Method and device for updating cache data |
| CN104573128A (en) * | 2014-10-28 | 2015-04-29 | 北京国双科技有限公司 | Business data processing method, a business data processing device and server |
| CN107066570A (en) * | 2017-04-07 | 2017-08-18 | 聚好看科技股份有限公司 | Data managing method and device |
| WO2018112685A1 (en) * | 2016-12-19 | 2018-06-28 | 深圳中兴力维技术有限公司 | Method, device and system for processing high concurrent hypertext transfer protocol request |
| WO2018153256A1 (en) * | 2017-02-21 | 2018-08-30 | 贵州白山云科技有限公司 | Method and apparatus for accelerating dynamic resource access, medium, and device |
| CN108874806A (en) * | 2017-05-09 | 2018-11-23 | 广东神马搜索科技有限公司 | Data query method, apparatus and data-storage system |
| CN109150929A (en) * | 2017-06-15 | 2019-01-04 | 北京京东尚科信息技术有限公司 | Data request processing method and apparatus under high concurrent scene |
| WO2019192103A1 (en) * | 2018-04-03 | 2019-10-10 | 平安科技（深圳）有限公司 | Concurrent access control method and apparatus, terminal device, and medium |
| CN110489694A (en) * | 2019-07-30 | 2019-11-22 | 阿里巴巴集团控股有限公司 | For handling the method and system of high concurrent request |
| CN110598138A (en) * | 2018-06-12 | 2019-12-20 | 北京京东尚科信息技术有限公司 | Cache-based processing method and device |
| CN110737680A (en) * | 2019-09-23 | 2020-01-31 | 贝壳技术有限公司 | Cache data management method and device, storage medium and electronic equipment |
| CN110764920A (en) * | 2019-10-10 | 2020-02-07 | 北京美鲜科技有限公司 | Cache breakdown prevention method and annotation component thereof |
| CN110928904A (en) * | 2019-10-31 | 2020-03-27 | 北京浪潮数据技术有限公司 | Data query method and device and related components |
-
2020
- 2020-04-22 CN CN202010322859.XA patent/CN111522836B/en active Active
Patent Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102880557A (en) * | 2012-09-13 | 2013-01-16 | 浙江金大科技有限公司 | Multistage distribution type high-speed cache of heterogeneous data source |
| EP2833307A1 (en) * | 2013-07-30 | 2015-02-04 | Google, Inc. | Handling search queries |
| CN104391862A (en) * | 2014-10-23 | 2015-03-04 | 北京锐安科技有限公司 | Method and device for updating cache data |
| CN104573128A (en) * | 2014-10-28 | 2015-04-29 | 北京国双科技有限公司 | Business data processing method, a business data processing device and server |
| WO2018112685A1 (en) * | 2016-12-19 | 2018-06-28 | 深圳中兴力维技术有限公司 | Method, device and system for processing high concurrent hypertext transfer protocol request |
| WO2018153256A1 (en) * | 2017-02-21 | 2018-08-30 | 贵州白山云科技有限公司 | Method and apparatus for accelerating dynamic resource access, medium, and device |
| CN107066570A (en) * | 2017-04-07 | 2017-08-18 | 聚好看科技股份有限公司 | Data managing method and device |
| CN108874806A (en) * | 2017-05-09 | 2018-11-23 | 广东神马搜索科技有限公司 | Data query method, apparatus and data-storage system |
| CN109150929A (en) * | 2017-06-15 | 2019-01-04 | 北京京东尚科信息技术有限公司 | Data request processing method and apparatus under high concurrent scene |
| WO2019192103A1 (en) * | 2018-04-03 | 2019-10-10 | 平安科技（深圳）有限公司 | Concurrent access control method and apparatus, terminal device, and medium |
| CN110598138A (en) * | 2018-06-12 | 2019-12-20 | 北京京东尚科信息技术有限公司 | Cache-based processing method and device |
| CN110489694A (en) * | 2019-07-30 | 2019-11-22 | 阿里巴巴集团控股有限公司 | For handling the method and system of high concurrent request |
| CN110737680A (en) * | 2019-09-23 | 2020-01-31 | 贝壳技术有限公司 | Cache data management method and device, storage medium and electronic equipment |
| CN110764920A (en) * | 2019-10-10 | 2020-02-07 | 北京美鲜科技有限公司 | Cache breakdown prevention method and annotation component thereof |
| CN110928904A (en) * | 2019-10-31 | 2020-03-27 | 北京浪潮数据技术有限公司 | Data query method and device and related components |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112395316A (en) * | 2020-11-10 | 2021-02-23 | 杭州萤石软件有限公司 | Data query method and device |
| CN112395316B (en) * | 2020-11-10 | 2023-08-29 | 杭州萤石软件有限公司 | Data query method and device |
| CN113051076A (en) * | 2021-03-23 | 2021-06-29 | 湖南快乐阳光互动娱乐传媒有限公司 | Request data processing method and device |
| CN115168690A (en) * | 2022-09-06 | 2022-10-11 | 深圳市明源云科技有限公司 | Data query method and device based on browser plug-in, electronic equipment and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111522836B (en) | 2023-10-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111522836B (en) | Data query method and device, electronic equipment and storage medium | |
| CN108647240B (en) | Method and device for counting access amount, electronic equipment and storage medium | |
| CN108111325B (en) | Resource allocation method and device | |
| CN110572390A (en) | Method, device, computer equipment and storage medium for detecting domain name hijacking | |
| CN111367672A (en) | Data caching method and device, electronic equipment and computer storage medium | |
| CN110430070B (en) | Service state analysis method, device, server, data analysis equipment and medium | |
| CN110311975B (en) | Data request processing method and device | |
| CN108154024B (en) | Data retrieval method and device and electronic equipment | |
| CN113315852B (en) | Domain name resolution method, device and system | |
| CN111355765B (en) | Network request processing and sending method and device | |
| CN109246234B (en) | Image file downloading method and device, electronic equipment and storage medium | |
| CN112866062B (en) | Distributed pressure test system, method, device, equipment and storage medium | |
| CN110891090B (en) | Request method, device, server, system and storage medium | |
| CN110727895B (en) | Sensitive word sending method and device, electronic equipment and storage medium | |
| CN113656178B (en) | Data processing method, device, equipment and readable storage medium | |
| CN109525654B (en) | Data acquisition and sending method, device, client and server | |
| CN109189813B (en) | Data sharing method and device | |
| CN108737493B (en) | Address allocation method and device and electronic equipment | |
| CN113918776B (en) | Data caching method and device, electronic equipment and data query method | |
| CN111339170A (en) | Data processing method and device, computer equipment and storage medium | |
| CN110865845B (en) | Method for improving interface access efficiency and storage medium | |
| CN111104376B (en) | Resource file query method and device | |
| CN111522714A (en) | Log query method and device, electronic equipment and storage medium | |
| CN113746868B (en) | Method, device, equipment and medium for optimizing server performance | |
| CN111061543A (en) | Multi-tenant workflow engine service method, device and server |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |