Data processing method and device, electronic equipment and storage medium

Abstract

The invention discloses a data processing method and device, electronic equipment and a storage medium, and relates to the technical field of computers. A specific embodiment of the method comprises the following steps: receiving a data request sent by a front end, obtaining a data identifier, and querying associated data; in response to query failure, acquiring a disaster recovery level corresponding to the data identifier, and determining a corresponding disaster recovery type according to the data identifier and the disaster recovery level; calling a component instance associated with the disaster recovery backup type, querying a corresponding data basic parameter according to the data identifier to generate a data updating event, and triggering the data updating event; determining collaborative system information from the component instance to call a preset system collaborative interface, and obtaining target data from a collaborative system according to the data basic parameters; and sending the target data to the front end, and rendering the target data at the front end. According to the embodiment of the invention, the problem that the business processing efficiency is reduced and great inconvenience is brought to business processing due to the fact that the emergency processing mode of the business information needs to collect various information offline and manually record the information can be solved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a data processing method, device, electronic device and storage medium. Background Art

[0002] In business processing in various fields, disaster recovery emergency plans are usually set up to ensure that business processing can be carried out normally. For example, in the financial field, various businesses often involve various types of information, such as various business information required for handling loans and other businesses. Since the accuracy of this information has a great impact on business processing, emergency processing methods for corresponding business information will be set up in the disaster recovery emergency plans for these business processing. In related technologies, in order to ensure the accuracy of business information in disaster recovery scenarios, emergency processing methods usually require various information to be collected offline and manually entered, which reduces the efficiency of business processing and brings great inconvenience to business processing. Summary of the invention

[0003] In view of this, an embodiment of the present invention provides a data processing method, device, electronic device and storage medium, which can solve the problem that the emergency processing method of business information requires offline collection of various information and manual entry, resulting in reduced business processing efficiency and causing great inconvenience to business processing.

[0004] To achieve the above objective, according to one aspect of an embodiment of the present invention, a method for data processing is provided.

[0005] A data processing method according to an embodiment of the present invention includes: receiving a data request sent by a front end, obtaining a data identifier corresponding to the data request, and querying data associated with the data identifier; in response to a query failure, obtaining a disaster recovery level corresponding to the data identifier, and determining a corresponding disaster recovery type according to the data identifier and the disaster recovery level; calling a component instance associated with the disaster recovery type, and querying corresponding data basic parameters according to the data identifier to generate and trigger a data update event; in response to the data update event being triggered, determining collaborative system information from the component instance, and calling a preset system collaborative interface to obtain target data from the collaborative system according to the data basic parameters; and sending the target data to the front end, and rendering the target data by the front end.

[0006] In one embodiment, obtaining the disaster recovery level corresponding to the data identifier includes: obtaining the page component and target page associated with the data request, determining the business identifier corresponding to the target page to call the corresponding business processing flow, and identifying the processing level of the parameters in the page component in the business processing flow; determining the disaster recovery level corresponding to the data identifier based on the processing level.

[0007] In another embodiment, obtaining the disaster recovery level corresponding to the data identifier includes: obtaining a target page associated with the data request, identifying a position of a component associated with the data request in the target page, extracting an attribute tag matching the position, and determining the disaster recovery level corresponding to the data identifier based on the attribute tag.

[0008] In another embodiment, the corresponding disaster recovery type is determined according to the data identifier and the disaster recovery level, including: obtaining a corresponding update path set according to the data identifier, screening out each valid update path, determining a target path that matches the disaster recovery level according to the attribute parameters of each of the valid update paths, and determining the update type of the target path as a disaster recovery type.

[0009] In another embodiment, querying the data associated with the data identifier includes: querying the corresponding data and time information from the database according to the data identifier, and obtaining the time limit interval corresponding to the data identifier; in response to the time information not satisfying the time limit interval, determining that the query result is a query failure; in response to the time information satisfying the time limit interval, sending the queried data to the front end.

[0010] In yet another embodiment, determining collaborative system information from the component instance includes:

[0011] Identify the disaster recovery type corresponding to the data update event; in response to the disaster recovery type belonging to the first type, determine the collaborative system information from the component instance; in response to the disaster recovery type belonging to the second type, obtain the target data corresponding to the data identifier from the offline system based on the data basic parameters.

[0012] To achieve the above objective, according to another aspect of an embodiment of the present invention, a data processing device is provided.

[0013] A data processing device according to an embodiment of the present invention includes: a receiving unit, which is used to receive a data request sent by a front end, obtain a data identifier corresponding to the data request, and query the data associated with the data identifier; a determining unit, which is used to obtain a disaster recovery level corresponding to the data identifier in response to a query failure, and determine the corresponding disaster recovery type according to the data identifier and the disaster recovery level; a generating unit, which is used to call a component instance associated with the disaster recovery type, and query the corresponding data basic parameters according to the data identifier to generate and trigger a data update event; an acquiring unit, which is used to determine collaborative system information from the component instance in response to the data update event being triggered, and call a preset system collaborative interface to obtain target data from the collaborative system according to the data basic parameters; and a sending unit, which is used to send the target data to the front end, and render the target data by the front end.

[0014] In one embodiment, the determination unit is specifically used to: obtain the page component and target page associated with the data request, determine the business identifier corresponding to the target page to call the corresponding business processing flow, and identify the processing level of the parameters in the page component in the business processing flow; determine the disaster recovery level corresponding to the data identifier according to the processing level.

[0015] In another embodiment, the determination unit is specifically used to: obtain a target page associated with the data request, identify a location of a component associated with the data request in the target page, extract an attribute tag matching the location, and determine a disaster recovery level corresponding to the data identifier based on the attribute tag.

[0016] In another embodiment, the determination unit is specifically used to: obtain a corresponding update path set according to the data identifier, filter out each valid update path, determine a target path that matches the disaster recovery level according to the attribute parameters of each valid update path, and determine the update type of the target path as a disaster recovery type.

[0017] In another embodiment, the receiving unit is specifically used to: query corresponding data and time information from a database according to the data identifier, and obtain a time limit interval corresponding to the data identifier; in response to the time information not satisfying the time limit interval, determine that the query result is a query failure; in response to the time information satisfying the time limit interval, send the queried data to the front end.

[0018] In another embodiment, the acquisition unit is specifically used to: identify the disaster recovery type corresponding to the data update event; in response to the disaster recovery type belonging to the first type, determine the collaborative system information from the component instance; in response to the disaster recovery type belonging to the second type, acquire the target data corresponding to the data identifier from the offline system based on the data basic parameters.

[0019] To achieve the above objective, according to another aspect of an embodiment of the present invention, an electronic device is provided.

[0020] An electronic device according to an embodiment of the present invention includes: one or more processors; a storage device for storing one or more programs, when the one or more programs are executed by the one or more processors, the one or more processors implement the data processing method provided by the embodiment of the present invention.

[0021] To achieve the above objective, according to another aspect of an embodiment of the present invention, a computer readable medium is provided.

[0022] A computer-readable medium according to an embodiment of the present invention stores a computer program, and when the program is executed by a processor, the data processing method provided by the embodiment of the present invention is implemented.

[0023] To achieve the above objective, according to another aspect of an embodiment of the present invention, a computer program product is provided.

[0024] A computer program product according to an embodiment of the present invention includes a computer program, and when the program is executed by a processor, the data processing method provided by the embodiment of the present invention is implemented.

[0025] One embodiment of the above invention has the following advantages or beneficial effects: In the embodiment of the present invention, a connection is established between the data processing system and each collaborative system. When the data query requested by the front end fails, the corresponding disaster recovery type can be determined according to the disaster recovery level and data identification of the data, so as to generate a data update event through the associated component instance. After the data update event is triggered, the preset system collaborative interface can be called according to the collaborative system information in the component instance, so that the target data can be obtained from the collaborative system in time to be sent to the front end and rendered. In the embodiment of the present invention, for the data that failed to be queried, after the disaster recovery type is determined, the corresponding collaborative system can be determined through the component instance and the required data can be obtained from the collaborative system through the data update event. In this way, in the embodiment of the present invention, the method of obtaining data in each collaborative system as a disaster recovery emergency plan can ensure the real-time and accuracy of the data, and at the same time, it can also improve the efficiency of data acquisition, thereby improving the efficiency of business processing and avoiding great inconvenience to business processing.

[0026] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with the specific implementation manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The accompanying drawings are used to better understand the present invention and do not constitute an improper limitation of the present invention. Figure 1 is a schematic diagram of a system architecture of a data processing system according to an embodiment of the present invention; Figure 2 is a schematic diagram of a main flow of a data processing method according to an embodiment of the present invention; Figure 3 is a schematic diagram of another main flow of a data processing method according to an embodiment of the present invention; Figure 4 is a schematic diagram of another main flow of a data processing method according to an embodiment of the present invention; Figure 5 is a schematic diagram of main units of a data processing apparatus according to an embodiment of the present invention; Figure 6is another exemplary system architecture diagram to which the embodiments of the present invention can be applied; Figure 7 It is a schematic diagram of the structure of a computer system suitable for implementing the embodiment of the present invention. DETAILED DESCRIPTION

[0028] The following is a description of exemplary embodiments of the present invention in conjunction with the accompanying drawings, including various details of the embodiments of the present invention to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0029] It should be pointed out that the embodiments of the present invention and the features in the embodiments can be combined with each other without conflict. The acquisition, transmission, storage, use, and processing of data in the technical solution of this application are in compliance with the relevant provisions of national laws and regulations. In the embodiments of this application, some existing solutions in the industry such as certain software, components, and models may be mentioned, which should be considered as exemplary. Their purpose is only to illustrate the feasibility of the implementation of the technical solution of this application, but it does not mean that the applicant has or will necessarily use the solution.

[0030] An embodiment of the present invention provides a data processing system, which can be used in disaster recovery emergency scenarios of data processing. Figure 1 FIG. 1 is a system architecture diagram of a data processing system in an embodiment of the present invention. Figure 1 As shown, the data processing system may include a front end and a back end; the data processing system may establish a connection with a collaborative system to obtain data from the collaborative system by interacting with the collaborative system; the data processing system may also be connected to an offline database for offline storage of data so that offline data may be used as a backup; a deployment resource component service may also be set up in the data processing system to set up and implement disaster recovery emergency plans for each data in the data processing; the data processing system may also include a database for storing reference data.

[0031] It should be noted that, in an embodiment of the present invention, the front end can provide an interface for interacting with the user, receive the disaster recovery emergency plan input by the user, and display relevant content for viewing, editing, etc. The back end can provide an interface linked to the front end to process the request of the front end, and can also include external collaborative system calls, database services, back-end services for internal logic processing, etc. The offline database can be specifically implemented through MySQL to save the specific data used in the disaster recovery emergency plan. In some scenarios (such as offline scenarios), the data can be provided to the system for use or directly displayed. The database for storing reference data can use redis to store the data required for the execution of the disaster recovery emergency plan, etc. The collaborative system can be a third-party system that provides interface query service capabilities, etc., and can include a variety of systems, such as a user center, configuration management, automation platform, notification center, etc.

[0032] The embodiment of the present invention provides a method for data processing, which can be Figure 1 In the system architecture shown, the backend is executed, such as Figure 2 As shown, the method includes the following steps.

[0033] S201: Receive a data request sent by the front end, obtain a data identifier corresponding to the data request, and query data associated with the data identifier.

[0034] Among them, the front end can receive instructions, such as instructions for obtaining data, through a display interface or other means during the business processing, and then send a data request to the back end through an interface connected to the back end. The data request indicates that data needs to be obtained, and specifically, it can be the data required for the front end to perform business processing. The data request may include a data identifier to indicate which data is to be requested. After receiving the data request, the back end can query the associated data according to the data identifier.

[0035] It should be noted that in the embodiments of the present invention, the data associated with the data identifier is usually pre-stored. Taking the requested data as contact information as an example, the data identifier can usually be set according to the actual situation, such as the department ID, user group ID, role ID or user ID, etc., to determine which data the data identifier corresponds to according to the organizational structure information, that is, the data identifier can be bound to one or more actual contacts, and the corresponding data can include one data or multiple data.

[0036] In an embodiment of the present invention, when querying data associated with a data identifier, if the query result is empty, it means that the query has failed; if the query result is not empty, it means that the query has succeeded, and the queried data can be returned to the front end for rendering and display.

[0037] In some application scenarios, due to the requirements of business processing on the timeliness of data, after the data is queried, its timeliness needs to be judged. Therefore, the steps of querying data can be specifically performed as follows: query the corresponding data and time information from the database according to the data identifier, and obtain the time limit interval corresponding to the data identifier; in response to the time information not meeting the time limit interval, determine that the query result is a query failure; in response to the time information meeting the time limit interval, send the queried data to the front end.

[0038] The time information can indicate the storage time or update time corresponding to the data, and the time limit interval can indicate the effective time interval of the data, which can be less than 1 day, less than 1 hour, etc. Therefore, after the data is queried, this step can compare the time information with the time limit interval. If the time information does not meet the time limit interval, the query result can be determined to be a query failure; if the time information meets the time limit interval, the query result can be determined to be a query success, and the queried data is sent to the front end.

[0039] In the embodiment of the present invention, a corresponding disaster recovery emergency plan is set for each data, so after determining that the data query fails, the disaster recovery emergency plan can be started to update the data.

[0040] S202: In response to a query failure, obtaining a disaster recovery level corresponding to the data identifier, so as to determine a corresponding disaster recovery type according to the data identifier and the disaster recovery level.

[0041] After determining that the query result is a query failure, the disaster recovery level of the data can be obtained first to determine the disaster recovery type, which indicates the data update method in the disaster recovery emergency plan. The disaster recovery level is pre-set, and generally the higher the importance of the data, the higher the disaster recovery level.

[0042] Specifically, on the one hand, in the embodiment of the present invention, the disaster recovery level can be determined according to the importance of data in business processing. Therefore, it can be specifically implemented as follows: obtaining the page component and target page associated with the data request, determining the business identifier corresponding to the target page, calling the corresponding business processing flow, identifying the processing level of the parameters in the page component in the business processing flow; determining the disaster recovery level corresponding to the data identifier according to the processing level.

[0043] Since the data request is sent by the front end, and the front end display page is the business corresponding to the execution request data, the page component and target page associated with the data request can be obtained in this step. The page component is associated with the data request, and the data set associated with the component can usually be considered as the same process used as a whole in the business processing, so in this step, the importance of the data corresponding to the request data in the business processing process can be determined by the importance of the data in the page component in the business processing process. The business processing process is pre-configured, which may include the processing level of each data. The processing level can indicate the degree of necessity of this data in the business processing. For example, some data can be supplemented later, and some data cannot be missing, so different data correspond to different processing levels, and then the processing level of each data is configured in the business processing process. After identifying the processing level of the parameters in the page component in the business processing process in this step, the disaster recovery level corresponding to the data identifier can be determined. For example, a mapping relationship between the processing level and the identification level can be established, so that the disaster recovery level can be determined according to the processing level.

[0044] On the other hand, in the embodiment of the present invention, the importance of some data in business processing can also be marked in the page to prompt the user. Therefore, determining the disaster recovery level in this step can also be performed as follows: obtaining the target page associated with the data request, identifying the location of the component associated with the data request in the target page, extracting the attribute tag matching the location, and determining the disaster recovery level corresponding to the data identifier according to the attribute tag.

[0045] The marking of the importance of data in the target page is usually set at the location where the data is displayed on the page, so this step can identify the location of the component associated with the data request in the target page to extract the corresponding attribute label, such as the attribute label on the component side, etc. The attribute label can indicate the importance of the data. The attribute label can be specifically an identifier of the importance, and a corresponding relationship between each attribute label and the disaster recovery level is established, thereby determining the disaster recovery level corresponding to the data identifier.

[0046] In this step, after determining the disaster recovery level, the disaster recovery type, that is, the data update method, can be determined in combination with the data identifier. In an embodiment of the present invention, multiple update paths can be set for data update, such as updating through an offline database, updating through a collaborative system, and the collaborative system can include multiple, different collaborative systems can also represent different update paths, and the time spent on data update and the accuracy of data acquisition corresponding to each different update path are different, so in this step, a matching disaster recovery level can be set for each update path. Therefore, this step of determining the disaster recovery type can be performed as follows: obtaining the corresponding update path set according to the data identifier, screening out each valid update path, determining the target path that matches the disaster recovery level according to the attribute parameters of each valid update path, and determining the update type of the target path as the disaster recovery type.

[0047] It should be noted that, since some update paths may become infeasible due to factors such as system expansion or contraction, and some update paths may be temporarily valid or invalid, the validity of each update path can be marked in the embodiment of the present invention to screen the valid update paths.

[0048] S203: calling the component instance associated with the disaster recovery type, querying the corresponding data basic parameters according to the data identifier, so as to generate and trigger a data update event.

[0049] Among them, the component instance is pre-set, and the embodiment of the present invention sets a corresponding component instance for each update path to realize the acquisition of update data through the component instance. The component instance may include the parameters required for the corresponding update path to realize the acquisition of update data. For example, in the component instance corresponding to the update path realized by the collaborative system, the system information of the outsourced system, such as interface information and address information, etc., may be included. Since it is impossible to obtain accurate and comprehensive data only based on the data identifier during data acquisition, the data basic parameters required for obtaining the data can be stored in this step for data acquisition. For example, for the data identifier being the department ID, the contact information of the department is obtained, and the names of the employees included in the department can be set as the data basic parameters. The data update event can pre-set the corresponding template, and then generate and trigger the data update event according to the data basic parameters and the preset template.

[0050] S204: In response to the data update event being triggered, determining the collaborative system information from the component instance to call a preset system collaborative interface and obtain target data from the collaborative system according to the data basic parameters.

[0051] Among them, after the data update event is triggered, the update path can also be judged first. For example, the data update event can include a corresponding disaster recovery type. In this step, the disaster recovery type corresponding to the data update event can be identified; in response to the disaster recovery type belonging to the first type, the collaborative system information is determined from the component instance; in response to the disaster recovery type belonging to the second type, the target data corresponding to the data identifier is obtained from the offline system based on the data basic parameters.

[0052] The first type indicates obtaining data through a collaborative system, and the second type indicates obtaining data through an offline system. Therefore, when it is determined in this step that the disaster recovery type belongs to the first type, the collaborative system information is determined from the component instance; when it is determined that the disaster recovery type belongs to the second type, the target data corresponding to the data identifier is obtained from the offline system based on the data basic parameters. The offline system can specifically be an offline database.

[0053] It should be noted that after obtaining the target data, the data corresponding to the data identifier in the offline database and the reference data can be updated.

[0054] S205: Send the target data to the front end so that the front end renders the target data.

[0055] After obtaining the target data, it can be returned to the front end for data display.

[0056] In an embodiment of the present invention, the front end can develop various component implementations based on the plug-in of tinymce (editor). All components can be defined as div elements in HTML, including the following five attributes: mce-dms-id: represents the unique ID of the component, which is also the ID of offline data; mce-dms-class-type: represents the type of component, such as user component, deployment resource component; mce-dms-data: stores the complete offline data of the component; mce-dms-data-key: stores the reference data key of the component; mce-dms-front: stores the front-end style of the component. Component matching: Scan the div element with the mce-dms-class-type attribute through the component scanner, and match the corresponding react component according to the value of the attribute mce-dms-class-type. Component rendering: When in offline mode, the component can directly render data and style according to the values ​​of mce-dms-data and mce-dms-front; when in non-offline mode, the component can obtain the referenced real-time data from the back end according to the values ​​of mce-dms-class-type and mce-dms-data-key before rendering. The offline mode may refer to a method of obtaining updated data through an offline system, and the non-offline mode may refer to a method of obtaining updated data through a non-offline system.

[0057] In an embodiment of the present invention, for data that fails to be queried, after determining the disaster recovery type, the corresponding collaborative system can be determined through the component instance and the required data can be obtained from the collaborative system through the data update event. In this way, the method of obtaining data in each collaborative system as a disaster recovery emergency plan in the embodiment of the present invention can ensure the real-time and accuracy of the data, and at the same time, it can also improve the efficiency of data acquisition, thereby improving the efficiency of business processing and avoiding great inconvenience to business processing.

[0058] Combine the following Figure 1 The system architecture shown in the figure specifically describes the data processing method in the embodiment of the present invention. Figure 3 As shown, the method includes the following steps.

[0059] S301: Receive a data request sent by the front end, obtain a data identifier corresponding to the data request, and query data associated with the data identifier.

[0060] S302: In response to a query failure, obtain the page component and target page associated with the data request, determine the business identifier corresponding to the target page, call the corresponding business processing flow, and identify the processing level of the parameters in the page component in the business processing flow.

[0061] S303: Determine the disaster recovery level corresponding to the data identifier according to the processing level.

[0062] S304: calling the component instance associated with the disaster recovery type, querying the corresponding data basic parameters according to the data identifier, so as to generate and trigger a data update event.

[0063] S305: In response to a data update event being triggered, identifying a disaster recovery type corresponding to the data update event.

[0064] S306: In response to the disaster recovery type belonging to the first type, determining the collaborative system information from the component instance to call a preset system collaborative interface, and obtaining target data from the collaborative system according to the data basic parameters.

[0065] S307: In response to the disaster recovery type belonging to the second type, acquiring target data corresponding to the data identifier from the offline system based on the data basic parameters.

[0066] S308: Send the target data to the front end so that the front end renders the target data.

[0067] It should be noted that the data processing principle in the embodiment of the present invention is the same as Figure 2 The corresponding data processing principles in the illustrated embodiments are the same and will not be described in detail here.

[0068] Combine the following Figure 1 The system architecture shown in the figure specifically describes the data processing method in the embodiment of the present invention. Figure 4 As shown, the method includes the following steps.

[0069] S401: Receive a data request sent by the front end, obtain a data identifier corresponding to the data request, query corresponding data and time information from a database according to the data identifier, and obtain a time limit interval corresponding to the data identifier.

[0070] S402: In response to the time information not satisfying the time limit interval, determining that the query result is a query failure.

[0071] S403: In response to the time information satisfying the time limit interval, the queried data is sent to the front end.

[0072] S404: Obtain the disaster recovery level corresponding to the data identifier, so as to determine the corresponding disaster recovery type according to the data identifier and the disaster recovery level.

[0073] S405: calling the component instance associated with the disaster recovery type, querying the corresponding data basic parameters according to the data identifier, so as to generate and trigger a data update event.

[0074] S406: In response to the data update event being triggered, determine the collaborative system information from the component instance to call a preset system collaborative interface and obtain target data from the collaborative system according to the data basic parameters.

[0075] S407: Send the target data to the front end so that the front end renders the target data.

[0076] It should be noted that the data processing principle in the embodiment of the present invention is the same as Figure 2 The corresponding data processing principles in the illustrated embodiments are the same and will not be described in detail here.

[0077] In order to solve the problems existing in the prior art, an embodiment of the present invention provides a data processing device 500, such as Figure 5 As shown, the device 500 includes: a receiving unit 501, which is used to receive a data request sent by a front end, obtain a data identifier corresponding to the data request, and query the data associated with the data identifier; a determining unit 502, which is used to obtain a disaster recovery level corresponding to the data identifier in response to a query failure, so as to determine the corresponding disaster recovery type according to the data identifier and the disaster recovery level; a generating unit 503, which is used to call a component instance associated with the disaster recovery type, query the corresponding data basic parameters according to the data identifier, so as to generate and trigger a data update event; an acquiring unit 504, which is used to determine the collaborative system information from the component instance in response to the data update event being triggered, so as to call a preset system collaborative interface, and obtain the target data from the collaborative system according to the data basic parameters; a sending unit 505, which is used to send the target data to the front end so that the front end renders the target data.

[0078] It should be understood that the manner of implementing the embodiments of the present invention is different from the Figure 2 The method of the illustrated embodiment is the same and will not be repeated here.

[0079] In one embodiment, the determination unit 502 is specifically used to: obtain the page component and target page associated with the data request, determine the business identifier corresponding to the target page to call the corresponding business processing flow, and identify the processing level of the parameters in the page component in the business processing flow; determine the disaster recovery level corresponding to the data identifier according to the processing level.

[0080] In another embodiment, the determination unit 502 is specifically used to: obtain a target page associated with the data request, identify a location of a component associated with the data request in the target page, extract an attribute tag matching the location, and determine a disaster recovery level corresponding to the data identifier based on the attribute tag.

[0081] In another embodiment, the determination unit 502 is specifically used to: obtain a corresponding update path set according to the data identifier, filter out each valid update path, determine a target path that matches the disaster recovery level according to the attribute parameters of each valid update path, and determine the update type of the target path as a disaster recovery type.

[0082] In another embodiment, the receiving unit 501 is specifically used to: query corresponding data and time information from the database according to the data identifier, and obtain the time limit interval corresponding to the data identifier; in response to the time information not satisfying the time limit interval, determine that the query result is a query failure; in response to the time information satisfying the time limit interval, send the queried data to the front end.

[0083] In another embodiment, the acquisition unit 504 is specifically used to: identify the disaster recovery type corresponding to the data update event; in response to the disaster recovery type belonging to the first type, determine the collaborative system information from the component instance; in response to the disaster recovery type belonging to the second type, acquire the target data corresponding to the data identifier from the offline system based on the data basic parameters.

[0084] It should be understood that the manner of implementing the embodiments of the present invention is different from the Figure 2 , 3 , and the method of the embodiment shown in 4 is the same and will not be repeated here.

[0085] In an embodiment of the present invention, for data that fails to be queried, after determining the disaster recovery type, the corresponding collaborative system can be determined through the component instance and the required data can be obtained from the collaborative system through the data update event. In this way, the method of obtaining data in each collaborative system as a disaster recovery emergency plan in the embodiment of the present invention can ensure the real-time and accuracy of the data, and at the same time, it can also improve the efficiency of data acquisition, thereby improving the efficiency of business processing and avoiding great inconvenience to business processing.

[0086] According to an embodiment of the present invention, the embodiment of the present invention further provides an electronic device and a readable storage medium.

[0087] The electronic device of an embodiment of the present invention comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the one processor, and the instructions are executed by the at least one processor so that the at least one processor executes the data processing method provided by the embodiment of the present invention.

[0088] Figure 6 An exemplary system architecture 600 is shown to which the data processing method or data processing apparatus according to the embodiment of the present invention can be applied.

[0089] like Figure 6 As shown, system architecture 600 may include terminal devices 601, 602, 603, network 604 and server 605. Network 604 is used to provide a medium for communication links between terminal devices 601, 602, 603 and server 605. Network 604 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0090] The user can use the terminal devices 601, 602, 603 to interact with the server 605 through the network 604 to receive or send messages, etc. Various client applications can be installed on the terminal devices 601, 602, 603.

[0091] The terminal devices 601 , 602 , and 603 may be, but are not limited to, smart phones, tablet computers, laptop computers, and desktop computers, etc.

[0092] The server 605 may be a server that provides various services. The server may analyze and process the received data such as the product information query request, and feed back the processing result (such as product information - just an example) to the terminal device.

[0093] It should be noted that the data processing method provided in the embodiment of the present invention is generally executed by the server 605 , and accordingly, the data processing device is generally set in the server 605 .

[0094] It should be understood that Figure 6 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0095] Reference below Figure 7 , which shows a schematic diagram of the structure of a computer system 700 suitable for implementing an embodiment of the present invention. Figure 7 The computer system shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0096] like Figure 7As shown, the computer system 700 includes a central processing unit (CPU) 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage part 708 into a random access memory (RAM) 703. In the RAM 703, various programs and data required for the operation of the system 700 are also stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other through a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0097] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, a mouse, etc.; an output section 707 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, a modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 710 as needed, so that a computer program read therefrom is installed into the storage section 708 as needed.

[0098] In particular, according to the embodiments disclosed in the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present invention include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 709, and / or installed from the removable medium 711. When the computer program is executed by the central processing unit (CPU) 701, the above-mentioned functions defined in the system of the present invention are executed.

[0099] It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present invention, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0100] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present invention. In this regard, each box in the flow chart or block diagram can represent a unit, a program segment, or a part of a code, and the above-mentioned unit, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0101] The units involved in the embodiments of the present invention may be implemented by software or hardware. The units described may also be set in a processor, for example, it may be described as: a processor includes a receiving unit, a determining unit, a generating unit, an acquiring unit, and a sending unit. The names of these units do not constitute limitations on the units themselves in some cases, for example, the receiving unit may also be described as a "unit with a receiving function".

[0102] As another aspect, the present invention further provides a computer-readable medium, which may be included in the device described in the above embodiment; or may exist independently without being assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by a device, the device executes the data processing method provided by the present invention.

[0103] As another aspect, the present invention further provides a computer program product, including a computer program, which, when executed by a processor, implements the data processing method provided by an embodiment of the present invention.

[0104] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for data processing, characterized in that: include: Receive a data request sent by the front end, obtain a data identifier corresponding to the data request, and query the data associated with the data identifier; In response to a query failure, obtaining a disaster recovery level corresponding to the data identifier, so as to determine a corresponding disaster recovery type according to the data identifier and the disaster recovery level; Calling the component instance associated with the disaster recovery type, querying the corresponding data basic parameters according to the data identifier, so as to generate and trigger a data update event; In response to the data update event being triggered, determining the collaborative system information from the component instance to call a preset system collaborative interface and obtain target data from the collaborative system according to the data basic parameters; The target data is sent to a front end so that the front end renders the target data.

2. The method according to claim 1, characterized in that: Obtaining the disaster recovery level corresponding to the data identifier includes: Obtaining the page component and the target page associated with the data request, determining the business identifier corresponding to the target page, invoking the corresponding business processing flow, and identifying the processing level of the parameters in the page component in the business processing flow; A disaster recovery level corresponding to the data identifier is determined according to the processing level.

3. The method according to claim 1, characterized in that Obtaining the disaster recovery level corresponding to the data identifier includes: A target page associated with the data request is obtained, a position of a component associated with the data request in the target page is identified, an attribute tag matching the position is extracted, and a disaster recovery level corresponding to the data identifier is determined according to the attribute tag.

4. The method according to claim 1, characterized in that: Determining a corresponding disaster recovery type according to the data identifier and the disaster recovery level includes: A corresponding update path set is obtained according to the data identifier, valid update paths are screened out, a target path matching the disaster recovery level is determined according to attribute parameters of each valid update path, and the update type of the target path is determined as a disaster recovery type.

5. The method according to claim 1, characterized in that: Querying the data associated with the data identifier includes: According to the data identifier, query the corresponding data and time information from the database to obtain the time limit interval corresponding to the data identifier; In response to the time information not satisfying the time limit interval, determining the query result as a query failure; in response to the time information satisfying the time limit interval, sending the queried data to the front end.

6. The method according to claim 1, characterized in that Determining collaborative system information from the component instance includes: Identify the disaster recovery type corresponding to the data update event; In response to the disaster recovery type belonging to the first type, determining the collaborative system information from the component instance; in response to the disaster recovery type belonging to the second type, acquiring the target data corresponding to the data identifier from the offline system based on the data basic parameters.

7. A data processing device, characterized in that: include: A receiving unit, configured to receive a data request sent by a front end, obtain a data identifier corresponding to the data request, and query data associated with the data identifier; a determining unit, configured to obtain, in response to a query failure, a disaster recovery level corresponding to the data identifier, so as to determine a corresponding disaster recovery type according to the data identifier and the disaster recovery level; A generating unit, configured to call a component instance associated with the disaster recovery type, query a corresponding data basic parameter according to the data identifier, so as to generate and trigger a data update event; an acquisition unit, configured to determine the collaborative system information from the component instance in response to the data update event being triggered, so as to call a preset system collaborative interface and acquire target data from the collaborative system according to the data basic parameters; The sending unit is used to send the target data to the front end so that the front end renders the target data.

8. The device according to claim 7, characterized in that The determining unit is specifically configured to: Obtaining the page component and the target page associated with the data request, determining the business identifier corresponding to the target page, invoking the corresponding business processing flow, and identifying the processing level of the parameters in the page component in the business processing flow; A disaster recovery level corresponding to the data identifier is determined according to the processing level.

9. The device according to claim 7, characterized in that The determining unit is specifically configured to: A target page associated with the data request is obtained, a position of a component associated with the data request in the target page is identified, an attribute tag matching the position is extracted, and a disaster recovery level corresponding to the data identifier is determined according to the attribute tag.

10. An electronic device, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 6.

11. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

12. A computer program product, comprising a computer program, characterized in that When the program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

Images