Data processing device, program product, and computer-readable storage medium

Abstract

The invention provides a data processing device, a program product, and a computer-readable storage medium, which can perform display effective for improving promotion effect on an information terminal. A data processing device includes an acquisition unit, a storage unit, and an attachment control unit. The acquisition unit acquires storage destination information indicating a storage destination in the first storage device, the storage destination information being used for storing data generated by the micro-service when the micro-service is installed. The storage unit stores the storage destination information acquired by the acquisition unit. The installation control unit installs the micro-service for which the storage destination information has been acquired.

Description

Technical Field

[0001] The embodiments of the present invention relate to a data processing device, a program product for causing a computer to function as the data processing device, and a computer-readable storage medium having the program recorded thereon. Background Art

[0002] In recent years, container technology has become known as a virtualization technology.

[0003] The so-called container is composed as follows: a virtual area is set up on the OS (Operating System) to execute and run the application and its execution environment. In addition, micro services are provided as a collection of applications in the container. Other applications running on the OS that are different from the micro services cannot directly access the micro services of the applications in the container.

[0004] The application in the container of the microservice stores data in the virtual volume, that is, on the storage, so when the container in the microservice is deleted, the stored data is also deleted. Therefore, container management tools such as Docker (trademark) provide a data persistence function that saves the data stored in the virtual volume in the container to a storage device on the hardware or an external storage device. At this time, the designated destination for data persistence is set when the container management tool deploys (installs) the application in the container, and becomes information managed only by the setting at the time of deployment.

[0005] In addition, it is also known that a microservice is run on an edge device that is an on-premises data processing device to provide various services. When a microservice is run on an on-premises edge device, the designated destination for data persistence is designated as a storage device in the edge device. In this way, if the storage device in the edge device is used as the designated destination for data persistence, the data in the designated destination for persistence may disappear due to a failure of the storage device of the edge device, etc. Therefore, a backup of the data stored in the designated destination for persistence is required.

[0006] The designated destination for data persistence is specified when the microservice (container) is deployed. Therefore, the control application that controls the edge device cannot grasp the designated destination for persistence. Therefore, it is difficult for the control application to accurately back up the data generated by the microservice and stored in the designated destination for persistence. In addition, even if all the data of the storage device containing the data of the designated destination for persistence is backed up to other storage devices, the control application does not know the designated destination for data persistence of the container, so it cannot perform data recovery for the microservice from the backed-up data.

[0007] [Prior art literature]

[0008] [Patent Literature]

[0009] [Patent Document 1] Japanese Patent Application Publication No. 2022-91301 Summary of the invention

[0010] An object of the present invention is to provide a data processing device and a program product thereof that can grasp the persistence destination of data generated by a microservice. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 It is an overall structural diagram of a data processing system in one embodiment of the present invention.

[0012] Figure 2 This is a block diagram showing a main circuit configuration of an edge device as one embodiment of a data processing apparatus.

[0013] Figure 3 is a schematic diagram showing the main data structure of a microservice information table stored in a main memory in an edge device.

[0014] Figure 4 is a schematic diagram showing the main software structure in the edge device.

[0015] Figure 5 It is a flowchart showing the main information processing steps of the control module of the edge device.

[0016] Figure 6 is a flowchart showing the steps of the microservice deployment process.

[0017] Figure 7 This is a schematic diagram showing an example of the relationship between each software structure and each storage device in the edge device during the microservice deployment process.

[0018] Figure 8 This is a schematic diagram showing an example of the content of a microservice package input to an edge device.

[0019] Fig. 9 is a flowchart showing the steps of the backup process.

[0020] Fig.10 This is a schematic diagram showing an example of the relationship between each software configuration and each storage device in the edge device during the backup process.

[0021] Fig.11 is a flowchart showing the steps of the recovery process.

[0022] Fig.12 This is a schematic diagram showing an example of the relationship between each software configuration and each storage device in the edge device during the recovery process. DETAILED DESCRIPTION

[0023] In one embodiment, a data processing device includes an acquisition unit, a storage unit, and an installation control unit. The acquisition unit acquires storage destination information indicating a storage destination in a first storage device used to store data generated by the microservice when installing the microservice. The storage unit stores the storage destination information acquired by the acquisition unit. The installation control unit installs the microservice that has acquired the storage destination information.

[0024] Hereinafter, embodiments of the data processing device will be described with reference to the drawings.

[0025] Figure 1 This is an overall structural diagram of a data processing system in one embodiment of the present invention. A data processing device in one embodiment of the present invention is provided as an edge device 1 pre-installed by an enterprise at a base B or the like. The edge device 1 is connected to a plurality of IoT (Internet of Things) devices 2 and a data storage device 3 via a LAN (Local Area Network) 4 in the base B. In addition, the edge device 1 is configured to be able to communicate with the cloud 5, and to be able to download programs and data from a cloud server 51 and a cloud storage device 52 on the cloud 5, or to upload data to the cloud server 51 and the cloud storage device 52. It should be noted that in Figure 1 In the figure, the edge device 1 is connected to the cloud 5 via the LAN 4, but it can of course also be configured to be directly connected to the cloud 5.

[0026] For example, if the location B is a factory, the IoT device 2 may be a sensor that detects mechanical movements in the factory, and the data storage device 3 may store data obtained by the IoT device 2. In this case, the edge device 1 may analyze or process the data obtained by the IoT device 2, and upload it to the cloud server 51 and cloud storage device 52 used by the head office, data sales service company, etc. In addition, if the location B is a store such as a supermarket, the IoT device 2 may be a POS (Point of Sales) terminal in the store, and the data storage device 3 may store a product master file that records the product code, unit price, etc. In this case, the edge device 1 may calculate the sales amount through the product code obtained by the IoT device 2 and the product master file stored in the data storage device 3, or analyze or process the sales amount, and upload it to the cloud server 51 and cloud storage device 52 used by the head office, etc.

[0027] Figure 21 is a block diagram showing the circuit structure of the main part of the edge device 1. The edge device 1 is configured by connecting a main memory 12, an auxiliary storage device 13, an input unit 14, an output unit 15, and a communication unit 16 to a processor 11. The edge device 1 is composed of the processor 11, the main memory 12, and the auxiliary storage device 13 to form a computer.

[0028] The processor 11 is equivalent to the central part of the above-mentioned computer. The processor 11 controls each part according to the OS and application programs in order to realize various functions as the edge device 1. The processor 11 is, for example, a CPU (Central Processing Unit). The processor 11 can be a processing circuit such as a GPU (Graphics Processing Unit), an application-specific integrated circuit (Application Specific Integrated Circuit: ASIC)), a programmable logic device (for example, a simple programmable logic device (Simple Programmable Logic Device: SPLD), a complex programmable logic device (Complex Programmable Logic Device: CPLD), and a field programmable gate array (Field Programmable Gate Array: FPGA)). The processor 11 is not limited to being configured as a single processing circuit, and a plurality of processing circuits can be combined to form the processor 11.

[0029] The main memory 12 is equivalent to the main storage part of the above-mentioned computer. The main memory 12 includes a non-volatile storage area and a volatile storage area. The main memory 12 stores the OS, applications, containerized applications, i.e., microservices, etc. in the non-volatile storage area. The main memory 12 sometimes also stores the data required for the processor 11 to perform processing for controlling each part in the non-volatile or volatile storage area. The main memory 12 uses a part of the non-volatile storage area as the production area of ​​the microservice information table 121. The microservice information table 121 stores information related to the microservices deployed (installed) in the main memory 12, and the details are described later. In addition, the main memory 12 uses the volatile storage area as a working area for the processor to rewrite data appropriately. For example, the non-volatile storage area is ROM (Read Only Memory). The volatile storage area is RAM (Random Access Memory).

[0030] The auxiliary storage device 13 is equivalent to the auxiliary storage part of the above-mentioned computer. For example, EEPROM (registered trademark) (Electric Erasable Programmable Read-Only Memory), HDD (Hard Disk Drive) or SSD (Solid State Drive) is used as the auxiliary storage device 13. The auxiliary storage device 13 stores the data used by the processor 11 when performing various processes and the data generated by the processing of the processor 11. The auxiliary storage device 13 sometimes also stores the above-mentioned application. The auxiliary storage device 13 includes a persistent destination storage device 131, a backup storage device 132, etc. The persistent destination storage device 131 is a first storage device that stores the data generated by the microservice in order to make the data persistent. The backup storage device 132 is a second storage device that copies and stores the data stored in the persistent destination storage device 131 in order to back up the data. The persistent destination storage device 131 and the backup storage device 132 are configured as physically different storage devices from each other, such as different physical drives. Alternatively, one side can be configured in the SSD and the other side can be configured in the HDD.

[0031] The input unit 14 is a user interface such as a keyboard, a touch panel, a mouse, or other pointing device. In addition, the input unit 14 may also include a reading device for reading microservice packets from a computer-readable storage medium such as a disk medium or a memory medium that records microservice packets used in the deployment of microservices described later. In addition, the output unit 15 is a user interface such as a display, an output device such as a printer, etc. It should be noted that the edge device 1 may not have at least one of these input unit 14 and output unit 15.

[0032] The communication unit 16 transmits and / or receives data with each unit connected via the LAN 4. In addition, the communication unit 16 communicates with the cloud 5 to download applications, microservice packages, data, etc. from the cloud server 51 or the cloud storage device 52, or upload data.

[0033] Figure 3 1 is a schematic diagram showing the main data structure of the microservice information table 121 stored in the main memory 12. The microservice information table 121 stores a microservice ID, persistent destination information, and backup destination information for each microservice deployed in the edge device 1. The microservice ID is unique identification information for identifying a microservice. The persistent destination information is a persistent designated destination path of the persistent destination storage device 131 used to store data generated by the microservice. The backup destination information is a storage destination path of the backup storage device 132 used to back up data.

[0034] Figure 4is a schematic diagram showing the main software structure in the edge device 1. In this embodiment, each application is containerized by using container technology, and hardware resources are managed by a container management tool. Figure 4 The software structure shown is implemented by the processor 11 executing a program stored in the main memory 12 of the edge device 1 .

[0035] like Figure 4 As shown, OS 171 is installed in edge device 1. In addition, container management tool 172 running on OS 171 is installed in edge device 1. Container management tool 172 includes container engines such as Dcker that build container environments and execute applications in container environments, and orchestration tools such as Kubernetes (trademark) and k3s that manage hardware resources of container environments.

[0036] The container engine forms a logical container area by virtualizing hardware resources, etc. In addition, the application is integrally constituted with the middleware used in the operation in the container environment and a part of the OS (library, setting, file system, etc.). As a result, the containerized application runs in the container area. It should be noted that the OS constituted in the container may be of a different type from the type of OS 171 of the edge device. Such a situation in which an application, middleware, and a part of the OS are integrally constituted is called containerization, and sometimes the containerized application is simply referred to as a container. In this way, a container environment is constructed by importing a container engine and the application is containerized, so that the container can be executed in the container environment.

[0037] The orchestration tool manages the hardware resources virtualized by the container engine. Specifically, the orchestration tool builds a logical area called a cluster as an environment for executing containerized applications. One or more nodes are set up in the cluster as the execution environment of the application. In the node, one or more containers are managed in units called Pods. A Pod is composed of one or more containers 174. When using containers to develop applications, a method called microservices is generally used in which the application is subdivided and installed according to each function. Using an orchestration tool, microservices are distributed in each Pod.

[0038] Therefore, in such an environment where the container management tool 172 is introduced, Figure 4 As shown, the microservice 173 is managed as a collection of one or more containers 174. The containerized application is managed in units of Pods. Whenever the microservice 173 completes a predetermined process, the container management tool 172 enables the microservice 173 to store a data file recording the generated processed data in the persistent destination storage device 131.

[0039] It should be noted that the orchestration tool can not only use the hardware resources of one edge device 1 to form a cluster, but also use the hardware resources of more than two different devices to form more than one cluster.

[0040] In addition, in this embodiment, the edge device 1 has a control module 175 as an application running on the OS 171. The control module 175 controls the deployment of the microservice 173 and the backup and recovery of the persisted data.

[0041] The following describes the operation of the edge device 1 with the operation of the control module 175 as the center.

[0042] Figure 5 1 is a flowchart showing the main information processing procedure of the control module 175. The processor 11 of the edge device 1 functions as the control module 175 by executing the data processing program installed in the main memory 12.

[0043] First, as Act 1, the control module 175 determines whether to deploy, i.e., install the microservice. The control module 175 can make the determination based on, for example, the presence or absence of a deployment instruction (deployment command) input by the operator of the edge device 1 from the input unit 14. Alternatively, the control module 175 can make the determination based on whether a deployment instruction is received from the cloud server 51 on the cloud 5 or a control terminal (not shown) through the communication unit 16.

[0044] When it is determined that the microservice is to be deployed, the control module 175 executes the microservice deployment process as Act 2. The microservice deployment process is a process of obtaining a designated destination for data persistence of the microservice 173 and causing the container management tool 172 to deploy the microservice 173. Figures 6 to 8 The microservice deployment process is described in detail. Figure 6 is a flowchart showing the steps of the microservice deployment process. Figure 7 1 is a schematic diagram showing an example of the relationship between each software structure and each storage device in the edge device 1 in the microservice deployment process. Figure 8 It is a schematic diagram showing an example of the content of the microservice package 18.

[0045] (1) In the microservice deployment process, as Act 21, the control module 175 first extracts the data persistence destination of the microservice. Specifically, the control module 175 extracts the path of the persistence destination storage device 131, which is the designated destination for persisting the data of the microservice, from the microservice package 18 of the microservice to be deployed. The microservice package 18 can be input from the input unit 14 together with the deployment instruction. Alternatively, the control module 175 can also download the microservice package 18 from the cloud server 51 or the cloud storage device 52 through the communication unit 16 based on the address on the cloud 5 indicated by the deployment instruction.

[0046] like Figure 8 As shown, in addition to the container image object 181 that is the basis for each container 174 in the microservice 173, the microservice package 18 also includes a setting file 182. The setting file 182 is a text file that records the definitions of the containers, networks, volumes, restart policies, etc. used by the microservice in YAML format. The setting file 182 also records the definition of the specified destination path for data persistence. Figure 8 In the example, the folder [ / tmp / storage] in the persistent destination storage device 131 is defined as the designated destination path (Store Path). When deploying a microservice from the microservice package 18, the container management tool 172 extracts the designated destination path from the setting file 182 and manages it as a persistent destination.

[0047] In this embodiment, the control module 175 extracts the designated destination path for data persistence from the setting file 182 of the microservice package 18 in Act 21 before the container management tool 172. In this way, the control module 175 functions as an acquisition unit.

[0048] (2) Then, as Act 22, the control module 175 saves the specified destination path of the extracted data persistence. Specifically, the control module 175 stores the specified destination path of the extracted data persistence as persistent destination information in the microservice information table 121 in association with the unique microservice ID for identifying the microservice. As described above, the microservice information table 121 functions as a storage unit.

[0049] (3) Then, as Act 23 , the control module 175 calls the container management tool 172 . That is, the control module 175 passes the input microservice package 18 to the container management tool 172 .

[0050] (4) It should be noted that the container management tool 172 that receives the microservice package 18 through the microservice deployment process deploys (installs) the microservice 173 from the microservice package 18. Therefore, the control module 175 functions as an installation control unit.

[0051] Then, the control module 175 ends the microservice deployment process. If the microservice deployment process ends, the control module 175 returns to the above-mentioned Act 1.

[0052] (5) When persisting data generated by the microservice 173 , the container management tool 172 writes the data to the [ / tmp / storage] folder of the persistence destination storage device 131 .

[0053] return Figure 5 Description.

[0054] When it is determined in the above-mentioned Act 1 that the microservice is not deployed, as Act 3, the control module 175 determines whether to back up the persisted data. The control module 175 can make a judgment based on, for example, the presence or absence of a backup instruction (backup command) input by the operator of the edge device 1 from the input unit 14. Alternatively, the control module 175 can make a judgment based on whether a backup instruction is received from the cloud server 51 on the cloud 5 or a control terminal not shown in the figure through the communication unit 16. In addition, the control module 175 can make a judgment based on whether the backup execution time determined daily has arrived. In this way, the backup can be implemented irregularly or regularly.

[0055] When it is determined that the persistent data is to be backed up, the control module 175 performs a backup process as Act 4. The backup process is a process of backing up the data stored in the designated destination path of the persistent destination storage device 131, which is the persistent destination of the data of the microservice 173, to the backup storage device 132. Fig. 9 and Fig.10 The backup process is described in detail. Fig. 9 is a flowchart showing the steps of the backup process. Fig.10 1 is a schematic diagram showing an example of the relationship between each software configuration and each storage device in the edge device 1 during the backup process.

[0056] (1) In the backup process, as Act 41, the control module 175 first reads the designated destination path for data persistence of the backup target microservice 173. Specifically, the control module 175 reads the designated destination path for data persistence stored as persistence destination information in the microservice information table 121 in association with the microservice ID corresponding to the target microservice.

[0057] (2) In addition, as Act 42, the control module 175 determines the backup destination. Specifically, the control module 175 determines the backup destination folder used in the backup storage device 132 as the designated destination path for the backup. The designated destination path for the backup may correspond to the read designated destination path, may be generated based on the microservice ID, or may be an arbitrary path that is not dependent on them. Then, as Act 43, the control module 175 saves the determined backup destination. Specifically, the control module 175 associates the designated destination path for the backup determined in Act 42 with the microservice ID corresponding to the microservice of the same object in the microservice information table 121 and stores it as the backup destination information.

[0058] (3) Then, as Act 44, the control module 175 copies the persisted data to the backup destination. Specifically, the control module 175 copies the data written in the designated path of the persistent destination of the data in the persistent destination storage device 131 to the designated path of the backup in the backup storage device 132. It should be noted that the persistent destination storage device 131 at the time of backup is also referred to as the persistent destination storage device 131-1 before replacement hereinafter. In this way, the control module 175 functions as a backup unit.

[0059] Then, the control module 175 ends the backup process. When the backup process ends, the control module 175 returns to the above-mentioned Act 1.

[0060] return Figure 5 Description.

[0061] When it is determined in the above-mentioned Act 3 that the persisted data is not backed up, as Act 5, the control module 175 determines whether to restore the backup data. For example, the control module 175 can make a judgment based on whether the recovery instruction (recovery command) input by the operator of the edge device 1 from the input unit 14 is incorrect. The recovery instruction is input by the operator, for example, when the hardware of the persistent destination storage device 131 is replaced with new hardware due to a failure of the persistent destination storage device 131. Alternatively, the control module 175 can make a judgment based on whether a recovery instruction is received from the cloud server 51 on the cloud 5 or a control terminal not shown in the figure through the communication unit 16.

[0062] When it is determined that the backup data is to be restored, the control module 175 executes the restoration process as Act 6. The restoration process is a process of restoring the data backed up in the backup storage device 132 to the designated destination of the data persistence of the microservice 173 in the persistence destination storage device 131. Fig.11 and Fig.12 The backup process is described in detail. Fig.11: is a flowchart showing the steps of the recovery process of Act 6. Fig.12 1 is a schematic diagram showing an example of the relationship between each software configuration and each storage device in the edge device 1 during the restoration process.

[0063] In the restoration process, as Act 61 , the control module 175 first reads a designated destination path for data persistence of a restoration target microservice 173. Specifically, the control module 175 reads a designated destination path for data persistence stored as persistence destination information in association with a microservice ID from the microservice information table 121 .

[0064] (2) Furthermore, as Act 62, the control module 175 reads the backup destination of the data of the microservice 173 to be restored. Specifically, the control module 175 reads the designated destination path in the backup storage device 132, which stores the designated destination path for persisting data in association with the read microservice ID, as the backup destination information, from the microservice information table 121.

[0065] (3) Then, as Act 63, the control module 175 copies the backup data to the persistent destination. Specifically, the control module 175 copies the backed-up data in the designated destination path of the backup to the path of the persistent destination storage device 131 indicated by the designated destination path of the data persistence. The persistent destination storage device 131 of the copy destination in this case is the new hardware after the replacement, not the persistent destination storage device 131-1 before the replacement. Hereinafter, the replaced persistent destination storage device 131 is also referred to as the replaced persistent destination storage device 131-2. In this way, the control module 175 functions as a recovery unit.

[0066] Then, as Act 64, the control module 175 determines whether there is any unrecovered data. Specifically, the control module 175 determines whether there is any microservice ID that has not been used as a recovery object among the microservice IDs stored in the microservice information table 121. If it is determined that there is any unrecovered data, the control module 175 returns to the above Act 61.

[0067] (4) When it is determined in Act 64 that there is no unrestored data, the control module 175 notifies the container management tool 172 of the completion of restoration as Act 65.

[0068] Then, the control module 175 ends the restoration process. When the restoration process ends, the control module 175 returns to the above-mentioned Act 1.

[0069] (5) In addition, the container management tool 172 that receives the recovery notification through the recovery process starts the microservice 173. Then, when the container management tool 172 needs the data generated by the microservice 173 in the past, it can read the data from the replaced persistent destination storage device 131-2. In addition, when making the data generated by the microservice 173 persistent, it can write the data to the replaced persistent destination storage device 131-2.

[0070] As described above, according to this embodiment, the control module 175 implemented by the control application program for controlling the data processing device obtains the designated destination path when deploying (installing) the microservice, stores it in the microservice information table 121, and causes the container management tool 172 to deploy the microservice, wherein the designated destination path is storage destination information indicating the storage destination in the persistent destination storage device 131 used to store the data generated by the microservice. Therefore, the control module 175 can grasp the persistent destination of the data generated by the microservice.

[0071] Furthermore, according to this embodiment, the control module 175 backs up the data generated by the microservice 173 stored in the persistence destination storage device 131 to the backup storage device 132, which is hardware physically different from the persistence destination storage device 131, according to the designated destination path of data persistence of the microservice 173 stored in the microservice information table 121, and stores the designated destination path of the backup of the backup storage device 132 in the microservice information table 121. Therefore, the data generated by the microservice 173 can be backed up.

[0072] Then, when the persistent destination storage device 131 storing the data backed up to the backup storage device 132, i.e., the persistent destination storage device 131-1 before replacement, fails and is replaced by a new persistent destination storage device 131, i.e., the persistent destination storage device 131-2 after replacement, according to this embodiment, the control module 175 restores the data backed up in the backup storage device 132 to the persistent destination storage device 131-2 after replacement based on the designated destination path of the backup of the backup storage device 132 stored in the microservice information table 121 and the designated destination path of the data persistence in the persistent destination storage device 131-1 before replacement. Therefore, the backed-up data generated by the microservice 173 can be restored to the persistent destination storage device 131-2 after replacement and continued to be used by the microservice 173.

[0073] It should be noted that according to this embodiment, the control module 175 extracts the designated destination path for persisting the data of the microservice from the microservice package 18 which is the file of the installation source of the microservice. Therefore, the control module 175 can easily obtain the designated destination path.

[0074] In addition, the data processing device of the present embodiment is an edge device 1 having a persistent destination storage device 131 and communicating with the cloud 5. Therefore, even if the storage device in the edge device 1 is designated as the persistent destination of the data of the microservice, the control module 175 can grasp the persistent destination of the data generated by the microservice and can perform backup and recovery of the data. Therefore, in a system accompanied by a container 174 running on the edge device 1 pre-installed by the enterprise, through the backup processing of the edge device 1, even if the persistent destination storage device 131 as the storage device of the persistent designated destination is damaged, data can be restored.

[0075] An embodiment has been described above, but the present invention is not limited thereto.

[0076] For example, the backup destination of the persisted data may not be the backup storage device 132 in the edge device 1, but an external storage device. For example, the backup destination may be a data storage device 3 pre-installed by the same enterprise as the edge device 1, or a cloud storage device 52 on the cloud 5 with which the edge device 1 communicates.

[0077] In addition, the steps and contents of the flowchart shown in the embodiment are examples. As long as the same result can be obtained, the steps and contents can be appropriately changed. For example, the order of Act 41, Act 42, and Act 43 can be reversed, or they can be performed in parallel. In this way, as long as there is no conflict with the preceding or subsequent processing, the order of processing can be changed, or multiple processing can be performed in parallel.

[0078] The above data processing device is as follows.

[0079] (1) A data processing device comprising: an acquisition unit that, when installing a microservice, acquires storage destination information indicating a storage destination in a first storage device for use in storing data generated by the microservice; a storage unit that stores the storage destination information acquired by the acquisition unit; and an installation control unit that installs the microservice that has acquired the storage destination information.

[0080] (2) The data processing device according to (1) further comprises a backup unit, which backs up the data generated by the microservice stored in the first storage device to a second storage device physically different from the first storage device based on the storage destination information stored in the storage unit.

[0081] (3) The data processing device according to (2), further comprising a restoration unit configured to restore the data stored in the second storage device to the first storage device based on the storage destination information stored in the storage unit.

[0082] (4) The data processing device according to any one of (1) to (3), wherein the acquisition unit extracts the storage destination information from a file of an installation source of the microservice.

[0083] (5) The data processing device according to any one of (1) to (4), wherein the data processing device is an edge device that further includes the first storage device and communicates with a cloud.

[0084] (6) A program product for enabling a computer running a microservice to implement the following functions when installing the microservice: a function of obtaining storage destination information indicating a storage destination in a first storage device used to store data generated by the microservice; a function of storing the obtained storage destination information in a memory; and a function of installing the microservice.

[0085] (7) A computer-readable storage medium storing a program for causing a computer running a microservice to implement the following functions when installing the microservice: a function of obtaining storage destination information indicating a storage destination in a first storage device used to store data generated by the microservice; a function of storing the obtained storage destination information in a memory; and a function of installing the microservice.

[0086] (8) A data processing device comprising a memory in which a microservice is to be installed, a processor for running the microservice installed in the memory, and a first storage device for storing data generated by the microservice, wherein when the processor installs the microservice in the memory, the processor executes: obtaining storage destination information indicating a storage destination in the first storage device; storing the obtained storage destination information in the memory; and installing the microservice in the memory.

[0087] The program of this embodiment can be transferred while being stored in an electronic device, or can be transferred while not being stored in an electronic device. In the latter case, the program can be transferred via a network, or can be transferred while being stored in a storage medium. A storage medium is a non-temporary tangible medium. A storage medium is a computer-readable medium. The storage medium can be any medium such as a CD-ROM, a memory card, etc. that can store a program and can be read by a computer, and its form is not limited.

[0088] It should be noted that the embodiments are only examples and are not intended to limit the scope of the invention. The above new embodiments can be implemented in various other ways, and various omissions, substitutions, changes, and combinations can be made without departing from the gist of the invention. The above embodiments and their variations are included in the scope and gist of the invention, and are also included in the schemes recorded in the claims and their equivalents.

Claims

1. A data processing device comprising: an acquisition unit that, when installing a microservice, acquires storage destination information indicating a storage destination in a first storage device used to store data generated by the microservice; a storage unit that stores the storage destination information acquired by the acquisition unit; as well as An installation control unit installs the microservice having acquired the storage destination information.

2. The data processing device according to claim 1, wherein: The device further includes a backup unit configured to back up the data generated by the microservice and stored in the first storage device in a second storage device that is physically different from the first storage device based on the storage destination information stored in the storage unit.

3. The data processing device according to claim 2, wherein: The device further includes a restoration unit configured to restore the data stored in the second storage device to the first storage device based on the storage destination information stored in the storage unit.

4. The data processing device according to claim 1, wherein: The acquisition unit extracts the storage destination information from a file of an installation source of the microservice.

5. The data processing device according to any one of claims 1 to 4, wherein: The data processing device is an edge device that also includes the first storage device and communicates with the cloud.

6. A program product for enabling a computer running a microservice to implement the following functions when the microservice is installed: A function of obtaining storage destination information indicating a storage destination in a first storage device used to store data generated by the microservice; a function of storing the acquired storage destination information in a memory; and Install the functionality of the microservice.

7. A computer-readable storage medium storing a program for enabling a computer running a microservice to implement the following functions when installing the microservice: A function of obtaining storage destination information indicating a storage destination in a first storage device used to store data generated by the microservice; a function of storing the acquired storage destination information in a memory; and Install the functionality of the microservice.

Images