CN113765972A

CN113765972A - Data request response method, device, system, server and storage medium

Info

Publication number: CN113765972A
Application number: CN202011162711.0A
Authority: CN
Inventors: 何武
Original assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Wodong Tianjun Information Technology Co Ltd
Current assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Wodong Tianjun Information Technology Co Ltd
Priority date: 2020-10-27
Filing date: 2020-10-27
Publication date: 2021-12-07

Abstract

The embodiment of the invention discloses a data request response method, a device, a system, a server and a storage medium, wherein the method is applied to an intermediate server and comprises the following steps: receiving a data request sent by a current client; sending the data request to a background server so that the background server returns first response data corresponding to the data request through a corresponding data interface, wherein the background server corresponds to the data interface one by one; and processing the first response data based on the current client type corresponding to the current client to obtain second response data matched with the current client type, and sending the second response data to the current client. By the technical scheme of the embodiment of the invention, the development workload can be reduced and the development efficiency can be improved on the premise of meeting the data requirements of different types of clients.

Description

Data request response method, device, system, server and storage medium

Technical Field

The embodiment of the invention relates to the internet technology, in particular to a data request response method, a data request response device, a data request response system, a data request response server and a storage medium.

Background

With the rapid development of internet technology, more and more types of clients are developed, such as Web pages, mobile H5 pages, applets, etc., to meet the increasing user demands.

Typically, the data required by different types of clients also differs. For example, when the user information is displayed, the mobile terminal H5 page is smaller than the display area of the Web page due to the limitation of the size of the mobile terminal screen, and thus, the user information data required to be acquired is less. For this reason, in order to enable the same background server to provide data services for different types of clients, different data interfaces need to be developed for the background server for the different types of clients, so that the background server can return response data matched with the types of the clients through the corresponding data interfaces, thereby satisfying the data requirements of the different types of clients.

However, in the process of implementing the present invention, the inventor finds that at least the following problems exist in the prior art:

when a new type of client is added, a new data interface needs to be developed for the background server so as to return response data matched with the type through the newly added data interface, thereby greatly increasing the development workload and reducing the development efficiency.

Disclosure of Invention

The embodiment of the invention provides a data request response method, a data request response device, a data request response system, a data request response server and a storage medium, so that the development workload is reduced and the development efficiency is improved on the premise of meeting the data requirements of different types of clients.

In a first aspect, an embodiment of the present invention provides a data request response method, applied to an intermediate server, including:

receiving a data request sent by a current client;

sending the data request to a background server so that the background server returns first response data corresponding to the data request through a corresponding data interface, wherein the background server corresponds to the data interface one by one;

and performing data processing on the first response data based on the current client type corresponding to the current client to obtain second response data matched with the current client type, and sending the second response data to the current client.

In a second aspect, an embodiment of the present invention further provides a data request response method, applied to a background server, including:

receiving a data request sent by an intermediate server;

responding to the data request, and determining first response data;

sending the first response data to the intermediate server through a data interface corresponding to a background server, so that the intermediate server performs data processing on the first response data based on the current client type corresponding to the current client, obtains second response data matched with the current client type, and sends the second response data to the current client;

the background servers correspond to the data interfaces one by one.

In a third aspect, an embodiment of the present invention further provides a data request response device, integrated in an intermediate server, including:

the data request receiving module is used for receiving a data request sent by the current client;

the data request sending module is used for sending the data request to a background server so as to enable the background server to return first response data corresponding to the data request through a corresponding data interface, wherein the background server corresponds to the data interface one by one;

and the first response data processing module is used for carrying out data processing on the first response data based on the current client type corresponding to the current client, obtaining second response data matched with the current client type, and sending the second response data to the current client.

In a fourth aspect, an embodiment of the present invention further provides a data request response apparatus, integrated in a background server, including:

the data request receiving module is used for receiving a data request sent by the intermediate server;

the data request response module is used for responding to the data request and determining first response data;

the first response data sending module is used for sending the first response data to the intermediate server through a data interface corresponding to a background server, so that the intermediate server performs data processing on the first response data based on the current client type corresponding to the current client, obtains second response data matched with the current client type, and sends the second response data to the current client;

the background servers correspond to the data interfaces one by one.

In a fifth aspect, an embodiment of the present invention further provides a data request response system, where the system includes: different types of clients, intermediate servers and background servers;

each client is connected with the intermediate server, and the intermediate server is connected with the background server;

the intermediate server is used for implementing the data request response method provided by the first aspect of the invention;

the background server is used for implementing the data request response method provided by the second aspect of the invention.

In a sixth aspect, an embodiment of the present invention further provides a server, where the server includes:

one or more processors;

a memory for storing one or more programs;

when executed by the one or more processors, cause the one or more processors to implement a data request response method as provided by any of the embodiments of the invention.

In a seventh aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the data request response method provided in any embodiment of the present invention.

The embodiment of the invention has the following advantages or beneficial effects:

the method comprises the steps that an intermediate server is arranged between a current client and a background server, a received data request sent by the current client is sent to the background server through the intermediate server, and the background server returns general first response data corresponding to the data request based on a corresponding data interface. The intermediate server processes the received first response data based on the current client type to obtain second response data matched with the current client type and sends the second response data to the current client, thereby meeting the data requirements of different types of clients, and by arranging the intermediate servers, each background server only needs to develop a universal data interface without developing different data interfaces, when a new type of client is added, only the existing data interface is used for returning general first response data, the intermediate server processes the first response data based on the newly added client type to obtain the second response data matched with the newly added client type, and a new data interface does not need to be developed for the background server, so that the development workload is reduced, and the development efficiency is improved.

Drawings

Fig. 1 is a flowchart of a data request response method according to an embodiment of the present invention;

fig. 2 is a flowchart of a data request response method according to a second embodiment of the present invention;

fig. 3 is a flowchart of a data request response method according to a third embodiment of the present invention;

fig. 4 is a schematic structural diagram of a data request response apparatus according to a fourth embodiment of the present invention;

fig. 5 is a schematic structural diagram of a data request response apparatus according to a fifth embodiment of the present invention;

fig. 6 is a schematic structural diagram of a data request response system according to a sixth embodiment of the present invention;

fig. 7 is a schematic structural diagram of a server according to a seventh embodiment of the present invention.

Detailed Description

The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.

Example one

Fig. 1 is a flowchart of a data request response method according to an embodiment of the present invention, which is applicable to a case of responding to data requests sent by different types of clients. The method may be performed by a data request responding device, which may be implemented by means of software and/or hardware, integrated in an intermediate server. As shown in fig. 1, the method specifically includes the following steps:

and S110, receiving a data request sent by the current client.

The intermediate server can be in communication connection with various clients of different types in advance to process data requests sent by each client so as to provide data services. A client may refer to a program that provides local services to a client. Different types of clients may be clients that implement the same software function in different forms of programs. For example, shopping functions may be implemented with an application APP, applet, web page web, etc. type client. Different types of clients can be installed on different devices, such as a desktop computer, a mobile phone, a tablet computer, a notebook computer, and the like. The current client in this embodiment may refer to any client that sends a data request at the current time.

The intermediate server can be arranged between each client and the background server, so that the data requests sent by the clients and the response data returned by the background server are processed through the intermediate server. The number of the intermediate servers can be one or more. For example, the intermediate server may exist in the form of a server cluster in order to increase the computing speed and perform data backup, etc. The intermediate server in this embodiment may be a data service provided based on NodeJs. NodeJs is a JavaScript runtime environment based on the Chrome V8 engine.

Specifically, when the client needs to acquire background data, a data request may be sent to the intermediate server, so that the intermediate server may receive the data request sent by the current client.

And S120, sending the data request to a background server so that the background server returns first response data corresponding to the data request through a corresponding data interface, wherein the background server corresponds to the data interface one by one.

The background server may refer to a server storing response data so as to provide data services to the client. The number of the background servers in this embodiment may be one or more. For example, the background server may also exist in the form of a server cluster. The background server cluster corresponding to the client can comprise a plurality of independent background servers for providing different data services, so as to facilitate background development. For example, the background server cluster may include a background server for providing user data, a background server for providing order data, a background server for providing item preference data, and the like. Each background server corresponds to a general data interface so as to send general response data in the background servers to the intermediate server through the data interface. The same background server can obtain the same first response data when processing the same data request sent by different types of clients. That is, for the same data request, the first response data returned by the same backend server through the corresponding data interface is the same.

Specifically, the intermediate server may determine the background server to be invoked based on the received data request. When only one background server to be called exists, the data request is shown to be related to only one background server, and at this time, the intermediate server can send the data request to the background server through a unique data interface between the intermediate server and the background server based on an inter-server calling protocol, so that the background server receives the data request through the data interface, responds to the data request based on data processing logic corresponding to the data interface, obtains general first response data, and returns the first response data to the intermediate server. For example, when there are multiple data requests, the data requests sent by the intermediate server may be queued based on the actual performance of the data interface, so as to avoid exceeding the load of the background server and improve the processing performance.

Exemplarily, before S120, the method may further include: and determining the background server to be called from the plurality of candidate background servers based on the data request and the preset background calling configuration information.

The candidate background servers may refer to each background server in the background server cluster. The background server to be invoked may refer to a background server for responding to the data request. The number of background servers to be called can be one or more. Because the data required by the client is usually fragmented, there may be a plurality of background servers to be invoked, that is, a plurality of background servers need to be invoked to obtain the complete first response data corresponding to the data request. The preset background calling configuration information can be pre-configured, and each data request needs to call background server information. For example, the preset background calling configuration information may include a correspondence between the data request identifier and the background server identifier to be called.

Specifically, the intermediate server may match a target data request identifier corresponding to the received data request in preset background calling configuration information, and determine a candidate background server successfully matched with the target data request identifier as a background server to be called. By setting the preset background calling configuration information, one or more background servers to be called can be configured, so that the applicability and diversity of application scenes are improved.

S130, based on the current client type corresponding to the current client, data processing is carried out on the first response data, second response data matched with the current client type are obtained, and the second response data are sent to the current client.

Client types may include, but are not limited to, application software APP, applets, and web pages web, among others. The second response data may be response data required by the current client, which is obtained by performing data processing on the first response data. For example, the second response data may refer to response data to be presented by the current client, for example, when the data request is a request for presenting user information, the corresponding second response data is the user information that the current client needs to present.

Specifically, the intermediate server may perform UA (user agent) user agent judgment on the data request sent by the current client, that is, identify client information such as an operating system version, a CPU type, a browser version, a browser rendering engine, a browser language, and a browser plug-in used by the client according to a UA string header in the data request, so that the current client type corresponding to the current client may be obtained based on the client information. After receiving the general first response data returned by the background server, the intermediate server can obtain a corresponding data processing mode based on the current client type, perform data processing on the first response data based on the data processing mode, obtain second response data matched with the current client type, and send the second response data to the current client, so that the matched second response data can be obtained for different client types, and the data service across the clients is realized. By arranging the intermediate server, when the data requirements of different types of clients are met, each background server only needs to develop one universal data interface without developing different data interfaces, and when new types of clients are added, new data interfaces do not need to be developed for the background servers, so that the development workload is greatly reduced, and the development efficiency is improved.

According to the technical scheme of the embodiment, the intermediate server is arranged between the current client and the background server, the received data request sent by the current client is sent to the background server by using the intermediate server, and the background server returns the general first response data corresponding to the data request based on the corresponding data interface. The intermediate server processes the received first response data based on the current client type to obtain second response data matched with the current client type and sends the second response data to the current client, thereby meeting the data requirements of different types of clients, and by arranging the intermediate servers, each background server only needs to develop a universal data interface without developing different data interfaces, when a new type of client is added, only the existing data interface is used for returning general first response data, the intermediate server processes the first response data based on the newly added client type to obtain the second response data matched with the newly added client type, and a new data interface does not need to be developed for the background server, so that the development workload is reduced, and the development efficiency is improved.

On the basis of the above technical solution, S130 may include: determining a field cutting function and a field conversion function corresponding to the first response data based on the current client type corresponding to the current client; performing data clipping on useless fields in the first response data by calling a field clipping function; data conversion is carried out on the field to be converted in the first response data by calling a field conversion function; and determining the first response data after data cutting and data conversion as second response data.

Wherein the field clipping function may be a predefined function for deleting useless data in the first response data. The field conversion function may be a predefined function for field-converting the field to be converted in the first response data. For example, a field conversion function may be used to, but is not limited to, convert the format of a field. Illustratively, the time field in the first response data returned by the background server is usually in the format of a timestamp (e.g., 1594619048937), but various character effects of "time" are shown on the client, such as 7/10/2020/20200710, so that the time field in the first response data can be format-converted by a field conversion function to obtain a time field in a format that can be shown by the client. The field clipping function and the field conversion function in the embodiment can be stored on line for resource sharing, so that an intermediate server does not need to be redeployed when the functions are modified subsequently, and the development efficiency is improved.

Specifically, a field clipping function and a field conversion function corresponding to each client type may be configured for each data request in advance based on data required by each client type, so as to obtain data processing function configuration information corresponding to each data request. When receiving first response data returned by a data request sent by a current client, the intermediate server can match the current client type in data processing function configuration information corresponding to the data request, determine whether a field clipping function and/or a field conversion function corresponding to the current client type exists, if the field clipping function exists, indicate that useless data exists in the first response data, and at the moment, perform data clipping on the useless fields in the first response data by calling the field clipping function, so as to delete the useless fields in the first response data, further avoid the redundant situation of the response data returned to the client, and reduce network consumption. If the field conversion function exists, it indicates that the data to be converted exists in the first response data, and at this time, the field conversion function may be called to perform data conversion on the field to be converted in the first response data. By carrying out field cutting and field conversion on the first response data, the second response data matched with the current client type can be obtained, so that the data requirements of different types of clients can be met, the condition of redundancy of response data returned to the clients is avoided, and the network consumption is reduced.

It should be noted that, when the data interface of the background server is modified or a new type of client is added, a developer only needs to configure and modify the layer of the intermediate server, and does not need to modify all the clients, thereby greatly reducing the development workload and improving the development efficiency.

On the basis of the above technical solution, the method may further include: caching first response data returned by the background server; and/or caching the second response data sent to the current client.

Specifically, the first response data returned by the background server is cached, so that the load of the background server can be reduced, and the performance of the background server can be improved. By caching the second response data sent to the current client, the client request waiting time can be reduced, and the user experience is improved. In this embodiment, the first response data and the second response data may be cached by using a Redis cache cluster, so that all data are cached in the Redis cache cluster by using unique key information, so as to stretch data of the background server, and global sharing is cached on the background server, thereby improving the overall performance of the application.

Illustratively, caching the first response data returned by the background server may include: and determining the effective time corresponding to the first response data based on the data updating frequency of the first response data, and deleting the first response data when the effective time is reached. For example, caching the second response data sent to the current client may include: and determining the effective time corresponding to the second response data based on the data updating frequency of the second response data, and deleting the second response data when the effective time is reached.

Specifically, since the data has timeliness, the validity time can be set based on the data update frequency of the response data, i.e., a higher data update frequency indicates a higher real-time requirement, and thus a shorter validity time is set. By setting the effective time of the first response data and the second response data, the accuracy of the cached response data can be ensured, and the accuracy of the response data returned to the client side is further ensured.

On the basis of the above technical solution, before S120, the method may further include: if the target first cache data corresponding to the current client type exists based on the corresponding relation between the first cache data sent to the client and the client type which are cached in advance, the target first cache data are sent to the current client; or if the target second cache data returned by the background server is determined to exist based on the corresponding relation between the pre-cached second cache data returned by the background server and the background server, performing data processing on the target second cache data based on the current client type corresponding to the current client, obtaining second response data matched with the current client type, and sending the second response data to the current client.

Specifically, when a data request sent by each client is addressed, second response data returned to each client is cached, that is, a corresponding relationship between first cache data and a client type is established, so that when the intermediate server receives the data request subsequently, whether target first cache data corresponding to the current client type exists in the first cache data or not can be detected based on the corresponding relationship between the first cache data and the client type, and if the target first cache data exists, the target first cache data can be directly sent to the current client as response data, so that the client waiting time can be greatly shortened, the response speed is increased, and the user experience is improved. When a data request sent by each client is aimed at, caching first response data returned by the background server, namely establishing a corresponding relation between second cache data and the background server, so that when the intermediate server receives the data request subsequently, whether target second cache data corresponding to the background server to be called exists in the second cache data can be detected firstly based on the corresponding relation, if the target second cache data exists, the target second cache data can be subjected to data processing, second response data matched with the type of the current client is obtained, the background server does not need to be called to obtain the response data, the calling times of the background server are reduced, the performance of the background server is improved, the waiting time of the client can be shortened, and the user experience is improved.

It should be noted that, if the first response data returned by the background server and the second response data sent to the client are both cached, when a data request is subsequently processed, detection may be performed in the cached first cache data first, and if there is no target first cache data corresponding to the current client type, then detection is performed in the cached second cache data whether there is target second cache data corresponding to the background server to be called, so as to return the response data to the client as soon as possible, thereby improving response efficiency and improving user experience.

Example two

Fig. 2 is a flowchart of a data request response method according to a second embodiment of the present invention, where on the basis of the foregoing embodiments, when there are at least two background servers to be called, the second embodiment further optimizes the step "performing data processing on first response data based on a current client type corresponding to a current client, and obtaining second response data matched with the current client type". Wherein explanations of the same or corresponding terms as those of the above embodiments are omitted.

Referring to fig. 2, the data request response method provided in this embodiment specifically includes the following steps:

s210, receiving a data request sent by the current client.

S220, determining the background server to be called from the candidate background servers based on the data request and the preset background calling configuration information.

The number of the background servers to be called is at least two.

And S230, sending the data request to the background server so that the background server returns first response data corresponding to the data request through a corresponding data interface.

Specifically, when there are at least two background servers to be called, the data request may be asynchronously or synchronously sent to each background server based on the service requirement and the actual scene, so that each background server responds to the received data request, and returns the obtained first response data to the intermediate server, so that the intermediate server may receive the first response data returned by each background server.

And S240, processing the data of the first response data returned by each background server based on the current client type corresponding to the current client.

Specifically, based on the data processing method provided in the above embodiment, the first response data returned by each background server may be processed according to the current client type.

And S250, carrying out data combination on each first response data after data processing to obtain second response data matched with the current client type.

Specifically, the first response data obtained after each data processing may be merged by calling a data merging function, and the merged first response data may be used as the second response data, so that the response data may be returned uniformly. Compared with the prior art that the client needs to be in network connection with each background server, so that at least two network requests can be initiated to obtain the response data from the at least two background servers, the embodiment combines the response data of each background server by using the intermediate server, so that the response data can be uniformly returned to the current client, the request quantity of the client is reduced, the network overhead is more reasonable, and the overall performance of the application is further improved.

It should be noted that, in this embodiment, data processing may be performed on each first response data, and then data merging is performed on the first response data after data processing, so as to obtain second response data matched with the current client type; or performing data merging on each first response data, and then performing data processing on the first response data after data merging based on each client type to obtain second response data matched with the current client type. The present embodiment does not limit the execution order of steps S240 and S250.

And S260, sending the second response data to the current client.

According to the technical scheme of the embodiment, the first response data returned by each background server is subjected to data processing and data merging by using the intermediate server, so that the obtained second response data can be uniformly returned to the current client, the request quantity of the client is reduced, the network overhead is more reasonable, and the overall application performance is further improved.

On the basis of the above technical solution, before S230, the method may further include: detecting whether to limit the current of the data request or not based on a preset current limiting mode; if the data request does not need to be subjected to current limiting, carrying out request verification on the data request; and if the data request is successfully verified, performing route matching on the data request.

The preset current limiting method may refer to, but is not limited to, an IP address current limiting method and a peak current limiting method. Routing may refer to the network-wide process of determining an end-to-end path as a packet travels from a source to a destination.

Specifically, since the data service provided by the intermediate server is directly exposed on the public network, when the intermediate server receives a data request sent by the current client, the intermediate server needs to perform a filtering operation on the data request to ensure data security. The intermediate server may detect whether to limit the data request based on a preset current limiting manner, such as whether an IP address of the data request is a current limiting address or whether the number of current data requests exceeds a threshold. If the IP address of the data request is detected to be a current-limiting address, or the number of the current data requests exceeds a threshold value, it is indicated that the data request needs to be limited, at this time, the data request can be ignored, so as to avoid malicious requests such as traffic attack and crawler, and meanwhile, the number of the client requests is limited, so that the condition that the intermediate server is fully occupied by a large number of data requests, which causes the server to hang up, is prevented. If the IP address of the data request is detected not to be the current limiting address, or the number of the current data requests does not exceed the threshold value, it indicates that the data request does not need to be limited, at this time, request verification can be performed on the data request, such as verifying a Refer message header, a cookie value, a User-Agent User Agent, a URL (uniform resource locator) website and the like in the request, so as to prevent malicious requests, XSS attacks and the like. After the data request is successfully verified, the path of the data request can be matched, so that the data request is processed by using the successfully matched code, the filtering operation on the data request is realized, and the data security is ensured.

It should be noted that, after receiving the filtered data request sent by the intermediate server, the background server may not need to perform operations such as checking on the data request, so that the resource utilization rate may be further improved and the data security is ensured.

EXAMPLE III

Fig. 3 is a flowchart of a data request response method according to a third embodiment of the present invention, which is applicable to a case of responding to data requests sent by different types of clients. The method can be executed by a data request response device, which can be implemented by software and/or hardware, and is integrated in a background server. As shown in fig. 3, the method specifically includes the following steps:

and S310, receiving a data request sent by the intermediate server.

The background server may refer to a server storing response data so as to provide data services to the client. The number of the background servers in this embodiment may be one or more. For example, the background server may also exist in the form of a server cluster. The background server cluster corresponding to the client can comprise a plurality of independent background servers for providing different data services, so as to facilitate background development. For example, the background server cluster may include a background server for providing user data, a background server for providing order data, a background server for providing item preference data, and the like.

It should be noted that the intermediate server is in communication connection with each backend server, and each backend server can return response data by executing steps S110 to S130.

Specifically, each background server and the intermediate server are in data communication through different data interfaces. The intermediate server may send the data request to the background server through a unique data interface with the background server based on an inter-server call protocol, so that the background server may receive the data request through the data interface.

S320, responding to the data request and determining first response data.

Specifically, after receiving a data request sent by the intermediate server, the background server may respond to the data request based on the data processing logic corresponding to the data interface, so as to obtain first response data corresponding to the data request.

It should be noted that each backend server corresponds to a general data interface, so that the general first response data can be obtained through the data interface. That is, the same background server obtains the same first response data when processing the same data request sent by different types of clients.

S330, sending the first response data to an intermediate server through a data interface corresponding to the background server, so that the intermediate server performs data processing on the first response data based on the current client type corresponding to the current client, obtains second response data matched with the current client type, and sends the second response data to the current client; the background servers correspond to the data interfaces one by one.

Specifically, each background server corresponds to a general data interface, so that general response data in the background server is sent to the intermediate server through the data interface, the intermediate server performs data processing on the general first response data, and second response data matched with the current client type are obtained, thereby realizing data service across clients. By arranging the intermediate server between the client and the background servers, when the data requirements of different types of clients are met, each background server only needs to develop one universal data interface without developing different data interfaces, and when new types of clients are added, new data interfaces do not need to be developed for the background servers, so that the development workload is greatly reduced, and the development efficiency is improved.

The following is an embodiment of a data request responding apparatus provided in the embodiments of the present invention, and the apparatus and the data request responding method in the first embodiment or the second embodiment belong to the same inventive concept, and details that are not described in detail in the embodiments of the data request responding apparatus may refer to the embodiments of the first embodiment or the second embodiment of the data request responding method.

Example four

Fig. 4 is a schematic structural diagram of a data request responding apparatus according to a fourth embodiment of the present invention, where this embodiment is applicable to a case of responding to data requests sent by different types of clients, and the apparatus may specifically include: a data request receiving module 410, a data request transmitting module 420 and a first response data processing module 430.

The data request receiving module 410 is configured to receive a data request sent by a current client; the data request sending module 420 is configured to send a data request to a background server, so that the background server returns first response data corresponding to the data request through a corresponding data interface, where the background server corresponds to the data interfaces one to one; the first response data processing module 430 is configured to perform data processing on the first response data based on a current client type corresponding to the current client, obtain second response data matched with the current client type, and send the second response data to the current client.

Optionally, the first response data processing module 430 is specifically configured to: determining a field cutting function and a field conversion function corresponding to the first response data based on the current client type corresponding to the current client; performing data clipping on useless fields in the first response data by calling a field clipping function; data conversion is carried out on the field to be converted in the first response data by calling a field conversion function; and determining the first response data after data cutting and data conversion as second response data.

Optionally, the apparatus further comprises:

and the background server determining module is used for determining the background server to be called from the candidate background servers based on the data request and the preset background calling configuration information before the data request is sent to the background server.

Optionally, the number of the background servers to be called is at least two; the first response data processing module 430 is further specifically configured to:

based on the current client type corresponding to the current client, performing data processing on first response data returned by each background server; and carrying out data combination on each first response data after data processing to obtain second response data matched with the current client type.

Optionally, the apparatus further comprises:

the data caching module is used for caching first response data returned by the background server; and/or caching the second response data sent to the current client.

Optionally, the apparatus further comprises:

the cache data detection module is used for sending a data request to a background server, and if the first cache data corresponding to the current client type is determined to exist based on the corresponding relation between the first cache data sent to the client and the client type, which are cached in advance, the first cache data is sent to the current client; alternatively, the first and second electrodes may be,

and if the target second cache data returned by the background server is determined to exist based on the corresponding relation between the pre-cached second cache data returned by the background server and the background server, performing data processing on the target second cache data based on the current client type corresponding to the current client, obtaining second response data matched with the current client type, and sending the second response data to the current client.

Optionally, the data caching module is specifically configured to: and determining the effective time corresponding to the first response data based on the data updating frequency of the first response data, and deleting the first response data when the effective time is reached.

Optionally, the apparatus further comprises:

the data request filtering module is used for detecting whether to limit the current of the data request based on a preset current limiting mode before sending the data request to the background server; if the data request does not need to be subjected to current limiting, carrying out request verification on the data request; and if the data request is successfully verified, performing route matching on the data request.

The data request response device provided by the embodiment of the invention can execute the data request response method provided by the first embodiment or the second embodiment of the invention, and has the corresponding functional modules and the beneficial effects of executing the data request response method.

The following is an embodiment of a data request responding apparatus provided in an embodiment of the present invention, and the apparatus and the data request responding method of the third embodiment belong to the same inventive concept, and details that are not described in detail in the embodiment of the data request responding apparatus may refer to the third embodiment of the data request responding method.

EXAMPLE five

Fig. 5 is a schematic structural diagram of a data request responding apparatus according to a fifth embodiment of the present invention, where this embodiment is applicable to a case of responding to data requests sent by different types of clients, and the apparatus may specifically include: a data request receiving module 510, a data request responding module 520, and a first response data transmitting module 530.

The data request receiving module 510 is configured to receive a data request sent by an intermediate server; a data request response module 520, configured to respond to the data request and determine first response data; a first response data sending module 530, configured to send the first response data to the intermediate server through a data interface corresponding to the background server, so that the intermediate server performs data processing on the first response data based on a current client type corresponding to the current client, obtains second response data matched with the current client type, and sends the second response data to the current client; the background servers correspond to the data interfaces one by one.

The data request response device provided by the embodiment of the invention can execute the data request response method provided by the third embodiment of the invention, and has the corresponding functional modules and beneficial effects of the data request response method.

EXAMPLE six

Fig. 6 is a schematic structural diagram of a data request response system according to a sixth embodiment of the present invention, which is applicable to a case of responding to data requests sent by different types of clients. As shown in fig. 6, the system includes: different types of clients 610, intermediate servers 620, and backend servers 630.

Each client 610 is connected with an intermediate server 620, and the intermediate server 620 is connected with a background server 630. In this embodiment, each client 610 and the intermediate server 620 may be communicatively connected through a network service, and the intermediate server 620 and the background server 630 may also be communicatively connected through a network service, so as to perform data transmission.

The intermediate server 620 is configured to implement the data request response method provided in the first embodiment or the second embodiment of the present invention; the background server 630 is used to implement the data request response method provided by the third embodiment of the present invention.

The working process of the data request response system provided by the embodiment is as follows:

the current client 610, which needs to request data at the current time, sends a data request to the intermediate server 620. Each backend server 630 may be in data communication with the intermediate server 620 via a different one of the data interfaces. The intermediate server 620 may send the data request to the backend server 630 through a unique data interface with the backend server 630 based on an inter-server call protocol, so that the backend server 630 may receive the data request through the data interface. The background server 630 responds to the data request based on the data processing logic corresponding to the data interface, so as to obtain the general first response data corresponding to the data request, and sends the first response data to the intermediate server 620 through the data interface. The inter-server 620 performs data processing on the first response data based on the current client type corresponding to the current client 610, obtains second response data matched with the current client type, and sends the second response data to the current client 610, thereby implementing a cross-client data service. By arranging the intermediate server 620 between the client 610 and the background server 630, when the data requirements of different types of clients are met, each background server only needs to develop a general data interface without developing different data interfaces, and when a new type of client is added, a new data interface does not need to be developed for the background server, so that the development workload is greatly reduced, and the development efficiency is improved.

In the data request response system in this embodiment, an intermediate server is arranged between the current client and the background server, the intermediate server is used to send the received data request sent by the current client to the background server, and the background server returns general first response data corresponding to the data request based on a corresponding data interface. The intermediate server processes the received first response data based on the current client type to obtain second response data matched with the current client type and sends the second response data to the current client, thereby meeting the data requirements of different types of clients, and by arranging the intermediate servers, each background server only needs to develop a universal data interface without developing different data interfaces, when a new type of client is added, only the existing data interface is used for returning general first response data, the intermediate server processes the first response data based on the newly added client type to obtain the second response data matched with the newly added client type, and a new data interface does not need to be developed for the background server, so that the development workload is reduced, and the development efficiency is improved.

EXAMPLE seven

Fig. 7 is a schematic structural diagram of a server according to a seventh embodiment of the present invention. FIG. 7 illustrates a block diagram of an exemplary server 12 suitable for use in implementing embodiments of the present invention. The server 12 shown in fig. 7 is only an example, and should not bring any limitation to the function and the scope of use of the embodiment of the present invention.

As shown in fig. 7, the server 12 is in the form of a general purpose computing server. The components of the server 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 that couples various system components including the system memory 28 and the processing unit 16.

Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, micro-channel architecture (MAC) bus, enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

The server 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by server 12 and includes both volatile and nonvolatile media, removable and non-removable media.

The system memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM)30 and/or cache memory 32. The server 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 7, and commonly referred to as a "hard drive"). Although not shown in FIG. 7, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 18 by one or more data media interfaces. System memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

A program/utility 40 having a set (at least one) of program modules 42 may be stored, for example, in system memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. Program modules 42 generally carry out the functions and/or methodologies of the described embodiments of the invention.

The server 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), with one or more devices that enable a user to interact with the server 12, and/or with any devices (e.g., network card, modem, etc.) that enable the server 12 to communicate with one or more other computing devices. Such communication may be through an input/output (I/O) interface 22. Also, the server 12 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet) via the network adapter 20. As shown, the network adapter 20 communicates with the other modules of the server 12 via the bus 18. It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the server 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

The processing unit 16 executes various functional applications and data processing by executing programs stored in the system memory 28, for example, to implement a data request response method provided by the embodiment, the method includes:

receiving a data request sent by a current client;

and processing the first response data based on the current client type corresponding to the current client to obtain second response data matched with the current client type, and sending the second response data to the current client.

Alternatively, the first and second electrodes may be,

receiving a data request sent by an intermediate server;

responding to the data request, and determining first response data;

sending the first response data to an intermediate server through a data interface corresponding to the background server, so that the intermediate server performs data processing on the first response data based on the current client type corresponding to the current client, obtains second response data matched with the current client type, and sends the second response data to the current client;

the background servers correspond to the data interfaces one by one.

Of course, those skilled in the art can understand that the processor can also implement the technical solution of the data request response method provided by any embodiment of the present invention.

Example eight

The present embodiment provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the data request response method as provided by any of the embodiments of the present invention.

Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer-readable storage medium may be, for example but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

It will be understood by those skilled in the art that the modules or steps of the invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of computing devices, and optionally they may be implemented by program code executable by a computing device, such that it may be stored in a memory device and executed by a computing device, or it may be separately fabricated into various integrated circuit modules, or it may be fabricated by fabricating a plurality of modules or steps thereof into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.

It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A data request response method is applied to an intermediate server and comprises the following steps:

receiving a data request sent by a current client;

2. The method of claim 1, wherein performing data processing on the first response data based on a current client type corresponding to the current client to obtain second response data matching the current client type comprises:

determining a field clipping function and a field conversion function corresponding to the first response data based on the current client type corresponding to the current client;

performing data clipping on useless fields in the first response data by calling the field clipping function;

performing data conversion on the field to be converted in the first response data by calling the field conversion function;

and determining the first response data after data cutting and data conversion as second response data.

3. The method of claim 1, prior to sending the data request to a backend server, further comprising:

and determining the background server to be called from a plurality of candidate background servers based on the data request and preset background calling configuration information.

4. The method of claim 3, wherein the number of background servers to be invoked is at least two;

the data processing of the first response data based on the current client type corresponding to the current client to obtain second response data matched with the current client type includes:

based on the current client type corresponding to the current client, performing data processing on first response data returned by each background server;

and performing data combination on each first response data after data processing to obtain second response data matched with the current client type.

5. The method of claim 1, further comprising:

caching first response data returned by the background server; and/or the presence of a gas in the gas,

and caching the second response data sent to the current client.

6. The method of claim 5, prior to sending the data request to a backend server, further comprising:

if the target first cache data corresponding to the current client type exists based on the corresponding relation between the first cache data which are sent to the client and the client type which are cached in advance, the target first cache data are sent to the current client; alternatively, the first and second electrodes may be,

7. The method of claim 5, wherein caching the first response data returned by the backend server comprises:

and determining the valid time corresponding to the first response data based on the data updating frequency of the first response data, and deleting the first response data when the valid time is reached.

8. The method of any of claims 1-7, further comprising, prior to sending the data request to a backend server:

detecting whether the data request is subjected to current limiting or not based on a preset current limiting mode;

if the data request does not need to be subjected to current limiting, carrying out request verification on the data request;

and if the data request is successfully verified, performing route matching on the data request.

9. A data request response method is applied to a background server and comprises the following steps:

receiving a data request sent by an intermediate server;

responding to the data request, and determining first response data;

the background servers correspond to the data interfaces one by one.

10. A data request response device, integrated with an intermediary server, comprising:

11. A data request response device, integrated in a backend server, comprising:

the background servers correspond to the data interfaces one by one.

12. A data request response system, the system comprising: different types of clients, intermediate servers and background servers;

the intermediate server is used for realizing the data request response method of any one of claims 1 to 8;

the background server is used for implementing the data request response method of claim 9.

13. A server, characterized in that the server comprises:

one or more processors;

a memory for storing one or more programs;

when executed by the one or more processors, cause the one or more processors to implement a data request response method as recited in any of claims 1-9.

14. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out a data request response method according to any one of claims 1 to 9.