Disclosure of Invention
Accordingly, the present invention is directed to a method, an apparatus, a server, and a readable storage medium for processing archive data, which can implement unified scheduling and coordination of archive data stored in a public cloud server and each privately-owned server, so that archive data stored in the privately-owned server can be processed rapidly and accurately, and the operation and maintenance costs of an archive data management platform can be reduced significantly.
In a first aspect, an embodiment of the present invention provides a method for processing archive data, which is applied to an archive data management platform, where the archive data management platform includes a public cloud server end and a plurality of privately-owned server ends, where the public cloud server end stores an archive user table, and the archive user table is used to characterize a mapping relationship between privately-owned alias labels and access addresses of the privately-owned server ends, and the method includes:
receiving an archive processing request sent by a terminal through the public cloud server;
if the archive processing request carries a first privately-arranged alias tag, determining a target access address corresponding to the first privately-arranged alias tag based on the archive user table by the public cloud server, and establishing communication connection between the terminal and a target privately-arranged server terminal based on the target access address;
And responding to the file processing request through the target privateization server side to obtain a file processing result.
In one implementation, the privatized server side is deployed with a first message unit and a data capturing unit, and the public cloud server side is deployed with a second message unit, and the method further includes:
Determining changed target user data when the user data stored in the archive user table is monitored to be changed through the data capturing unit, and sending the target user data to a user pushing Topic in the first message unit;
Pushing the target user data stored in the Topic for the user through the first message unit, marking a data change type tag and a second privately-owned alias tag, and sending the target user data, the data change type tag and the second privately-owned alias tag to the second message unit of the public cloud server in an associated manner;
And updating the archive user table based on the target user data, the data change type tag and the second privately-owned alias tag through the second message unit.
In one embodiment, pushing the target user data stored in Topic for the user, tagging a data change type tag and a second privately-aliased tag, includes:
Newly adding a type field and an alias field in the target user data;
Assigning the data change type of the target user data to the type field to obtain a data change type label; and assigning the preset privately-assigned alias to the alias field to obtain a second privately-assigned alias tag.
In one embodiment, the public cloud server is in communication connection with a public cloud database, the public cloud database is used for storing user data, and updating the archive user table based on the target user data, the data change type tag and the second privately owned alias tag comprises:
If the data change type label is a new type, storing the target user data into the public cloud database, determining an access address corresponding to the second privately-arranged alias label, and storing the second privately-arranged alias label and the access address corresponding to the second privately-arranged alias label in an associated mode into the archive user table;
If the data change type is a modification type and the second privately-owned alias tag is stored in the archive user table, updating the target user data to the public cloud database;
And if the data change type is a deletion type, the second privately-arranged alias tag is removed from the archive user table.
In one embodiment, the archive processing request includes a first query request, the archive processing result includes a first archive query result, the privatized server is in communication connection with a privatized database, the privatized database is used for storing private archive data, the target privatized server responds to the archive processing request to obtain an archive processing result, and the archive processing result is fed back to the terminal, including:
retrieving, by the privating server, the privating database based on the first query request to obtain private archive data corresponding to the first query request;
and taking the private archive data corresponding to the first query request as a first archive query result.
In one embodiment, the archive processing request includes a second query request, the archive processing result includes a second archive query result, the public cloud server is in communication connection with a public cloud database, the public cloud database is further used for storing public archive data, and the method further includes:
If the second query request does not carry the first privately-owned alias tag, searching in the public cloud database based on the second query request through the public cloud server end to obtain public archive data corresponding to the second query request;
And taking the public file data corresponding to the second query request as a second file query result.
In one embodiment, the method further comprises:
and feeding back the archive processing result to the terminal through the public cloud server or the target privateization server so as to display the archive processing result through a graphical user interface of the terminal.
In a second aspect, an embodiment of the present invention further provides a processing device of archive data, which is applied to an archive data management platform, where the archive data management platform includes a public cloud server end and a plurality of privately-owned server ends, where the public cloud server end stores an archive user table, where the archive user table is used to characterize a mapping relationship between privately-owned alias labels and access addresses of the privately-owned server ends, and the device includes:
the public cloud server is used for receiving an archive processing request sent by the terminal;
The public cloud server is further used for determining a target access address corresponding to the first privately-owned alias tag based on the archive user table if the archive processing request carries the first privately-owned alias tag, and establishing communication connection between the terminal and a target privately-owned server terminal based on the target access address;
and the target privateization server side is used for responding to the archive processing request to obtain an archive processing result.
In a third aspect, embodiments of the present invention also provide a server comprising a processor and a memory storing computer executable instructions executable by the processor, the processor executing the computer executable instructions to implement the method of any one of the first aspects.
In a fourth aspect, embodiments of the present invention also provide a computer-readable storage medium storing computer-executable instructions which, when invoked and executed by a processor, cause the processor to implement the method of any one of the first aspects.
The embodiment of the invention provides a method, a device, a server and a readable storage medium for processing file data, which are applied to a file data management platform, wherein the file data management platform comprises a public cloud server and a plurality of privately-arranged server sides, the public cloud server side stores a file user table, the file user table is used for representing a mapping relation between privately-arranged alias labels and access addresses of the privately-arranged server sides, firstly, a file processing request sent by a terminal is received through the public cloud server side, when the file processing request carries a first privately-arranged alias label, a target access address corresponding to the first privately-arranged alias label is determined based on the file user table, communication connection between the terminal and the target privately-arranged server sides is established based on the target access address, and finally, the file processing request can be responded through the target privately-arranged server sides to obtain a file processing result. The method realizes user synchronization through the archives user table stored in the public cloud server, the public cloud server receives the archives processing request sent by the terminal, establishes communication connection between the terminal and the target privately-owned server according to the target access address corresponding to the first privately-owned alias tag, which is equivalent to forwarding the archives processing request to the target privately-owned server, according to the embodiment of the invention, through adopting a user synchronization and policy forwarding mode, file retrieval can still be realized under the condition of environment isolation, and unified scheduling and coordination of file data stored in the public cloud server end and each privately-owned server end are realized, so that the file data stored in the privately-owned server end can be rapidly and accurately processed, and the operation and maintenance cost of a file data management platform can be remarkably reduced.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
In order to make the above objects, features and advantages of the present invention more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the present invention will be clearly and completely described in conjunction with the embodiments, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
At present, with the development of services, users' demands are increasing, and users hope to be able to query their own file system data on public cloud applets or APP (Application). However, since the environments are isolated, and the data is stored in different environments, if a proprietary deployment environment builds a applet, the later maintenance cost will be greatly increased, such as the need for upgrading versions, thus increasing the operation and maintenance iteration cost.
Based on the above, the embodiment of the invention provides a method, a device, a server and a readable storage medium for processing archive data, which can realize unified scheduling and coordination of archive data stored in a public cloud server end and each privately-owned server end, so that the archive data stored in the privately-owned server end can be processed rapidly and accurately, and the operation and maintenance cost of an archive data management platform can be obviously reduced.
For the convenience of understanding the present embodiment, first, a detailed description is given of a method for processing archive data disclosed in the present embodiment, which is applied to an archive data management platform, where the archive data management platform includes a public cloud server side and a plurality of privately-owned server sides, the public cloud server side stores an archive user table, and the archive user table is used to characterize a mapping relationship between privately-owned alias labels and access addresses of the privately-owned server sides, and refer to a flow diagram of a method for processing archive data shown in fig. 1, and the method mainly includes steps S102 to S106 below:
Step S102, receiving a file processing request sent by a terminal through a public cloud server. The archive processing request may include a query request, a modify/add/delete request, and the like. In one embodiment, the terminal is provided with an APP corresponding to the archive data management platform, and the terminal can establish communication connection with the public cloud server through the APP, so that the public cloud server can receive an archive processing request sent by the terminal through the APP.
Step S104, if the archive processing request carries the first privately-arranged alias tag, determining a target access address corresponding to the first privately-arranged alias tag based on the archive user table through the public cloud server side, and establishing communication connection between the terminal and the target privately-arranged server side based on the target access address. The first privately-owned alias tag can understand a unique user identification of a user on the archive data management platform, and is used for marking that the user belongs to a user at a privately-owned server side.
In one embodiment, if the archive processing request carries the first privately-owned alias tag, it is indicated that the user belongs to the user of the privately-owned server, and at this time, a target access address corresponding to the first privately-owned alias tag is searched in the archive user table, so that a communication connection between the terminal and the target privately-owned server is established based on the target access address, and archive data of the user is stored in a privately-owned database connected to the target privately-owned server.
In another embodiment, if the archive processing request does not carry the first privately-owned alias tag, it is indicated that the user belongs to the user of the public cloud server, and the archive processing request is responded directly through the public cloud server.
Step S106, responding to the file processing request through the target privateization server side to obtain a file processing result. In one embodiment, the file processing request can be forwarded to the target privately owned server through the public cloud server, the target privately owned server responds to the file processing request, and the file processing result is fed back to the terminal through the target privately owned server. By way of example, assuming that the archive processing request is a query request, privatization of the connection at the target privatization server the corresponding private archive data is found in the database, and feeding the private archive data back to the terminal as an archive processing result.
According to the file data processing method provided by the embodiment of the invention, user synchronization is realized through the file user table stored in the public cloud server, the public cloud server receives the file processing request sent by the terminal, and communication connection between the terminal and the target privately-arranged server is established according to the target access address corresponding to the first privately-arranged alias label, which is equivalent to forwarding the file processing request to the target privately-arranged server.
In order to reduce the operation and maintenance cost of the archive data management platform, the embodiment of the invention provides a method for synchronizing privately-owned user data to public cloud service based on user synchronization, and allowing privately-owned users to log in public cloud applets/apps through policy forwarding, and forwarding user access requests of all environments to the privately-owned environments, so that archive retrieval is realized. The embodiment of the invention aims to solve the problems that a privately-owned user cannot log in an applet/app (public cloud environment) due to environmental isolation, so that files cannot be read on a mobile phone, and the public cloud files of the user are read by adopting a mode of user synchronization and strategy forwarding, so that the inquiry of a file system is realized more efficiently, and the later maintenance cost is reduced to a great extent.
In order to facilitate understanding of the archive data management platform, the embodiment of the invention provides an archive data management platform, which comprises a public cloud server and a plurality of privately-owned server ends, wherein the public cloud server ends are respectively in communication connection with a terminal and each privately-owned server end. The public cloud server is connected with a public cloud database, the public cloud database is used for storing user data and public file data, the privating server is connected with a privating database, and the privating database is used for storing private file data.
In practical application, before executing the foregoing step S102, it is necessary to maintain the archive user table stored in the public cloud server, so as to better maintain the archive user table, and in the embodiment of the present invention, the privately-owned server is provided with a first message unit and a data capturing unit, and the public cloud server is provided with a second message unit, where the first message unit is a Kafka unit (denoted as a first Kafka unit) deployed in the privately-owned server, the data capturing unit is a Debezium unit, and the second message unit is a Kafka unit (denoted as a second Kafka unit) deployed in the public cloud server.
In practical application, the privately-owned server side designs a user-synchronized data synchronization model, monitors data by using kafka+ Debezium, and sends data change to a second Kafka unit of the public cloud server side by using codes of the privately-owned server side. The public cloud server end designs a user-synchronized data receiving model, processes information on privately-owned data (namely changed target user data) received by the second Kafka unit, synchronizes different data aiming at adding and deleting modification, and identifies a source.
For easy understanding, the embodiment of the present invention provides an implementation manner of maintaining a profile user table, see the following steps 1 to 3:
And step 1, determining changed target user data when the user data stored in the archive user table is monitored to be changed through the data capturing unit, and sending the target user data to the user push Topic in the first message unit. In one embodiment, the message user who created the first kafka unit pushes Topic, listens to the archive user table of the database using Debezium units, and when Debezium unit listens to the change in DML statement (add, modify, delete) of data, it sends the data to the user who created the first kafka unit pushes Topic.
And step 2, pushing target user data stored in the Topic for the user through the first message unit, marking the data change type label and the second privately-owned alias label, and sending the target user data, the data change type label and the second privately-owned alias label to the second message unit of the public cloud server side in an associated manner. The embodiment of the invention also provides an implementation mode for pushing the target user data stored in the Topic, marking the data change type label and the second privately-arranged alias label for the user, which is shown in the following steps 2.1 to 2.2:
Step 2.1, adding a type field and an alias field in the target user data. Wherein the value of the type field is used to characterize the data change type tag and the value of the alias field is used to characterize the second proprietary alias tag.
And 2.2, assigning the data change type of the target user data to the type field to obtain a data change type label, and assigning the preset privately-assigned alias to the alias field to obtain a second privately-assigned alias label. In one embodiment, the customer code of the privately-owned server monitors, when a user pushes a Topic, and when a message arrives in the user pushes the Topic, the customer code of the privately-owned server sends target user data to the user synchronization Topic of the second Kafka unit of the public cloud server, which is configured with the account password. Taking the type field as an example, a field type (i.e., a type field) is added, the value of the newly added type is add, the value of the modified type is update, and the value of the deleted type is Del. Taking the alias field as an example, a privately-assigned alias such as the industry-line naming ICBC, the maritime education naming hailiangEdu, and the like is set in advance, and then the value of the alias field is set as the privately-assigned alias.
For example, when the name of the user changes or the mailbox is modified, the Debezium unit monitors the change of the data and the changed data, sends the data to the first Kafka unit of the privately-owned server, then the code of the privately-owned server consumes the message, marks the target user data with a data change type tag and a privately-owned alias tag, and sends the target user data, the data change type tag and the privately-owned alias tag to the second Kafka unit of the public cloud server.
And 3, updating the archive user table based on the target user data, the data change type tag and the second privately-owned alias tag through a second message unit. The embodiment of the invention also provides an implementation manner for updating the archive user table, which is shown in the following steps 3.1 to 3.3:
And 3.1, if the data change type label is a new type, storing target user data into a public cloud database, determining an access address corresponding to the second privately-arranged alias label, and storing the second privately-arranged alias label and the access address corresponding to the second privately-arranged alias label in an archive user table in an associated mode. Wherein the second Kafka unit is provided with a user synchronization Topic. In one embodiment, the public and server end will monitor the user to synchronize Topic, when there is message, the consumer of the second Kafka unit code will consume the message immediately, judge the data change type. If the data is newly added, the target user data is inserted into a public cloud database, the identity (Identity document, identity number) in the target user data is ensured to be consistent, wherein the identity (Identity document) can be ensured to be unique by adopting a snowflake algorithm, and the privately-owned alias tag is also inserted into the archive user table.
And 3.2, if the data change type is a modification type and the second privately-owned alias tag is stored in the archive user table, updating the target user data to the public cloud database. In one embodiment, when the data is modified, the data is queried through the ID of the target user data, and in order to make a compensation mechanism when the message is lost, the embodiment of the present invention further determines whether the user exists, if not, the foregoing step 3.1 is executed, and if so, the modification is performed.
And 3.3, if the data change type is the deletion type, removing the second privately-owned alias tag from the file user table. In one embodiment, when the data is deleted, then the archive user table in the public cloud database is deleted directly by the ID of the target user data.
In order to facilitate understanding of the foregoing embodiments, the embodiments of the present invention provide a functional block diagram of a method for processing archive data as shown in fig. 2, at a privately-owned server, monitor MySQL (i.e. the privately-owned database) electronic archive data user changes (including adding or deleting) at the privately-owned server through a Debezium unit, if it is monitored that user data changes, send the changed target user data to a user push Topic of a first Kafka unit, a privately-owned service monitors the user push Topic, marks a tag for the target user data stored in the user push Topic, sends the target user data marked with the tag to a user synchronization Topic of a second Kafka unit of SaaS (i.e. the public cloud server), monitors user synchronization Topic, and synchronizes the target user data to MySQL of SaaS through a service agent (i.e. the public cloud database).
The data synchronization provided by the embodiment of the invention relates to how the privately-owned archival user table monitors changes, how the privately-owned archival user table is marked and then sent to public cloud, and how the public cloud synchronizes to the public cloud SaaS archival user table after receiving the data, which is the core technology of the embodiment of the invention. When the method is specifically implemented, the privately owned archive users synchronize to the data transmission flow of public cloud archive users, so that the defects that data loss, less data, untimely and the like are easily caused by a traditional archive user transmission mode are avoided, and the experience of the users and the accuracy and instantaneity of the data are greatly improved based on stream operation.
On the basis of the foregoing embodiments, the embodiments of the present invention explain steps S102 to S106. In practical applications, the terminal (i.e. mobile terminal) program or APP may be based on the foregoing embodiments, so as to perform near real-time processing of data. The user logs in the verification account password, judges the identification, carries out domain name data forwarding aiming at different identifications, and forwards the requests of users with different sources to the corresponding privately-owned server side. Specifically, when the user logs in the applet or the app, the login interface requests the public cloud server, and because the user is already synchronized into the public cloud database, the password is checked at the moment, if the password does not exist, the user is prompted to be not exist, and if the password exists, the privately-owned alias tag field is judged.
The embodiment of the invention provides two implementations as follows for respectively aiming at whether the second query request carries the first privately-arranged alias tag or not:
The file processing request comprises a first query request, and the file processing result comprises a first file query result. When the second query request carries the first privately-owned alias tag, determining a target access address corresponding to the first privately-owned alias tag based on a file user table through a public cloud server, establishing communication connection between a terminal and the target privately-owned server based on the target access address, and searching in a privately-owned database based on the first query request through the privately-owned server to obtain private file data corresponding to the first query request, wherein the private file data corresponding to the first query request is used as a first file query result.
In practical application, if the privately-owned alias tag is not empty, the representative data is privately-owned user data, and because the public cloud server side does not privately-owned data, the interface request address configured by the privately-owned alias tag is queried through an interface, such as wwwww.baidu.com, and subsequent requests are all forwarded to the area below the domain name for access.
And (II) the file processing request comprises a second query request, and the file processing result comprises a second file query result. And when the second query request does not carry the first privately-owned alias tag, searching in a public cloud database based on the second query request through the public cloud server end to obtain public file data corresponding to the second query request, and taking the public file data corresponding to the second query request as a second file query result.
In practice, if the privately-placed alias tag is empty, the representative data is data of a public cloud itself, the applet will remain unchanged and all subsequent requests are handled by public cloud server side by default.
After the corresponding archive data is obtained through inquiry, the archive processing result can be fed back to the terminal through the public cloud server or the target privately-owned server, so that the archive processing result can be displayed through a graphical user interface of the terminal. In the concrete implementation, if the privately-arranged alias tag is not empty, inquiring and feeding back the file processing result through the target privately-arranged server, if the target privately-arranged server is empty, inquiring and feeding back the file processing result through the public cloud server, and finally displaying the file processing result through the applet or the APP of the terminal. In practical application, the user side reviews and inquires, the users of different data platforms can acquire the requests of different servers, the privately-owned users can log in the public cloud platform due to the synchronization of the user data, and the data requests after logging in are actually all accessed to the corresponding privately-owned servers due to the forwarding of the flow strategy by the codes, so that the consistency and the accuracy of the data are ensured.
In order to facilitate understanding of the foregoing embodiments, the embodiment of the present invention provides a functional block diagram of another archive data processing method shown in fig. 3, where a user accesses and logs in a SaaS applet or APP, verifies an account filled by the user, exits if not, determines whether the account carries a first privately-owned alias tag if not, continues to request SaaS to attempt to retrieve if there is no tag, queries a target access address corresponding to the first privately-owned alias tag if there is a tag, and accesses a corresponding privately-owned server terminal based on the target access address to attempt to retrieve.
When the archive applet logs in and inquires, based on the privacy tag label policy management, the data is accurately forwarded to the corresponding database, so that the defect that public cloud does not privately exist the data is avoided, the data is accurate, and the usability of codes is greatly improved. The embodiment of the invention applies the strategy of forwarding different domain name traffic based on the label, so that the mobile terminal can access proprietary data, the data seen by different enterprise users are inconsistent, the data is sourced from a plurality of different proprietary servers, and the mutually isolated data can be displayed on one platform, which is also one of the innovation points of the embodiment of the invention.
The embodiment of the invention can ensure the accuracy and the integrity of the query result while solving the problem that the privately-used user cannot log in the public cloud applet, and avoids the possible problems of other query schemes.
In summary, the method for processing archive data provided by the embodiment of the present invention has at least the following characteristics:
(1) The operation and maintenance cost is reduced, because the environment is isolated, the data is asynchronous, if the scheme is not adopted, independent applets or APP can not be independently deployed for each privatization, the cost of later-stage upgrading is greatly increased, the number of code deployment and release is increased, the larger operation and maintenance cost can be increased, the operation and maintenance cost is greatly reduced through user synchronization and flow strategy forwarding, convenience is provided for code maintenance, and only one set of codes is required to be maintained.
(2) The method and the device for the user experience are capable of enabling the user to more quickly and accurately inquire the data of the privately owned environment, enabling the user to access the data on the mobile phone, and improving the user experience.
(3) The embodiment of the invention realizes a data user synchronization mechanism and a flow forwarding strategy, ensures the synchronous updating of user data of the saas platform and ensures the consistency of the data. And the flow is forwarded to the corresponding server, so that the accuracy of the data is ensured.
(4) Real-time performance the implementation scheme of the embodiment of the invention is based on monitoring the change of the archival user table of the database by Debezium, and timely reacting after the data change. When the user data changes, the data can be transmitted to public cloud to change, so that the real-time property of the data is ensured.
Therefore, the embodiment of the invention has higher practicability and market value.
For the method for processing archive data provided in the foregoing embodiment, an embodiment of the present invention provides a processing device for archive data, which is applied to an archive data management platform, where the archive data management platform includes a public cloud server and a plurality of privately-owned servers, the public cloud server stores an archive user table, and the archive user table is used to characterize a mapping relationship between privately-owned alias labels and access addresses of the privately-owned servers, and referring to a structural schematic diagram of the processing device for archive data shown in fig. 4, the device mainly includes the following parts:
the public cloud server 402 is configured to receive an archive processing request sent by a terminal;
The public cloud server 402 is further configured to determine, if the archive processing request carries the first privately-owned alias tag, a target access address corresponding to the first privately-owned alias tag based on the archive user table, and establish a communication connection between the terminal and the target privately-owned server based on the target access address;
the target privateization server 404 is configured to respond to the file processing request to obtain a file processing result.
According to the file data processing device provided by the embodiment of the invention, user synchronization is realized through the file user table stored in the public cloud server, the public cloud server receives the file processing request sent by the terminal, and communication connection between the terminal and the target privately-arranged server is established according to the target access address corresponding to the first privately-arranged alias label, which is equivalent to forwarding the file processing request to the target privately-arranged server.
In one embodiment, the privatized server side 404 is deployed with a first message unit and a data capturing unit, and the public cloud server side 402 is deployed with a second message unit, the method further comprising:
the data capturing unit is used for determining changed target user data when the user data stored in the archive user table is monitored to be changed, and sending the target user data to the user pushing Topic in the first message unit;
the first message unit is used for pushing target user data stored in the Topic for a user, marking a data change type label and a second privately-owned alias label, and sending the target user data, the data change type label and the second privately-owned alias label to the second message unit of the public cloud server in an associated manner;
the second message unit is used for updating the archive user table based on the target user data, the data change type label and the second privately-owned alias label.
In one embodiment, the first message unit is further configured to:
newly adding a type field and an alias field in the target user data;
and assigning the preset privately-assigned alias to the alias field to obtain a second privately-assigned alias tag.
In one embodiment, the public cloud server 402 is communicatively connected to a public cloud database for storing user data, and the second message unit is further configured to:
if the data change type label is a new type, storing target user data into a public cloud database, determining an access address corresponding to the second privately-arranged alias label, and storing the second privately-arranged alias label and the access address corresponding to the second privately-arranged alias label in an associated mode into a file user table;
If the data change type is a modification type and the file user table stores a second privately-arranged alias tag, updating the target user data to a public cloud database;
and if the data change type is the deletion type, removing the second privately-arranged alias tag from the file user table.
In one embodiment, the file processing request includes a first query request, the file processing result includes a first file query result, the privately-owned server is communicatively connected to a privately-owned database, the privately-owned database is used for storing private file data, and the target privately-owned server is further 404 configured to:
Searching in the privateization database based on the first query request to obtain private archive data corresponding to the first query request;
And taking the private archive data corresponding to the first query request as a first archive query result.
In one embodiment, the file processing request includes a second query request, the file processing result includes a second file query result, and the public cloud server is communicatively connected to a public cloud database, where the public cloud database is further configured to store public file data, and the public cloud server 402 is further configured to:
if the second query request does not carry the first privately-arranged alias tag, searching in a public cloud database based on the second query request to obtain public file data corresponding to the second query request;
and taking the public file data corresponding to the second query request as a second file query result.
In one embodiment, the public cloud server 402 or the target privately owned server 404 is further configured to feed back the archive processing result to the terminal, so as to display the archive processing result through a graphical user interface of the terminal.
The device provided by the embodiment of the present invention has the same implementation principle and technical effects as those of the foregoing method embodiment, and for the sake of brevity, reference may be made to the corresponding content in the foregoing method embodiment where the device embodiment is not mentioned.
The embodiment of the invention provides a server, in particular to the server, which comprises a processor and a storage device, wherein the storage device is stored with a computer program which, when being executed by the processor, executes the method according to any one of the embodiments.
Fig. 5 is a schematic structural diagram of a server according to an embodiment of the present invention, where the server 100 includes a processor 50, a memory 51, a bus 52 and a communication interface 53, where the processor 50, the communication interface 53 and the memory 51 are connected through the bus 52, and the processor 50 is configured to execute executable modules, such as computer programs, stored in the memory 51.
The memory 51 may include a high-speed random access memory (RAM, random Access Memory), and may further include a non-volatile memory (non-volatile memory), such as at least one disk memory. The communication connection between the system network element and at least one other network element is achieved via at least one communication interface 53 (which may be wired or wireless), and the internet, wide area network, local network, metropolitan area network, etc. may be used.
Bus 52 may be an ISA bus, a PCI bus, an EISA bus, or the like. The buses may be classified as address buses, data buses, control buses, etc. For ease of illustration, only one bi-directional arrow is shown in FIG. 5, but not only one bus or type of bus.
The memory 51 is configured to store a program, and the processor 50 executes the program after receiving an execution instruction, and the method executed by the apparatus for flow defining disclosed in any of the foregoing embodiments of the present invention may be applied to the processor 50 or implemented by the processor 50.
The processor 50 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuitry in hardware in the processor 50 or by instructions in the form of software. The processor 50 may be a general-purpose processor including a central Processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), a digital signal processor (DIGITAL SIGNAL Processing, DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable GATE ARRAY (FPGA), a Programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The disclosed methods, steps, and logic blocks in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory 51 and the processor 50 reads the information in the memory 51 and in combination with its hardware performs the steps of the above method.
The computer program product of the readable storage medium provided by the embodiment of the present invention includes a computer readable storage medium storing a program code, where the program code includes instructions for executing the method described in the foregoing method embodiment, and the specific implementation may refer to the foregoing method embodiment and will not be described herein.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. The storage medium includes a U disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, an optical disk, or other various media capable of storing program codes.
It should be noted that the foregoing embodiments are merely illustrative embodiments of the present invention, and not restrictive, and the scope of the invention is not limited to the embodiments, and although the present invention has been described in detail with reference to the foregoing embodiments, it should be understood by those skilled in the art that any modification, variation or substitution of some of the technical features of the embodiments described in the foregoing embodiments may be easily contemplated within the scope of the present invention, and the spirit and scope of the technical solutions of the embodiments do not depart from the spirit and scope of the embodiments of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.