CN115002210A

CN115002210A - Data processing method, platform, electronic device and storage medium

Info

Publication number: CN115002210A
Application number: CN202210630154.3A
Authority: CN
Inventors: 郑晓玲; 杨宝頔; 李帅; 陈强强; 张晗; 云鹏; 王基欢
Original assignee: Beijing Ziroom Information Technology Co Ltd
Current assignee: Beijing Ziroom Information Technology Co Ltd
Priority date: 2022-06-06
Filing date: 2022-06-06
Publication date: 2022-09-02

Abstract

The application provides a data processing method, a platform, an electronic device and a storage medium, wherein the method comprises the following steps: acquiring first service data, wherein the first service data is request data sent by a client; determining target data processing operation to be executed on the first service data; processing operation according to the target data to obtain second service data; and sending the second service data to a response third party. By the method and the device, the problem that a large amount of redundant content is contained in the project code in the related technology is solved.

Description

Data processing method, platform, electronic device and storage medium

Technical Field

The present application relates to the internet field, and in particular, to a data processing method, a data processing platform, an electronic device, and a storage medium.

Background

At present, in an internet enterprise, a plurality of departments need to cooperate together to efficiently complete complex business of the company. With the continuous landing of micro-service architectures of departments of companies, the number of items is also greatly increased, which also causes problems: each service needs to manage the API (Application Programming Interface) of many other department systems (hereinafter referred to as three-party systems), and when the address or Interface of some API changes, the worker needs to check all microservice items. The same API may be used by different items simultaneously, as in fig. 1, so that a large amount of redundant code is present in the code.

Therefore, the related art has a problem that a large amount of redundant contents are contained in the project code.

Disclosure of Invention

The application provides a data processing method, a data processing platform, an electronic device and a storage medium, which are used for solving at least the problem that a large amount of redundant content is contained in project codes in the related art.

According to an aspect of an embodiment of the present application, there is provided a method of data processing, the method including:

acquiring first service data, wherein the first service data is request data sent by a client;

determining target data processing operation to be executed on the first service data;

processing operation according to the target data to obtain second service data;

and sending the second service data to a response third party.

According to another aspect of the embodiments of the present application, there is also provided a data processing platform, including:

the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring first service data, and the first service data is request data sent by a client;

the first determining module is used for determining target data processing operation to be executed on the first service data;

the obtaining module is used for processing operation according to the target data to obtain second service data;

and the first sending module is used for sending the second service data to a third party responding to the second service data.

According to another aspect of the embodiments of the present application, there is also provided an electronic device, including a processor, a communication interface, a memory, and a communication bus, where the processor, the communication interface, and the memory communicate with each other through the communication bus; wherein the memory is used for storing the computer program; a processor for performing the method steps in any of the above embodiments by running the computer program stored on the memory.

According to a further aspect of the embodiments of the present application, there is also provided a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to perform the method steps of any of the above embodiments when the computer program is executed.

In the embodiment of the application, first service data is obtained, wherein the first service data is request data sent by a client; determining target data processing operation to be executed on the first service data; processing operation according to the target data to obtain second service data; and sending the second service data to the responding third party. The third-party system interface management platform is arranged in the embodiment of the application, and is used for managing all the APIs (application programming interfaces) of the third-party system in a centralized manner, so that the configuration and maintenance of various interfaces responding to the third-party system of the client service system are reduced, and meanwhile, the third-party system interface management platform is used for uniformly processing the request service data, so that redundant codes and code complexity can be effectively reduced, and the problem that a large amount of redundant contents are contained in project codes in the related technology is solved.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.

In order to more clearly illustrate the embodiments of the present invention 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, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.

FIG. 1 is a diagram illustrating a business system and API calls responding to a third party system according to the related art;

fig. 2 is a schematic diagram of an optional API call situation after introducing a third-party system interface management platform according to an embodiment of the present application;

FIG. 3 is a schematic diagram illustrating an overall design of an alternative data processing method according to an embodiment of the present application;

fig. 4 is a schematic diagram of an alternative route forwarding processing scheme according to an embodiment of the present application;

FIG. 5 is a schematic diagram of an alternative interface exception retry scheme according to an embodiment of the present application;

FIG. 6 is a schematic diagram of an alternative data simulation scheme according to an embodiment of the present application;

FIG. 7 is a schematic diagram of an alternative implementation of a fusing mechanism for responding to a third party interface according to an embodiment of the present application;

FIG. 8 is a schematic diagram of an alternative abnormal alert scheme according to an embodiment of the present application;

FIG. 9 is a schematic diagram of an alternative anomaly alert interface according to an embodiment of the present application;

FIG. 10 is a schematic diagram of an alternative statistical analysis of requested data according to an embodiment of the present application;

FIG. 11 is a schematic diagram of an alternative interface data statistics page according to an embodiment of the present application;

FIG. 12 is an alternative interface diagram for entering page information according to an embodiment of the present application;

FIG. 13 is an alternative interface basic configuration interface diagram according to an embodiment of the present application;

FIG. 14 is an alternative interface response correlation information interface diagram according to an embodiment of the present application;

FIG. 15 is a schematic flow chart diagram illustrating an alternative method of data processing according to an embodiment of the present application;

FIG. 16 is a block diagram of an alternative platform architecture for data processing according to an embodiment of the present application;

fig. 17 is a block diagram of an alternative electronic device according to an embodiment of the present application.

Detailed Description

In order to make the technical solutions of the present application better understood by those skilled in the art, 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 some embodiments of the present application, and not all 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.

It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the accompanying drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

In this embodiment and subsequent embodiments, the third-party system interface management platform is used as an execution subject side, and specifically, the process of the method may include the following steps:

step 1, acquiring first service data, wherein the first service data is request data sent by a client;

step 2, determining target data processing operation to be executed on the first service data;

step 3, processing operation is carried out according to the target data to obtain second service data;

and 4, sending the second service data to a response third party.

Optionally, as shown in fig. 3, in the embodiment of the present application, a third-party system interface management platform (i.e., the three-party interface access system in fig. 3) is configured as an intermediate medium between the service system and the third-party system (i.e., responding to a third party), so that the third-party system interface management platform acquires first service data sent by the service system (i.e., a client), and processes (e.g., performs a target data processing operation) the first service data by using the first service data as request data, so as to obtain second service data, and then sends the processed service data to the third-party system.

As an optional embodiment, determining that the target data processing operation to be performed on the first service data includes:

acquiring a plurality of data sub-processing schemes contained in a target integrated scheme, wherein each data sub-processing scheme corresponds to a data processing operation;

performing data self-adaptation on the first service data and the data sub-processing scheme to determine a target data sub-processing scheme;

determining the target data processing operation based on the target data sub-processing scheme.

Optionally, as shown in fig. 2 and fig. 3, the third-party system interface management platform includes functions of routing forwarding, current limiting, fusing, data simulation, unified authentication, data statistics, monitoring and warning, load balancing, and the like, the functions included in the third-party system interface management platform may be unified into one target integrated scheme, and then the corresponding forwarding, current limiting, fusing, data simulation, and the like are used as data sub-processing schemes in the target integrated scheme, and after the first service data is obtained, only the first service data needs to be subjected to data self-adaptation with each data sub-processing scheme, and then the target data processing operation for processing the first service data can be obtained.

In addition, as can be known from fig. 3, at the service system side, each service system accesses the third party system interface management platform through the SDK, and returns data to the service system after completing data flow through the third party system interface management platform.

As an optional embodiment, the data sub-processing scheme includes a route forwarding processing scheme, and the obtaining the second service data according to the target data processing operation includes:

acquiring an interface protocol for requesting the response third party from the first service data;

automatically adapting the interface protocol according to protocol adaptation in the route forwarding processing scheme to obtain a target interface, wherein the target interface is an interface capable of requesting the response third party;

and sending the second service data through the target interface, wherein the current second service data is the same as the first service data.

Optionally, as shown in fig. 4, protocols responding to the API of the third-party system may be various, some may be interfaces of Http, some may be Webservice protocols, or RPC protocols based on Dubbo, the third-party system interface management platform integrates the routing forwarding functions of these protocols, when the service system uses SDK to send the first service data and requests to access and respond to the third-party system, the third-party system interface management platform automatically adapts the protocol responding to the third-party interface, and then performs data automatic adaptation on the request response data to obtain a target interface sending the first service data to the responding third party. Here, since the third-party system interface management platform performs a routing forwarding function and does not process the first service data, the current second service data is the acquired first service data.

In the embodiment of the application, the third-party system interface management platform realizes the multi-protocol adaptive routing forwarding function, and all calls in the centralized management department respond to the third-party system API, so that the configuration and maintenance of various third-party system interfaces responding to the service system are reduced.

As an optional embodiment, the data sub-processing scheme includes an interface exception retry scheme, and the obtaining the second service data according to the target data processing operation includes:

acquiring request information of a first interface contained in the first service data, wherein the first interface is any interface which requests the response of the third party;

under the condition that the request times corresponding to the request information of the first interface are smaller than a time threshold value, starting a retry scheme of the first interface to obtain the second service data; or, under the condition that it is determined that the request duration corresponding to the request information of the first interface is smaller than a duration threshold, starting the retry scheme for the first interface to obtain the second service data.

Optionally, for some interfaces supporting idempotent, the retry number of each API interface may be configured through a page, and when the interface request is over time or abnormal, the third-party system interface management platform supports the interface retry function. The retry function is implemented as shown in fig. 5:

after the third-party system interface management platform acquires the request information to the first interface, the first interface can be loaded, and the cache (including the threshold value of the retry times) is configured.

After the number of times of requesting information for the first interface is determined to be larger than or equal to the number threshold, the first interface can be directly used for feeding back response data. And restarting the first interface retry scheme when the number of times of requesting the information for the first interface is determined to be less than the threshold number of times.

Meanwhile, in the embodiment of the application, a duration threshold is further set, and the retry scheme of the first interface is restarted under the condition that the request duration corresponding to the request information of the first interface is determined to be smaller than the duration threshold.

That is, in the embodiment of the present application, a retry scheme of an interface is set, a certain fault tolerance is given, and a dynamically configurable timeout retry mechanism is supported.

As an alternative embodiment, the data sub-processing scheme includes a data simulation scheme, and the obtaining the second service data according to the target data processing operation includes:

intercepting the first service data under the condition that the acquired first service data contains simulation configuration information;

and starting simulation operation, and simulating response data based on the first service data as the second service data.

Optionally, as shown in fig. 6, in the embodiment of the present application, during cross-department collaborative development, if some third party interfaces are not developed, a data simulation (Mock) mechanism may be disposed on the third party system interface management platform, and a data request (e.g., first service data) is intercepted to complete simulation of response information of the first service data, so as to obtain simulated second service data, and then the simulated second service data value client is sent, so that a project research and development process of the client is not affected.

At this time, the simulated switch and the simulated response data can be configured through the page configuration API interface.

As an optional embodiment, after the sending the second service data to the responding third party, the method further includes:

receiving response information of the response third party;

under the condition that the corresponding abnormal times in the response information are determined to be larger than or equal to a first abnormal threshold value, starting a data fusing mechanism;

and sending the fusing result to the client, or sending the data stored in the database at the previous moment of the current moment to the client.

Optionally, the third party system interface management platform is down in order to reduce the downstream system failure. When the same API is unavailable in a short time or the response time is too long, a fusing mechanism is started, fusing can be recovered after the fusing time limit is exceeded, and the fusing can be executed according to the operation configured in the background. The specific implementation mechanism is shown in fig. 7:

when the third-party interface is called and responded for multiple times, if the received response information is abnormal, the number of times of the abnormality is compared with a preset first abnormal threshold value, if the number of times of the abnormality is larger than or equal to the first abnormal threshold value, a fusing mechanism is started, whether the fusing mechanism exceeds a fusing time limit or not is judged, if the fusing time limit is exceeded, the fusing mechanism can be recovered, if the fusing time limit is not exceeded, a fusing result (namely fused data) is sent to a client, a friendly prompt is returned to the client, and data cached in redis at the last time can also be returned.

In addition, after the number of managed systems and APIs is gradually increased, the third-party system interface management platform is similar to a traffic gateway and needs to support high concurrency and high performance. The embodiment of the application introduces Spring Reactor response type programming, and improves the throughput and concurrency of the system through an asynchronous model.

The third-party system interface management platform can centrally process API (application program interface) flows responding to a third-party system, can make unified data processing and monitoring aiming at the flows, supports a load balancing mechanism, an asynchronous model mechanism and a fusing current limiting mechanism, and has the characteristics of high concurrency, high performance and high availability.

As an optional embodiment, the data sub-processing scheme includes an exception alarm scheme, and the obtaining the second service data according to the target data processing operation includes:

acquiring request information of a second interface contained in the first service data, wherein the second interface is any interface which requests the response of the third party;

under the condition that the abnormal data of the second interface is determined, setting a preset time length as the advancing step length of a sliding window, and storing the abnormal data occurring in the preset time length in a database, wherein each preset time length corresponds to one sliding window;

and under the condition that the abnormal data contained in the target sliding window is greater than or equal to a second abnormal threshold, triggering abnormal alarm according to the alarm level corresponding to the target sliding window, wherein the target sliding window is a subset of the sliding windows, and each sliding window corresponds to one alarm level.

Optionally, in the embodiment of the present application, a sliding window algorithm is used to reduce noise of the abnormal alarm of the API interface, which may specifically refer to fig. 8:

firstly, setting the advancing step length of window sliding: the preset time period may be set to 1 minute, 1 hour, 1 day, or the like. Each preset duration is set with an alarm level, for example, 10 times of abnormality (or 5 times, etc., without limitation) occurs in 1 minute, the corresponding alarm level is P0, 10 times of abnormality occurs in 1 hour, the corresponding alarm level is P1, 10 times of abnormality occurs in 1 day, and the corresponding alarm level is P2, etc.

When the request information of the first service data for the second interface is determined to be abnormal data, no alarm occurs for the first time, the data is added into a redis cache, when the abnormal data occurs subsequently, the abnormal data is stored into a database (such as mysql), corresponding alarm noise reduction is matched according to the number of the obtained abnormal data, for example, when the abnormal data occurs more than 10 times within 1 minute in a subsequent target sliding window, a P0 alarm level is selected for alarm, an alarm group and an alarm mode (DD, QYWX and other communication software) can be selected, and then the alarm is stored into the database (such as mysql).

And (4) each level of abnormal alarm can be prompted by the abnormal alarm in the communication software, and the abnormal alarm is transmitted to a responsible person of the interface.

Clicking ' no reminding any more on the day ' in the communication software, and removing the white list after 00 o ' clock the next day, such as an alarm interface shown in fig. 9.

The current abnormal alarm policy also includes a default policy: the default strategy is as follows: if the interface is abnormal, an abnormal alarm prompt can be given in the communication software, and @ the interface is sent to a responsible person.

In the embodiment of the application, any response third-party system API has a problem, the alarm notification can be timely given, and the repeated alarm is subjected to noise reduction treatment, so that the alarm omission and disturbance are avoided.

receiving response information fed back by the third party requested interface, wherein the response information comprises the requested number of the requested interface, the success number and the failure number of the requested interface in preset time;

determining a response time length according to the response information;

determining the number of overtime, the shortest response time and the longest response time in the preset time according to the response time;

and storing the response information, the number of overtime, the response shortest time and the response longest time in a database, and displaying the response information, the number of overtime, the response shortest time and the response longest time on the client through a display tool.

Optionally, as shown in fig. 10, a request response log (including the requested number of requested interfaces, the success number of requested interfaces within a preset time, the failure number, the response duration, and the like) is collected based on Filebeat, Kafka, and Flink, all the request response data is stored in a database (e.g., Clickhouse), and the statistical result is displayed on the front end of the client through the display software.

Referring to fig. 11, fig. 11 is an interface statistics page, which includes a search box for users to search,

and (3) retrieval conditions:

time range: default "24 hours elapsed";

ServiceKey: unique identification corresponding to the interface;

the display list is as follows:

ServiceKey: unique identification corresponding to the interface;

url: displaying the URL path of the interface, such as: the/api/stopReceive/group/indexValue;

the number of requests: the number of requests for the interface during this search time;

failure rate (%): counting the failure percentage in the interface request number in the time range;

the number of overtime: counting the overtime quantity in the quantity of the interface requests within the time range;

counting the time with the maximum interface response time in milliseconds in the interface requests within the time range, wherein the unit of the time is Max (ms);

min (ms): counting the minimum time of interface response time in the interface request within the time range, wherein the unit is millisecond;

avg (ms): and counting the average response time of the interface in the interface request in the time range, wherein the unit is millisecond.

In the embodiment of the application, a set of complete log collection scheme is provided for mass data statistics, so that the response conditions of the third-party system API, including the number of requests, failure rate, timeout, maximum response time, minimum response time, average response time and the like, can be seen very intuitively through a background.

As an optional embodiment, the embodiment of the present application describes page entry information of an interface management platform of a third-party system, and as shown in fig. 12, a page which can be entered and respond to the third-party system is provided in the interface management platform of the third-party system, and different environments can be distinguished, and a domain name of the third-party system can be dynamically updated and responded to.

In fig. 12, the entry information includes:

the system name is: responding to the name of the third party system, such as: building dictionary system.

And (3) daily environment: responding to the daily environment domain name of the third-party system;

the quasi-production environment is as follows: responding to the domain name of the quasi-production environment of the third-party system;

formal environment: responding to a formal environment domain name of a third party system;

remarking: and (4) remarking information.

In addition, the third-party system interface management platform provides API interface management responding to the third-party system, as shown in fig. 13, which is an interface basic configuration interface diagram.

ServiceKey: the service system can use the SDK to input the parameter according to the unique identifier of the corresponding interface, and the third-party system interface management platform can automatically identify the corresponding response third-party interface of the parameter.

The system comprises the following steps: a responding third party system may be selected.

Host: after selecting and responding to a third-party system, automatically displaying a corresponding domain name under the environment; such as: if the third-party system interface management platform of the quasi-production environment is logged in, then if the "inventory system" is selected in fig. 13, the domain name of the quasi-production environment of the "inventory system" is corresponded.

The method comprises the following steps: and the API interface corresponds to a request mode and a requested URL path.

The data source is as follows: "Mock (Mock) data" or "real data" may be selected, and when "Mock data" is selected, the response data is Mock data when the service system sends a request for this interface.

Interface document address: the url path of the interface document can be input, and the user can conveniently check the url path.

The interface request setting includes: and (4) timeout: and calling the timeout time responding to the third-party interface by the third-party system interface management platform, defaulting to 5000ms, dynamically modifying the timeout time, and handling the timeout setting of the unused interface.

And (4) retry: the third-party system interface management platform calls the overtime retry times after responding to the third-party interface failure, can retry aiming at the inquired or idempotent interface and supports the dynamic retry times.

Request data location:

body: corresponding to Content-Type in http request header information: application/json.

formData: corresponding to Content-Type in http request header information: application/x-www-form-url encoded.

Header parameters: and the format of the header information in the corresponding http request header information is in a key/vlue form.

The third party system interface management platform also sets a response related information page, as shown in fig. 14, including:

code field name: responding to the field corresponding to the third-party interface response code, such as: code.

Successful response code: the successful response codes returned by the response third-party interface are defined, so that the condition that the successful response codes returned by the response third-party interface are not uniform can be compatible.

data field name: fields responsive to third party interface return data

message field name: responding to the field of the message information returned by the third-party interface

Exception code white list: the third-party system interface management platform can respond to the abnormal interface return and can carry out communication software alarm on abnormal information, and if some abnormal codes exist, business personnel do not need to pay attention to the abnormal codes, a corresponding white list can be configured to carry out filtering, so that unnecessary abnormal alarm is avoided.

White list of abnormal keywords: the business personnel do not need to pay attention to the abnormity, except the configuration through the abnormal code white list, the keywords in the abnormal information can be returned for filtering, and the invalid alarm is further filtered.

Alarm strategy type:

the types of the alarm strategies are as follows: the default policy and the frequency policy refer to the above embodiments in the specific implementation, which are not described herein again.

Fusing type:

the fusing types are: no operation, returning default configuration data and returning the last request data of the cache.

No operation: and the processing after fusing is directly returned to the service system without special processing.

And returning default configuration data: and returning configured data to the processing after fusing, wherein the configuration content is configured in the field of fusing configuration.

Returning the last request data of the cache: and returning the data cached in the redis last time after the interface is fused, and aiming at the problem that some query interfaces are still available high after the interface is fused.

A fusing configuration:

when the fusing type is "return default configuration data", the interface after fusing returns JSON data configured for this.

Mock returns rowCode: when the interface data source is 'Mock data', the returned code can be customized, and the service system can perform scene coverage of multiple successes and failures according to the rock code of Mock.

And Mock returns data: when the interface data source is 'Mock data', JSON data configured in the field is returned.

Based on the content of the foregoing embodiments, as an alternative embodiment, an embodiment of the present application provides an overall flow of a data processing method, as shown in fig. 15, including the following steps:

the third party system interface management platform inputs and responds to the third party interface and the related configuration; a third party system interface management platform cache interface;

the service system uses the SDK to request the cache interface;

the third-party system interface management platform loads a cache interface, performs data processing operation on the request data, and sends the processed data to a response third-party system;

performing internal logic operation on the received processed data by the third-party system to obtain response data, and sending the response data to the third-party system interface management platform;

the third-party system interface management platform receives the response data and stores the response data;

and the third-party system interface management platform performs abnormity judgment on the response data, performs abnormity monitoring and further gives an abnormity alarm if the response data is abnormal, and transmits the response data to the service system if the response data is not abnormal.

It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.

Through the description of the foregoing embodiments, it is clear to those skilled in the art that the method according to the foregoing embodiments may be implemented by software plus a necessary general hardware platform, and certainly may also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (e.g., a ROM (Read-Only Memory)/RAM (Random Access Memory), a magnetic disk, an optical disk) and includes several instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the methods according to the embodiments of the present application.

According to another aspect of the embodiments of the present application, there is also provided a data processing platform for implementing the above-mentioned data processing method. Fig. 16 is a block diagram of a platform structure of an alternative data processing according to an embodiment of the present application, and as shown in fig. 16, the platform may include:

an obtaining module 1601, configured to obtain first service data, where the first service data is request data sent by a client;

a first determining module 1602, configured to determine a target data processing operation to be performed on the first service data;

an obtaining module 1603, configured to obtain second service data according to the target data processing operation;

a first sending module 1604, configured to send the second service data to a responding third party.

It should be noted that the acquiring module 1601 in this embodiment may be configured to execute the step S201, the first determining module 1602 in this embodiment may be configured to execute the step S202, the obtaining module 1603 in this embodiment may be configured to execute the step S203, and the first sending module 1604 in this embodiment may be configured to execute the step S204.

Through the modules, the third-party system interface management platform is arranged in the embodiment of the application, all the APIs (application program interfaces) of the third-party system responding are managed in a centralized mode through the third-party system interface management platform, various interfaces responding to the third-party system are reduced in configuration and maintenance of a client service system, request service data are processed in a unified mode through the third-party system interface management platform, redundant codes and code complexity can be effectively reduced, and the problem that a large amount of redundant contents are contained in project codes in the related technology is solved.

As an alternative embodiment, the first determining module includes:

the system comprises a first acquisition unit, a second acquisition unit and a third acquisition unit, wherein the first acquisition unit is used for acquiring a plurality of data sub-processing schemes contained in a target integrated scheme, and each data sub-processing scheme corresponds to one data processing operation;

the first adaptation unit is used for carrying out data self-adaptation on the first service data and the data sub-processing scheme to determine a target data sub-processing scheme;

a determining unit, configured to determine the target data processing operation based on the target data sub-processing scheme.

As an alternative embodiment, the data sub-processing scheme includes a route forwarding processing scheme, and the obtaining module includes:

a second obtaining unit, configured to obtain, from the first service data, an interface protocol that requests the third party to respond;

a second adapting unit, configured to automatically adapt the interface protocol according to protocol adaptation in the route forwarding processing scheme, so as to obtain a target interface, where the target interface is an interface capable of requesting the third party to respond;

and a sending unit, configured to send the second service data through the target interface, where the current second service data is the same as the first service data.

As an alternative embodiment, the data sub-processing scheme includes an interface exception retry scheme, and the obtaining module includes:

a third obtaining unit, configured to obtain request information of a first interface included in the first service data, where the first interface is any interface that requests the response of the third party;

an obtaining unit, configured to start a retry scheme for the first interface to obtain the second service data when it is determined that the number of requests corresponding to the request information of the first interface is smaller than a number threshold; or, under the condition that it is determined that the request duration corresponding to the request information of the first interface is smaller than a duration threshold, starting the retry scheme for the first interface to obtain the second service data.

As an alternative embodiment, the data sub-processing scheme includes a data simulation scheme, and the obtaining module includes:

the intercepting unit is used for intercepting the first service data under the condition that the acquired first service data contains the simulation configuration information;

and the simulation unit is used for starting simulation operation and simulating response data based on the first service data as the second service data.

As an alternative embodiment, the platform further comprises:

the first receiving module is used for receiving response information of a third responding party after the second service data is sent to the third responding party;

the starting module is used for starting a data fusing mechanism under the condition that the corresponding abnormal times in the response information are determined to be greater than or equal to a first abnormal threshold;

and the second sending module is used for sending the fusing result to the client side, or sending data stored in a database at the previous moment to the client side.

As an alternative embodiment, the data sub-processing scheme includes an abnormal alarm scheme, and the obtaining module includes:

a fourth obtaining unit, configured to obtain request information of a second interface included in the first service data, where the second interface is any interface that requests the third party to respond;

the setting unit is used for setting a preset time length as the advancing step length of a sliding window under the condition that the abnormal data of the second interface is determined to appear, and storing the abnormal data appearing in the preset time length in a database, wherein each preset time length corresponds to one sliding window;

and the alarm unit is used for triggering an abnormal alarm according to the alarm level corresponding to the target sliding window under the condition that the abnormal data contained in the target sliding window is greater than or equal to a second abnormal threshold, wherein the target sliding window is a subset of the sliding window, and each sliding window corresponds to one alarm level.

Optionally, the platform comprises:

a second receiving module, configured to receive response information fed back by a requested interface of a responding third party after the second service data is sent to the responding third party, where the response information includes a requested number of the requested interface, a success number and a failure number of the requested interface within a preset time;

the second determining module is used for determining the response time length according to the response information;

a third determining module, configured to determine, according to the response duration, the number of times out, the shortest response time, and the longest response time within the preset time;

and the display module is used for storing the response information, the overtime quantity, the shortest response time and the longest response time in a database and displaying the response information, the overtime quantity, the shortest response time and the longest response time on the client through a display tool.

According to another aspect of the embodiments of the present application, there is also provided an electronic device for implementing the above-mentioned data processing method, where the electronic device may be a server, a terminal, or a combination thereof.

Fig. 17 is a block diagram of an alternative electronic device according to an embodiment of the present disclosure, as shown in fig. 17, including a processor 1701, a communication interface 1702, a memory 1703 and a communication bus 1704, where the processor 1701, the communication interface 1702 and the memory 1703 communicate with each other via the communication bus 1704, where,

a memory 1703 for storing a computer program;

the processor 1701 is configured to execute the computer program stored in the memory 1703, and implement the following steps:

and sending the second service data to a response third party.

Alternatively, in this embodiment, the communication bus may be a PCI (Peripheral Component Interconnect) bus, an EISA (Extended Industry Standard Architecture) 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 in FIG. 17, but this does not mean 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 RAM, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory. Alternatively, the memory may be at least one memory device located remotely from the processor.

As an example, as shown in fig. 17, the memory 1703 may include, but is not limited to, an obtaining module 1601, a first determining module 1602, an obtaining module 1603, and a first sending module 1604 in the data processing platform. In addition, the present invention may also include, but is not limited to, other module units in the above-mentioned data processing platform, which is not described in detail in this example.

The processor may be a general-purpose processor, and may include but is not limited to: a CPU (Central Processing Unit), NP (Network Processor), and the like; but also a DSP (Digital Signal Processing), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component.

In addition, the electronic device further includes: and the display is used for displaying the result of the data processing.

Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment is not described herein again.

It can be understood by those skilled in the art that the structure shown in fig. 17 is only an illustration, and the device implementing the data processing method may be a terminal device, and the terminal device may be a terminal device such as a smart phone (e.g., an Android phone, an iOS phone, etc.), a tablet computer, a palm computer, a Mobile Internet Device (MID), a PAD, and the like. Fig. 17 is a diagram illustrating a structure of the electronic device. For example, the terminal device may also include more or fewer components (e.g., network interfaces, display devices, etc.) than shown in FIG. 17, or have a different configuration than shown in FIG. 17.

Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by a program instructing hardware associated with the terminal device, where the program may be stored in a computer-readable storage medium, and the storage medium may include: flash disk, ROM, RAM, magnetic or optical disk, and the like.

According to still another aspect of an embodiment of the present application, there is also provided a storage medium. Alternatively, in the present embodiment, the storage medium described above may be used for program codes of a method of executing data processing.

Optionally, in this embodiment, the storage medium may be located on at least one of a plurality of network devices in a network shown in the above embodiment.

Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps:

processing operation is carried out according to the target data to obtain second service data;

and sending the second service data to a response third party.

Optionally, the specific example in this embodiment may refer to the example described in the above embodiment, which is not described again in this embodiment.

Optionally, in this embodiment, the storage medium may include, but is not limited to: various media capable of storing program codes, such as a U disk, a ROM, a RAM, a removable hard disk, a magnetic disk, or an optical disk.

According to yet another aspect of an embodiment of the present application, there is also provided a computer program product or a computer program comprising computer instructions stored in a computer readable storage medium; the processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the method steps of data processing in any of the embodiments described above.

The above-mentioned serial numbers of the embodiments of the present application are merely for description, and do not represent the advantages and disadvantages of the embodiments.

The integrated unit in the above embodiments, if implemented in the form of a software functional unit and sold or used as a separate product, may be stored in the above computer-readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or a part of or all or part of the technical solution contributing to the prior art may be embodied in the form of a software product stored in a storage medium, and including a plurality of instructions for causing one or more computer devices (which may be personal computers, servers, network devices, or the like) to execute all or part of the steps of the method for processing data of the embodiments of the present application.

In the above embodiments of the present application, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

In the several embodiments provided in the present application, it should be understood that the disclosed client may be implemented in other manners. The above-described apparatus embodiments are merely illustrative, and for example, a division of a unit is only a logical division, and in actual implementation, there may be another division, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, and may also be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution provided in the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The foregoing is only a preferred embodiment of the present application and it should be noted that those skilled in the art can make several improvements and modifications without departing from the principle of the present application, and these improvements and modifications should also be considered as the protection scope of the present application.

Claims

1. A method of data processing, the method comprising:

and sending the second service data to a response third party.

2. The method of claim 1, wherein the determining a target data processing operation to be performed on the first traffic data comprises:

3. The method of claim 2, wherein the data sub-processing scheme comprises a route forwarding processing scheme, and wherein obtaining second service data according to the target data processing operation comprises:

4. The method of claim 2, wherein the data sub-processing scheme comprises an interface exception retry scheme, and wherein obtaining second traffic data according to the target data processing operation comprises:

acquiring request information of a first interface contained in the first service data, wherein the first interface is any interface requesting for responding to the third party;

5. The method of claim 2, wherein the data sub-processing scheme comprises a data simulation scheme, and wherein obtaining second traffic data according to the target data processing operation comprises:

6. The method of claim 1, wherein after the sending the second business data to the responding third party, the method further comprises:

receiving response information of the response third party;

7. The method of claim 2, wherein the data sub-processing scheme comprises an exception alarm scheme, and wherein obtaining second service data according to the target data processing operation comprises:

acquiring request information of a second interface contained in the first service data, wherein the second interface is any interface requesting for responding to the third party;

8. The method of claim 1, wherein after the sending the second business data to the responding third party, the method further comprises:

determining a response time length according to the response information;

determining the overtime number, the shortest response time and the longest response time in the preset time according to the response time;

9. A platform for data processing, the platform comprising:

and the first sending module is used for sending the second service data to a response third party.

10. An electronic device comprising a processor, a communication interface, a memory and a communication bus, wherein said processor, said communication interface and said memory communicate with each other via said communication bus,

the memory for storing a computer program;

the processor for performing the method steps of any one of claims 1 to 8 by running the computer program stored on the memory.

11. A computer-readable storage medium, in which a computer program is stored, wherein the computer program realizes the method steps of any one of claims 1 to 8 when executed by a processor.