Data processing apparatus, program, and computer-readable storage medium

MYPI2025000800A0Undetermined Publication Date: 2024-06-23TOSHIBA TEC KK
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
MYPI2025000800
Authority / Receiving Office
MY · MY
Patent Type
Applications
Current Assignee / Owner
Priority Date
2022-12-23
Filing Date
2023-05-23
Publication Date
2024-06-23

AI Technical Summary

Technical Problem

In microservice container environments, data persistence destinations are not easily identifiable by control applications, making data backup and recovery challenging, especially when microservices operate on edge devices where storage failures can occur.

Method used

A data processing device with an acquisition unit to obtain storage location information for microservice data, a storage unit to store this information, and an installation control unit to manage microservice deployment and data persistence, allowing the control module to track and manage data persistence destinations within the microservice information table.

Benefits of technology

Enables the control module to correctly identify and manage data persistence destinations, facilitating data backup and recovery even if the original persistence destination storage fails, ensuring data continuity for microservices operating on edge devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure PI2025000800_DRAWING_001
    Figure PI2025000800_DRAWING_001
  • Figure PI2025000800_DRAWING_002
    Figure PI2025000800_DRAWING_002
  • Figure PI2025000800_DRAWING_003
    Figure PI2025000800_DRAWING_003
Patent Text Reader

Abstract

Enabling display effective for further improving a sales promotion effect on an information terminal. A data processing apparatus includes an acquisition unit, a storage unit, and an installation control unit. The acquisition unit acquires, when a microservice is to be installed, storage destination information indicating a storage destination in a first storage device, and the storage destination is used to store data generated by the microservice. The storage unit stores the storage destination information acquired by the acquisition unit. The installation control unit installs the microservice for which the storage destination information has been acquired. Figure 7
Need to check novelty before this filing date? Find Prior Art

Description

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

[0001] An embodiment of the present invention relates to a data processing device, a program for causing a computer to function as the data processing device, and a computer-readable storage medium on which the program is recorded.

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

[0003] A container is a mechanism that creates a virtual area on an operating system (OS) and runs and operates applications and their execution environments within it. Microservices are provided as a collection of applications within this container. Microservices provided by applications within this container cannot be directly accessed from other applications running on the OS other than this microservice.

[0004] Applications in microservice containers store data in virtual volumes, i.e., in memory. Therefore, when a container in a microservice is deleted, the stored data is also deleted. Therefore, container management tools such as Docker (trademark) provide a data persistence function that saves data stored in virtual volumes in a container to hardware storage or external storage. In this case, the data persistence destination is set when the container management tool deploys (installs) the application in the container, and the information is managed only by the settings at the time of deployment.

[0005] Another known operational mode is to run microservices on edge devices, which are on-premise data processing devices, to provide various services. When running microservices on an on-premise edge device, the designated destination for data persistence is storage within the edge device. In this way, if the designated destination for data persistence is storage within the edge device, there is a possibility that data in the designated destination for persistence will be lost due to a storage failure in the edge device, etc. Therefore, it is necessary to back up the data stored in the designated destination for persistence.

[0006] The data persistence destination is specified when the microservice (container) is deployed. Therefore, the control application that controls the edge device cannot grasp the specified persistence destination. This makes it difficult for the control application to correctly back up the data generated by the microservice and saved in the specified persistence destination. Furthermore, even if all data in the storage, including the data in the specified persistence destination, is backed up to another storage, the control application cannot recover data for the microservice from the backed up data because it does not know the specified data persistence destination of the container.

[0007] Japanese Patent Application Publication No. 2022-91301

[0008] The problem to be solved by the embodiments of the present invention is to provide a data processing device and a program therefor that are capable of determining the persistence destination of data generated by a microservice.

[0009] FIG. 1 is a diagram illustrating the overall configuration of a data processing system according to an embodiment of the present invention. FIG. 2 is a block diagram illustrating the main circuit configuration of an edge device as an embodiment of a data processing device. FIG. 3 is a schematic diagram illustrating the main data structure of a microservice information table stored in a main memory in the edge device. FIG. 4 is a schematic diagram illustrating the main software configuration in the edge device. FIG. 5 is a flowchart illustrating the main information processing procedure of a control module in the edge device. FIG. 6 is a flowchart illustrating the procedure of a microservice deployment process. FIG. 7 is a schematic diagram illustrating an example of the relationship between each software configuration and each storage in the edge device during the microservice deployment process. FIG. 8 is a schematic diagram illustrating an example of the contents of a microservice package input to the edge device. FIG. 9 is a flowchart illustrating the procedure of a backup process. FIG. 10 is a schematic diagram illustrating an example of the relationship between each software configuration and each storage in the edge device during the backup process. FIG. 11 is a flowchart illustrating the procedure of a recovery process. FIG. 12 is a schematic diagram illustrating an example of the relationship between each software configuration and each storage in the edge device during the recovery process. Embodiment

[0010] 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 to be used to store data generated by the microservice when installing the microservice. The storage unit saves the storage destination information acquired by the acquisition unit. The installation control unit installs the microservice for which the storage destination information has been acquired.

[0011] Hereinafter, an embodiment of a data processing device will be described with reference to the drawings.

[0012] FIG. 1 is a diagram illustrating the overall configuration of a data processing system according to an embodiment of the present invention. The data processing device according to an embodiment of the present invention is provided as an on-premise edge device 1 at a site B or the like. The edge device 1 is connected to a plurality of Internet of Things (IoT) devices 2 and data storage 3 via a local area network (LAN) 4 within the site B. The edge device 1 is also configured to be able to communicate with a cloud 5, and can download programs and data from a cloud server 51 or cloud storage 52 on the cloud 5, and upload data to the cloud server 51 or cloud storage 52. Note that while FIG. 1 illustrates the edge device 1 as being connected to the cloud 5 via a LAN 4, it is of course also possible to configure the edge device 1 to be directly connected to the cloud 5.

[0013] For example, if base B is a factory, IoT device 2 can be a sensor that detects the operation of machines in the factory, and data storage 3 can accumulate data acquired by IoT device 2. In this case, edge device 1 can analyze and process the data acquired by IoT device 2 and upload it to cloud server 51 or cloud storage 52 operated by a headquarters or a data sales service company. Also, if base B is a store such as a supermarket, IoT device 2 can be a point-of-sale (POS) terminal in the store, and data storage 3 can store product master data that lists product codes, unit prices, etc. In this case, edge device 1 can calculate sales using the product codes acquired by IoT device 2 and the product master data stored in data storage 3, analyze and process the sales data, and upload it to cloud server 51 or cloud storage 52 operated by a headquarters or the like.

[0014] 2 is a block diagram showing the main circuit configuration of the edge device 1. The edge device 1 is configured such that a processor 11 is connected to a main memory 12, an auxiliary storage device 13, an input unit 14, an output unit 15, and a communication unit 16. The processor 11, the main memory 12, and the auxiliary storage device 13 constitute a computer in the edge device 1.

[0015] The processor 11 corresponds to the central part of the computer. The processor 11 controls each part to realize various functions of the edge device 1 in accordance with an OS and application programs. The processor 11 is, for example, a CPU (Central Processing Unit). The processor 11 may be a processing circuit such as a GPU (Graphics Processing Unit), an Application Specific Integrated Circuit (ASIC), a programmable logic device (e.g., a Simple Programmable Logic Device (SPLD), a Complex Programmable Logic Device (CPLD), or a Field Programmable Gate Array (FPGA)). The processor 11 is not limited to being configured as a single processing circuit, and may also be configured as a combination of multiple processing circuits.

[0016] The main memory 12 corresponds to the main storage portion of the computer. The main memory 12 includes a nonvolatile memory area and a volatile memory area. The nonvolatile memory area of ​​the main memory 12 stores an OS, application programs, microservices that are containerized application programs, etc. The main memory 12 may store data necessary for the processor 11 to execute processes for controlling each component in either a nonvolatile or volatile memory area. The main memory 12 uses a portion of the nonvolatile memory area as a creation area for a microservice information table 121. This microservice information table 121 stores information about microservices deployed (installed) in the main memory 12, details of which will be described later. The main memory 12 also uses a volatile memory area as a work area where data can be rewritten by the processor as needed. For example, the nonvolatile memory area is ROM (Read Only Memory). The volatile memory area is RAM (Random Access Memory).

[0017] The auxiliary storage device 13 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM (registered trademark), an HDD (Hard Disk Drive), or an SSD (Solid State Drive) is used as the auxiliary storage device 13. The auxiliary storage device 13 stores data used by the processor 11 when performing various processes and data created by the processes in the processor 11. The auxiliary storage device 13 may also store the above-mentioned applications. The auxiliary storage device 13 includes a persistence destination storage 131, a backup storage 132, and the like. The persistence destination storage 131 is a first storage device that stores data generated by a microservice in order to persist the data. The backup storage 132 is a second storage device that copies and stores data stored in the persistence destination storage 131 for backup purposes. The persistence destination storage 131 and the backup storage 132 are configured on physically different storage devices, for example, different physical drives. Alternatively, one can be configured as an SSD and the other as an HDD.

[0018] The input unit 14 is a user interface such as a keyboard, a touch panel, or a pointing device such as a mouse. Furthermore, the input unit 14 may include a reading device that reads a microservice package from a computer-readable storage medium such as a disk medium or a memory medium on which a microservice package used for deploying the microservice, as described below, is recorded. The output unit 15 is a user interface such as a display or an output device such as a printer. The edge device 1 does not necessarily have to have at least one of the input unit 14 and the output unit 15.

[0019] The communication unit 16 transmits and / or receives data to and from each unit connected via the LAN 4. The communication unit 16 also communicates with the cloud 5, downloads application programs, microservice packages, data, etc. from the cloud server 51 or the cloud storage 52, and uploads data.

[0020] 3 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, persistence destination information, and backup destination information for each microservice deployed to the edge device 1. The microservice ID is unique identification information for identifying a microservice. The persistence destination information is a specified persistence destination path in the persistence destination storage 131 used to store data generated by the microservice. The backup destination information is a storage destination path in the backup storage 132 for backing up that data.

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

[0022] 4, an OS 171 is installed in the edge device 1. Furthermore, a container management tool 172 that runs on the OS 171 is installed in the edge device 1. The container management tool 172 includes a container engine, such as Decker, that builds a container environment and executes applications in the container environment, and an orchestration tool, such as Kubernetes (trademark) or k3s, that manages hardware resources in the container environment.

[0023] The container engine forms a logical container area by virtualizing hardware resources, etc. Then, the application is configured integrally with middleware and parts of the OS (libraries, settings, file system, etc.) used to run in the container environment. As a result, the containerized application runs in the container area. Note that the OS configured in this container can be of a different type from the OS 171 of the edge device. This integration of an application with middleware and parts of the OS is called containerization, and a containerized application is sometimes simply referred to as a container. In this way, a container environment is built by introducing a container engine, and containerizing an application makes it possible to run the container in the container environment.

[0024] The orchestration tool manages hardware resources virtualized by the container engine. Specifically, the orchestration tool builds a logical area called a cluster as an environment in which containerized applications are executed. One or more nodes, which are the execution environments for the applications, are provided in the cluster. In the node, one or more containers are managed in units called pods. A pod is made up of one or more containers 174. When developing applications using containers, a technique called microservices is generally used, in which an application is implemented by dividing it into smaller functions. Using the orchestration tool, microservices are distributed and deployed in each pod.

[0025] Therefore, in an environment where the container management tool 172 is introduced in this way, the microservice 173 is managed as a collection of one or more containers 174, as shown in Fig. 4. Containerized applications are managed in units of pods. Each time the microservice 173 completes a specified process, the container management tool 172 causes the microservice 173 to store a data file that records the generated processed data in the persistence destination storage 131.

[0026] The orchestration tool can not only configure a cluster using the hardware resources of one edge device 1 in this way, but also configure one or more clusters using the hardware resources of two or more different devices.

[0027] Furthermore, in this embodiment, the edge device 1 includes a control module 175 as an application that runs on the OS 171. This control module 175 controls the deployment of the microservices 173 and the backup and recovery of persisted data.

[0028] The operation of the edge device 1 will be described below, focusing on the operation of this control module 175.

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

[0030] First, the control module 175 determines whether to deploy, i.e., install, the microservice in Act 1. The control module 175 can determine this based on, for example, whether or not a deploy instruction (deploy command) has been entered from the input unit 14 by the operator of the edge device 1. Alternatively, the control module 175 can determine this based on whether or not a deploy instruction has been received via the communication unit 16 from the cloud server 51 on the cloud 5 or a control terminal (not shown).

[0031] When it is determined that the microservice should be deployed, the control module 175 executes a microservice deployment process in Act 2. This microservice deployment process acquires a designated data persistence destination for the microservice 173 and causes the container management tool 172 to deploy the microservice 173. This microservice deployment process will be described in detail below with reference to FIGS. 6 to 8. FIG. 6 is a flowchart showing the steps of this microservice deployment process. FIG. 7 is a schematic diagram showing an example of the relationship between each software configuration and each storage in the edge device 1 during this microservice deployment process. Finally, FIG. 8 is a schematic diagram showing an example of the contents of the microservice package 18.

[0032] (1) In this microservice deployment process, the control module 175 first extracts the data persistence destination of the microservice in Act 21. Specifically, the control module 175 extracts the path of the persistence destination storage 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 along with a deployment instruction. Alternatively, the control module 175 may download the microservice package 18 from the cloud server 51 or cloud storage 52 via the communication unit 16, based on the address on the cloud 5 indicated in the deployment instruction.

[0033] As shown in FIG. 8 , the microservice package 18 includes a configuration file 182 in addition to a container image object 181 that is the source of each container 174 in the microservice 173. The configuration file 182 is a text file that describes, in YAML format, definitions of the containers, networks, volumes, restart policies, and so on used by the microservice. This configuration file 182 also defines a destination path for data persistence. In the example of FIG. 8 , a folder called " / tmp / storage" in the persistence destination storage 131 is defined as the destination path (Store Path). When deploying a microservice from this microservice package 18, the container management tool 172 extracts this destination path from the configuration file 182 and manages it as the persistence destination.

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

[0035] (2) Then, the control module 175 saves the extracted destination path for data persistence in Act 22. Specifically, the control module 175 associates the extracted destination path for data persistence with a unique microservice ID that identifies the microservice, and stores the associated path as persistence destination information in the microservice information table 121. In this way, the microservice information table 121 functions as a storage unit.

[0036] (3) Then, in 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.

[0037] (4) The container management tool 172, which receives the microservice package 18 through this microservice deployment process, deploys (installs) the microservice 173 from the microservice package 18. Therefore, the control module 175 functions as an installation control unit.

[0038] Then, the control module 175 ends this microservice deployment process. When this microservice deployment process ends, the control module 175 returns to Act 1.

[0039] (5) Then, when the container management tool 172 persists the data generated by the microservice 173, the container management tool 172 writes the data to the “ / tmp / storage” folder of the persistence destination storage 131.

[0040] Returning to the description of FIG. 5 , if it is determined in Act 1 that the microservice will not be deployed, the control module 175 determines whether to back up the persisted data in Act 3. The control module 175 can determine this based on, for example, whether or not a backup instruction (backup command) has been received from the input unit 14 by the operator of the edge device 1. Alternatively, the control module 175 can determine this based on whether or not a backup instruction has been received via the communication unit 16 from the cloud server 51 on the cloud 5 or a control terminal (not shown). The control module 175 can also determine this based on whether or not the daily scheduled backup execution time has arrived. In this way, backups may be performed irregularly or periodically.

[0041] When it is determined that the persisted data should be backed up, the control module 175 executes backup processing as Act 4. This backup processing is processing for backing up data stored in a specified destination path of the persistence destination storage 131, which is the data persistence destination of the microservice 173, to the backup storage 132. This backup processing will be described in detail below with reference to FIGS. 9 and 10. Here, FIG. 9 is a flowchart showing the procedure of this backup processing. Also, FIG. 10 is a schematic diagram showing an example of the relationship between each software configuration and each storage in the edge device 1 during this backup processing.

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

[0043] (2) Furthermore, the control module 175 determines a backup destination in Act 42. Specifically, the control module 175 determines a backup destination folder to be used in the backup storage 132 as the designated backup destination path. This designated backup destination path may correspond to the read designated destination path, may be generated based on the microservice ID, or may be an arbitrary path independent of the microservice ID. Then, the control module 175 saves the determined backup destination in Act 43. Specifically, the control module 175 associates the designated backup destination path determined in Act 42 with the microservice ID corresponding to the target microservice in the microservice information table 121, and stores the path as backup destination information.

[0044] (3) Thereafter, the control module 175 copies the persisted data to the backup destination in Act 44. Specifically, the control module 175 copies the data written to the specified destination path of the data persistence destination in the persistence destination storage 131 to the specified backup destination path in the backup storage 132. Note that the persistence destination storage 131 at the time of backup is also referred to as the pre-replacement persistence destination storage 131-1 below. In this way, the control module 175 functions as a backup unit.

[0045] Then, the control module 175 ends this backup process. Once this backup process is completed, the control module 175 returns to Act 1.

[0046] Returning to the description of FIG. 5 , if it is determined in Act 3 that the persisted data will not be backed up, the control module 175 determines whether to recover the backup data in Act 5. The control module 175 can determine this based on, for example, whether or not a recovery instruction (recovery command) is entered from the input unit 14 by the operator of the edge device 1. The recovery instruction is entered by the operator, for example, when the hardware of the persistence destination storage 131 is replaced with new hardware due to a failure of the persistence destination storage 131. Alternatively, the control module 175 can determine this based on whether or not a recovery instruction is received via the communication unit 16 from the cloud server 51 on the cloud 5 or a control terminal (not shown).

[0047] If it is determined that backup data should be recovered, the control module 175 executes recovery processing as Act 6. This recovery processing is processing for recovering data backed up in the backup storage 132 to a data persistence destination specified by the microservice 173 in the persistence destination storage 131. This backup processing will be described in detail below with reference to FIGS. 11 and 12. Here, FIG. 11 is a flowchart showing the procedure for the recovery processing of Act 6. Also, FIG. 12 is a schematic diagram showing an example of the relationship between each software configuration and each storage in the edge device 1 during this recovery processing.

[0048] In this recovery process, the control module 175 first reads out the designated data persistence path of one microservice 173 to be recovered in Act 61. Specifically, the control module 175 reads out the designated data persistence path that is associated with one microservice ID and stored as persistence destination information from the microservice information table 121.

[0049] (2) Furthermore, in Act 62, the control module 175 reads out the backup destination of the data of the recovery-target microservice 173. Specifically, the control module 175 reads out, from the microservice information table 121, the designated backup path of the backup storage 132, which is stored as backup destination information in association with the read microservice ID as the designated data persistence path.

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

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

[0052] (4) If it is determined in Act 64 that there is no unrecovered data, the control module 175 notifies the container management tool 172 of the end of recovery in Act 65.

[0053] Then, the control module 175 ends this recovery process. After this recovery process is completed, the control module 175 returns to Act 1.

[0054] (5) Upon receiving the recovery notification from this recovery process, the container management tool 172 starts the microservice 173. When the microservice 173 needs data that it generated in the past, the container management tool 172 reads the data from the post-replacement persistence destination storage 131-2, and when it needs to persist the data generated by the microservice 173, the container management tool 172 can write the data to the post-replacement persistence destination storage 131-2.

[0055] As described above in detail, according to this embodiment, when deploying (installing) a microservice, the control module 175 realized by the control application that controls the data processing device acquires a specified destination path, which is storage destination information indicating the storage destination in the persistence destination storage 131 used to store data generated by the microservice, saves this in the microservice information table 121, and causes the container management tool 172 to deploy the microservice. This allows the control module 175 to grasp the persistence destination of the data generated by the microservice.

[0056] According to this embodiment, the control module 175 backs up the data generated by the microservice 173 and stored in the persistence destination storage 131 to the backup storage 132, which is hardware physically different from the persistence destination storage 131, based on the specified destination path for data persistence of the microservice 173 stored in the microservice information table 121, and also stores the specified destination path for the backup of the backup storage 132 in the microservice information table 121. This makes it possible to back up the data generated by the microservice 173.

[0057] Subsequently, if the pre-replacement persistence destination storage 131-1, which is the persistence destination storage 131 storing the data backed up to the backup storage 132, fails and is replaced with a new post-replacement persistence destination storage 131, according to this embodiment, the control module 175 recovers the data backed up in the backup storage 132 to the post-replacement persistence destination storage 131-2 based on the specified backup destination path of the backup storage 132 and the specified data persistence destination path in the pre-replacement persistence destination storage 131-1, which are stored in the microservice information table 121. Therefore, the backed-up data generated by the microservice 173 can be restored to the post-replacement persistence destination storage 131-2, allowing the microservice 173 to continue using the data.

[0058] According to this embodiment, the control module 175 extracts the destination path for data persistence of the microservice from the microservice package 18, which is the installation source file of the microservice. Therefore, the control module 175 can easily obtain the destination path.

[0059] Furthermore, the data processing device according to this embodiment is an edge device 1 that includes a persistence destination storage 131 and communicates with the cloud 5. Therefore, even if storage within the edge device 1 is specified as the persistence destination of the data of a microservice, the control module 175 can grasp the persistence destination of the data generated by the microservice and can back up and recover that data. Therefore, in a system that includes a container 174 running on an on-premise edge device 1, the backup process of the edge device 1 makes it possible to recover data even if the persistence destination storage 131, which is the storage specified as the persistence destination, is damaged.

[0060] Although one embodiment has been described above, the present invention is not limited to this.

[0061] For example, the backup destination of the persisted data may be an external storage rather than the backup storage 132 in the edge device 1. For example, the backup destination may be the same on-premise data storage 3 as the edge device 1, or may be the cloud storage 52 on the cloud 5 with which the edge device 1 communicates.

[0062] Furthermore, the procedures and contents of the flowcharts shown in the embodiments are merely examples. The procedures and contents can be modified as appropriate as long as similar results can be obtained. For example, Act 41, Act 42, and Act 43 may be performed in reverse order or in parallel. In this way, the order of the processes may be changed or multiple processes may be performed in parallel, as long as no discrepancy occurs with the preceding or subsequent processes.

[0063] The above-described data processing device is as follows: (1) A data processing device comprising: an acquisition unit that acquires storage destination information indicating a storage destination in a first storage device used to store data generated by a microservice when the microservice is installed; a storage unit that saves the storage destination information acquired by the acquisition unit; and an installation control unit that installs the microservice for which the storage destination information has been acquired. (2) The data processing device according to (1), further comprising: a backup unit that 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 saved in the save unit. (3) The data processing device according to (2), further comprising: a recovery unit that recovers the data stored in the second storage device to the first storage device, based on the storage destination information saved in the save unit. (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 at the installation source of the microservice. (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. (6) A program for causing a computer that runs a microservice to realize the following functions when installing the microservice: acquiring storage destination information indicating a storage destination in a first storage device to be used for storing data generated by the microservice, saving the acquired storage destination information in memory, and installing the microservice. (7) A computer-readable storage medium storing a program for causing a computer that runs a microservice to realize the following functions when installing the microservice: acquiring storage destination information indicating a storage destination in a first storage device to be used for storing data generated by the microservice, saving the acquired storage destination information in memory, and installing the microservice.(8) A data processing device comprising: a memory in which a microservice is to be installed; a processor that operates the microservice installed in the memory; and a first storage device used to store data generated by the microservice, wherein, when installing the microservice in the memory, the processor: acquires storage destination information indicating a storage destination in the first storage device; stores the acquired storage destination information in the memory; and installs the microservice in the memory.

[0064] The program according to this embodiment may be transferred in a state where it is stored in an electronic device, or may be transferred in a state where it is not stored in an electronic device. In the latter case, the program may be transferred via a network, or may be transferred in a state where it is stored in a storage medium. The storage medium is a non-transitory tangible medium. The storage medium is a computer-readable medium. The storage medium may be in any form, such as a CD-ROM or a memory card, as long as it is capable of storing the program and is computer-readable.

[0065] It should be noted that the embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, and are also included in the inventions and their equivalents as defined in the claims.

Claims

1. A data processing device comprising: an acquisition unit that acquires storage destination information indicating a storage destination in a first storage device to be used to store data generated by a microservice when the microservice is installed; a storage unit that saves 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.

2. The data processing device according to claim 1, further comprising a backup unit that backs up data generated by the microservice stored in the first storage device to 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, further comprising a recovery unit that recovers data stored in said second storage device to said first storage device based on said storage destination information stored in said storage unit.

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

5. The data processing device according to any one of claims 1 to 4, further comprising the first storage device, and being an edge device that communicates with a cloud.

6. A program for causing a computer running a microservice to perform the following functions when installing the microservice: acquire storage destination information indicating the storage destination in a first storage device to be used to store data generated by the microservice; store the acquired storage destination information in memory; and install the microservice.

7. A computer-readable storage medium storing a program for causing a computer running a microservice to acquire storage destination information indicating a storage destination in a first storage device to be used to store data generated by the microservice when the microservice is installed; storing the acquired storage destination information in memory; and installing the microservice.