Microservice cooperation support program, microservice collaboration support device, microservice collaboration support method, and recording medium

The microservice collaboration support program and device enhance AWS Step Functions by managing microservice execution and integration, ensuring maintainable systems with easy function addition.

JP2025147683APending Publication Date: 2025-10-07NEC SOLUTION INNOVATORS LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2024048051
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-03-25
Publication Date
2025-10-07

AI Technical Summary

Technical Problem

Existing systems using AWS Step Functions face difficulties in integrating non-AWS services and maintaining business logic when linking multiple Lambda functions for microservices.

Method used

A microservice collaboration support program and device that manage and control microservice execution through type and order information, enabling integration with excellent maintainability by associating configuration information with execution control information.

Benefits of technology

Facilitates the integration of microservices with improved maintainability, allowing for easy addition of new functions and system maintenance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025147683000001_ABST
    Figure 2025147683000001_ABST
Patent Text Reader

Abstract

To provide a microservice collaboration support program, a microservice collaboration support device, a microservice collaboration support method, and a recording medium that link microservice with improved maintainability.SOLUTION: A microservice collaboration support device, which is a PC on which a microservice collaboration support program is installed, includes a microservice management unit, an execution control information management unit, and an execution control unit. The microservice management unit manages a type of at least one microservice whose execution is controlled by execution control information in association with setting information of the microservice, the execution control information management unit manages the execution control information for each constituent system, and the execution control unit controls, on the basis of the setting information and the execution control information, execution of the microservice. The execution control information includes type information of at least one microservice constituting the system and execution order information of the microservice.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present disclosure relates to a microservice collaboration support program, a microservice collaboration support device, a microservice collaboration support method, and a recording medium. [Background technology]

[0002] AWS Step Functions is known as a means for building a system that links multiple microservices (Non-Patent Document 1). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] “AWS Developer Guide AWS Step Functions”, [online], November 26, 2023 (updated), Amazon Web Services Japan, LLC, [searched March 19, 2024], Internet <URL:https: / / docs.aws.amazon.com / ja_jp / step-functions / latest / dg / step-functions-dg.pdf#welcome> Summary of the Invention [Problem to be solved by the invention]

[0004] However, when building a system using AWS Step Functions, while it is possible to add functions provided by AWS services, it is difficult to add functions that are not provided by AWS services. Also, when multiple Lambda functions are executed with AWS Step Functions to link microservices, it becomes difficult to follow the business logic.

[0005] Therefore, an object of the present disclosure is to provide a microservice integration support program, a microservice integration support device, a microservice integration support method, and a recording medium that enable the integration of microservices with excellent maintainability. [Means for solving the problem]

[0006] In order to achieve the above object, the microservice collaboration support program of the present disclosure includes: Including microservice management procedures, execution control information management procedures, and execution control procedures; The microservice management procedure manages the type of at least one microservice whose execution is controlled by execution control information in association with configuration information of the microservice; The execution control information management procedure manages execution control information for each of the constituent systems, The execution control information includes type information of at least one microservice constituting the system and execution order information of the microservice; The execution control procedure controls execution of the microservice based on the setting information and the execution control information. A microservice collaboration support program for causing a computer to execute each of the above procedures.

[0007] The microservice collaboration support device of the present disclosure includes: A microservice management unit, an execution control information management unit, and an execution control unit, The microservice management unit manages the type of at least one microservice whose execution is controlled by execution control information in association with configuration information of the microservice; the execution control information management unit manages execution control information for each of the constituent systems; The execution control information includes type information of at least one microservice constituting the system and execution order information of the microservice; The execution control unit controls the execution of the microservice based on the setting information and the execution control information.

[0008] The microservice collaboration support method of the present disclosure includes: A microservice management process, an execution control information management process, and an execution control process, The microservice management step manages the type of at least one microservice whose execution is controlled by execution control information in association with configuration information of the microservice; The execution control information management step manages execution control information for each of the constituent systems, The execution control information includes type information of at least one microservice constituting the system and execution order information of the microservice; The execution control step controls the execution of the microservice based on the setting information and the execution control information. Each of the steps is a computer-implemented method.

[0009] The recording medium of the present disclosure includes: Including microservice management procedures, execution control information management procedures, and execution control procedures; The microservice management procedure manages the type of at least one microservice whose execution is controlled by execution control information in association with configuration information of the microservice; The execution control information management procedure manages execution control information for each of the constituent systems, The execution control information includes type information of at least one microservice constituting the system and execution order information of the microservice; The execution control procedure controls execution of the microservice based on the setting information and the execution control information. A computer-readable recording medium that records a microservice collaboration support program for causing a computer to execute each of the above procedures. [Effects of the Invention]

[0010] According to the present disclosure, it is possible to link microservices with excellent maintainability. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a block diagram illustrating a configuration of an example of a microservice cooperation support device according to the present disclosure. [Figure 2] FIG. 2 is a block diagram illustrating an example of a hardware configuration of the microservice cooperation support device according to the present disclosure. [Figure 3] FIG. 3 is a flowchart illustrating an example of a procedure performed by the microservice collaboration support program of the present disclosure. [Figure 4] FIG. 4 is a diagram illustrating an example of setting information in the present disclosure. [Figure 5] FIG. 5 is a diagram illustrating an example of execution control information in the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. The present disclosure is not limited to the following embodiments. In the following drawings, identical parts are designated by the same reference numerals. Furthermore, the descriptions of the embodiments can be used interchangeably unless otherwise specified, and the configurations of the embodiments can be combined unless otherwise specified. In the present disclosure, each drawing may apply to one or more embodiments.

[0013] [Embodiment 1] The microservice collaboration support program disclosed herein is a program for causing a computer to execute a microservice management procedure, an execution control information management procedure, and an execution control procedure. The microservice collaboration support program disclosed herein can also be described as a program for causing a computer to function as the microservice management procedure, the execution control information management procedure, and the execution control procedure. Furthermore, the microservice collaboration support program disclosed herein can also be described as a program for causing a computer to execute, for example, each step of a microservice collaboration support method described below.

[0014] The microservice management procedure manages the type of at least one microservice whose execution is controlled by execution control information in association with configuration information of the microservice; The execution control information management procedure manages execution control information for each of the constituent systems, The execution control information includes type information of at least one microservice constituting the system and execution order information of the microservice; The execution control procedure controls the execution of the microservice based on the setting information and the execution control information.

[0015] For example, the "procedure" in each of the steps can be read as a "process." The microservice collaboration support program of the present disclosure may be recorded on a computer-readable recording medium. The recording medium is, for example, a non-transitory computer-readable storage medium. The recording medium is not particularly limited, and examples thereof include random access memory (RAM), read-only memory (ROM), hard disk (HD), flash memory (e.g., solid state drive (SSD), USB flash memory, SD / SDHC card, etc.), optical disk (e.g., CD-R / CD-RW, DVD-R / DVD-RW, BD-R / BD-RE, etc.), magneto-optical disk (MO), and floppy disk (FD). The microservice collaboration support program of the present disclosure (also referred to as a programming product or program product, for example) may be distributed from an external computer. The "distribution" may be, for example, distribution via a communication network or a device connected via a wired connection. The microservice collaboration support program of the present disclosure may be installed and executed on the device to which it is distributed, or may be executed without being installed. An information processing device capable of executing the microservice collaboration support program of the present disclosure can be referred to as, for example, the microservice collaboration support device of the present disclosure.

[0016] Next, the configuration of an example of a microservice collaboration support device according to the present disclosure will be described with reference to FIG. 1. FIG. 1 is a block diagram showing an example of the configuration of a microservice collaboration support device 10 according to the present disclosure (hereinafter also referred to as the present device 10). As shown in FIG. 1, the present device 10 includes a microservice management unit 11, an execution control information management unit 12, and an execution control unit 13. The present device 10 may also include, for example, an input unit, an output unit, a display unit, and / or a storage unit, although these are not shown. The microservice management unit 11, the execution control information management unit 12, and the execution control unit 13 are capable of executing, for example, a microservice management procedure, an execution control information management procedure, and an execution control procedure in the microservice collaboration support program according to the present disclosure, respectively.

[0017] The device 10 may be, for example, a single device including the above-described units, or a device in which the units can be connected via a communication network. The device 10 can also be connected to an external device (described later) via the communication network. The communication network is not particularly limited and any known network can be used, for example, a wired or wireless network. Examples of the communication network include the Internet, the World Wide Web (WWW), a telephone line, a Local Area Network (LAN), a Storage Area Network (SAN), a Delay Tolerant Networking (DTN), a Low Power Wide Area Network (LPWA), and a Local 5G (L5G). Examples of wireless communication include Wi-Fi (registered trademark), Bluetooth (registered trademark), Local 5G, and LPWA. Examples of the wireless communication include direct communication between devices (Ad Hoc communication), infrastructure communication, and indirect communication via an access point. The device 10 may be incorporated into a server as a system. Furthermore, the present device 10 may be, for example, a personal computer (PC, for example, desktop or notebook type) on which the program of the present disclosure is installed, a smartphone, a tablet terminal, etc. The present device 10 may be in the form of cloud computing or edge computing, for example, in which at least one of the above-mentioned units is located on a server and the other units are located on a terminal.

[0018] 2 shows a block diagram of the hardware configuration of the device 10. The device 10 includes, for example, a central processing unit (CPU, GPU, etc.) 101, a memory 102, a bus 103, a storage device 104, an input device 105, an output device 106, and a communication device 107. The components of the device 10 are connected to each other via the bus 103 and their respective interfaces (I / F).

[0019] The central processing unit 101 cooperates with other components via a controller (such as a system controller or an I / O controller) and is responsible for overall control of the device 10. In the device 10, the central processing unit 101 executes, for example, the program of the present disclosure (the microservice cooperation support program) and other programs, and also reads and writes various types of information. Specifically, for example, the central processing unit 101 functions as a microservice management unit 11, an execution control information management unit 12, and an execution control unit 13. The device 10 may include other arithmetic units such as a CPU, a GPU (Graphics Processing Unit), an APU (Accelerated Processing Unit), or a combination thereof as the arithmetic unit.

[0020] The bus 103 can also be connected to, for example, external devices. Examples of the external devices include an external storage device (such as an external database), a printer, an external input device, an external display device, and an external imaging device. The device 10 can be connected to an external network (the communication line network) by, for example, a communication device 107 connected to the bus 103, and can also be connected to other devices via the external network.

[0021] The memory 102 may be, for example, a main memory (primary storage device). When the central processing unit 101 performs processing, the memory 102 reads various operating programs, such as the program of the present disclosure, stored in the storage device 104 (described later), and the central processing unit 101 receives data from the memory 102 and executes the programs. The main memory may be, for example, a RAM (random access memory). The memory 102 may also be, for example, a ROM (read only memory).

[0022] The storage device 104 is also referred to as an auxiliary storage device, for example, in contrast to the main memory (primary storage device). As described above, the storage device 104 stores an operating program including the program of the present disclosure. The storage device 104 may be, for example, a combination of a recording medium and a drive for reading and writing data from and to the recording medium. The recording medium is not particularly limited and may be, for example, an internal or external type, such as a hard disk (HD), CD-ROM, CD-R, CD-RW, MO, DVD, flash memory, or memory card. The storage device 104 may be, for example, a hard disk drive (HDD) or a solid-state drive (SSD) in which the recording medium and drive are integrated. When the device 10 includes the storage unit, for example, the storage device 104 functions as the storage unit. The storage unit can store, for example, execution control information, microservices, and setting information, which will be described later.

[0023] In the present device 10, the memory 102 and the storage device 104 can also store various information such as log information, information acquired from an external database (not shown) or an external device, information generated by the present device 10, and information used when the present device 10 executes processing. In this case, the memory 102 and the storage device 104 may store, for example, the above-mentioned information on the user of the present device. Note that at least a portion of the information may be stored, for example, in an external server other than the memory 102 and the storage device 104, or may be stored in a distributed manner across multiple terminals using blockchain technology or the like.

[0024] The device 10 further includes, for example, an input device 105 and an output device 106. Examples of the input device 105 include pointing devices such as a touch panel, track pad, and mouse; a keyboard; imaging means such as a camera and scanner; card readers such as an IC card reader and a magnetic card reader; and audio input means such as a microphone. Examples of the output device 106 include display devices such as an LED display and a liquid crystal display; audio output devices such as a speaker; a printer; and the like. In the first embodiment, the input device 105 and the output device 106 are configured separately, but the input device 105 and the output device 106 may be configured as an integrated device, such as a touch panel display.

[0025] An example of processing by the microservice cooperation support program of the present disclosure will be described in more detail with reference to Fig. 3. Fig. 3 is a flowchart showing an example of each procedure of the microservice cooperation support program of the present disclosure.

[0026] The microservice management unit 11 manages the type of at least one microservice whose execution is controlled by execution control information by associating it with the configuration information of the microservice (S1, microservice management procedure). The microservice is, for example, a service that individually configures each function included in an information system. The type of microservice is not particularly limited and can be any microservice. The configuration information is, for example, information on settings required for executing the microservice. The configuration information includes, for each microservice, at least one piece of information: a microservice path, a storage location for the execution result, and a reference source for the information. The microservice management unit 11 may store the type of microservice and the configuration information in the storage unit of the device 10 or in a recording medium external to the device 10. Figure 4 shows a specific example of information managed by the microservice management unit 11, but the present disclosure is not limited to this example. As shown in Figure 4, the microservice management unit 11 manages the configuration information, including the following items, by associating it with a microservice (ARG.JSON), for example: [ENV]...settings section [PARAM] [ARG_JSON_FILE] [RTN_JSON_FILE] [SERVICES]...Services to be used [SEVICE_NAME:KMS] [DOMAIN]AAA.COM [ENDPOINT] / BBB / CCC [URL_PARAM] [AAA] TEST [SEVICE_NAME:GET_SOSHIKI_ID] ...

[0027] The execution control information management unit 12 manages execution control information for each constituent system (S2, execution control information management procedure). The execution control information includes type information of at least one microservice that constitutes the system and execution order information of the microservice. The execution control information management unit 12 can, for example, set the type and execution order of any microservices to suit the system built by the user. A specific example of the execution control information is shown in Fig. 5. As shown in Fig. 5, the execution control information management unit 12 associates and manages execution control information including the execution order of microservices and parameters required for executing the microservices for each system built. [EXEC]...Section that describes execution control [0] Processing order [CONST] [VAL1]: XXXXX [TRY] [DO]GET_SOSHIKI_ID [PARAM] [ARG] 0_ARG.JSON [RTN] 0_RTN.JSON [CHECK] [CATCK_PTN] [FINALY]

[0028] The execution control unit 13 controls the execution of the microservices based on the setting information and the execution control information (S3, execution control procedure). The execution control unit 13 queues the microservices based on, for example, the type information and execution order information included in the execution control information, and specifies a storage location for the execution results and a reference location for the information for each microservice based on setting information corresponding to the queued microservices.

[0029] The microservice integration support method of the present disclosure is implemented by, for example, replacing the "procedures" in the microservice integration support program of the present disclosure with "processes." Specifically, the microservice integration support method of the present disclosure includes a microservice management process, an execution control information management process, and an execution control process. The microservice management process manages the type of at least one microservice whose execution is controlled by the execution control information in association with configuration information for the microservice. The execution control information management process manages the execution control information for each system that constitutes the system. The execution control information includes type information for at least one microservice that constitutes the system and execution order information for the microservice. The execution control process controls the execution of the microservice based on the configuration information and the execution control information. The microservice integration support method of the present disclosure can be implemented, for example, using the microservice integration support device 10 of the present disclosure shown in FIG. 1 or FIG. 2. Note that the microservice integration support method of the present disclosure is not limited to a method using the microservice integration support device 10, for example. The microservice collaboration support method of the present disclosure can, for example, incorporate the descriptions of the microservice collaboration support program and microservice collaboration support device of the present disclosure.

[0030] According to the microservice integration support program of the present disclosure, the microservice management procedure manages the type of at least one microservice whose execution is controlled by execution control information by linking the type of the microservice with configuration information for the microservice. The execution control information management procedure manages the execution control information for each constituent system. The execution control information includes type information for at least one microservice constituting the system and execution order information for the microservice. The execution control procedure controls the execution of the microservice based on the configuration information and the execution control information. Therefore, according to the microservice integration support program of the present disclosure, even when building a system in which multiple microservices are integrated, system maintenance is possible simply by maintaining the configuration information in the microservice integration support program of the present disclosure. Furthermore, when adding functions to the system, new functions can be easily added by further adding new microservices and their configuration information. Therefore, according to the present disclosure, microservice integration with excellent maintainability is possible.

[0031] Although the present disclosure has been described above with reference to the embodiments, the present disclosure is not limited to the above-described embodiments. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present disclosure within the scope of the present disclosure. Furthermore, each embodiment can be combined with other embodiments as appropriate.

[0032] <Additional Notes> Some or all of the above embodiments can be described as, but not limited to, the following supplementary notes. (Appendix 1) Including microservice management procedures, execution control information management procedures, and execution control procedures; The microservice management procedure manages the type of at least one microservice whose execution is controlled by execution control information in association with configuration information of the microservice; The execution control information management procedure manages execution control information for each of the constituent systems, The execution control information includes type information of at least one microservice constituting the system and execution order information of the microservice; The execution control procedure controls execution of the microservice based on the setting information and the execution control information. A microservice collaboration support program for causing a computer to execute each of the above procedures. (Appendix 2) The microservice integration support program according to claim 1, wherein the configuration information includes, for each microservice, at least one piece of information: a path to the microservice, a location where the execution results are stored, and a reference source for the information. (Appendix 3) The execution control procedure includes: queuing the microservices based on the type information and execution order information included in the execution control information; A microservice integration support program according to appendix 2, which specifies a storage location for execution results and a reference location for information for each microservice based on configuration information corresponding to the queued microservice. (Appendix 4) A microservice management unit, an execution control information management unit, and an execution control unit, The microservice management unit manages the type of at least one microservice whose execution is controlled by execution control information in association with configuration information of the microservice; the execution control information management unit manages execution control information for each of the constituent systems; The execution control information includes type information of at least one microservice constituting the system and execution order information of the microservice; The execution control unit controls the execution of the microservices based on the setting information and the execution control information. (Appendix 5) The microservice collaboration support device according to claim 4, wherein the configuration information includes, for each microservice, at least one piece of information: a path of the microservice, a storage location of the execution result, and a reference source of the information. (Appendix 6) The execution control unit queuing the microservices based on the type information and execution order information included in the execution control information; A microservice collaboration support device according to claim 5, which specifies a storage location for execution results and a reference location for information for each microservice based on configuration information corresponding to the queued microservice. (Appendix 7) A microservice management process, an execution control information management process, and an execution control process, The microservice management step manages the type of at least one microservice whose execution is controlled by execution control information in association with configuration information of the microservice; The execution control information management step manages execution control information for each of the constituent systems, The execution control information includes type information of at least one microservice constituting the system and execution order information of the microservice; The execution control step controls the execution of the microservice based on the setting information and the execution control information. A microservice collaboration support method in which each of the steps is executed by a computer. (Appendix 8) The microservice collaboration support method according to claim 7, wherein the configuration information includes, for each microservice, at least one piece of information: a path to the microservice, a location where the execution results are stored, and a reference source for the information. (Appendix 9) The execution control step includes: queuing the microservices based on the type information and execution order information included in the execution control information; A microservice integration support method according to claim 8, which specifies a storage location for execution results and a reference location for information for each microservice based on configuration information corresponding to the queued microservice. (Appendix 10) Including microservice management procedures, execution control information management procedures, and execution control procedures; The microservice management procedure manages the type of at least one microservice whose execution is controlled by execution control information in association with configuration information of the microservice; The execution control information management procedure manages execution control information for each of the constituent systems, The execution control information includes type information of at least one microservice constituting the system and execution order information of the microservice; The execution control procedure controls execution of the microservice based on the setting information and the execution control information. A computer-readable recording medium on which a microservice collaboration support program for causing a computer to execute each of the above procedures is recorded. (Appendix 11) The microservice collaboration support device according to claim 10, wherein the configuration information includes, for each microservice, at least one piece of information: a path of the microservice, a storage location of the execution result, and a reference source of the information. (Appendix 12) The execution control procedure includes: queuing the microservices based on the type information and execution order information included in the execution control information; 12. The recording medium of claim 11, wherein a storage location for execution results and a reference location for information are specified for each microservice based on configuration information corresponding to the queued microservice. [Industrial Applicability]

[0033] The present disclosure enables the integration of microservices with excellent maintainability, and therefore can be widely and usefully utilized in the IT field. [Explanation of symbols]

[0034] 10 Microservice integration support device 11 Microservice Management Department 12 Execution control information management unit 13 Execution control section 101 Central Processing Unit 102 memory 103 Bus 104 Storage device 105 Input Device 106 Output Device 107 Communication Devices

Claims

1. Including microservice management procedures, execution control information management procedures, and execution control procedures; The microservice management procedure manages the type of at least one microservice whose execution is controlled by execution control information in association with configuration information of the microservice; The execution control information management procedure manages execution control information for each of the constituent systems, The execution control information includes type information of at least one microservice constituting the system and execution order information of the microservice; The execution control procedure controls execution of the microservice based on the setting information and the execution control information. A microservice collaboration support program for causing a computer to execute each of the above procedures.

2. The microservice collaboration support program according to claim 1 , wherein the setting information includes, for each microservice, at least one piece of information regarding a path of the microservice, a storage location of an execution result, and a reference source of the information.

3. The execution control procedure includes: queuing the microservices based on the type information and execution order information included in the execution control information; The microservice collaboration support program according to claim 2 , further comprising: specifying a storage location for execution results and a reference location for information for each microservice based on configuration information corresponding to the queued microservice.

4. A microservice management unit, an execution control information management unit, and an execution control unit, The microservice management unit manages the type of at least one microservice whose execution is controlled by execution control information in association with configuration information of the microservice; the execution control information management unit manages execution control information for each of the constituent systems; The execution control information includes type information of at least one microservice constituting the system and execution order information of the microservice; The execution control unit controls the execution of the microservices based on the setting information and the execution control information.

5. The microservice collaboration support device according to claim 4 , wherein the setting information includes, for each microservice, at least one piece of information regarding a path of the microservice, a storage location of an execution result, and a reference source of the information.

6. The execution control unit queuing the microservices based on the type information and execution order information included in the execution control information; The microservice collaboration support device according to claim 5 , further comprising: a storage location for execution results and a reference location for information for each microservice based on configuration information corresponding to the queued microservices.

7. A microservice management process, an execution control information management process, and an execution control process, The microservice management step manages the type of at least one microservice whose execution is controlled by execution control information in association with configuration information of the microservice; The execution control information management step manages execution control information for each of the constituent systems, The execution control information includes type information of at least one microservice constituting the system and execution order information of the microservice; The execution control step controls the execution of the microservice based on the setting information and the execution control information. A microservice collaboration support method in which each of the steps is executed by a computer.

8. The microservice collaboration support method according to claim 7 , wherein the setting information includes, for each microservice, at least one piece of information regarding a path of the microservice, a storage location of an execution result, and a reference source of the information.

9. The execution control step includes: queuing the microservices based on the type information and execution order information included in the execution control information; The microservice collaboration support method according to claim 8 , further comprising specifying a storage location for execution results and a reference location for information for each microservice based on configuration information corresponding to the queued microservice.

10. Including microservice management procedures, execution control information management procedures, and execution control procedures; The microservice management procedure manages the type of at least one microservice whose execution is controlled by execution control information in association with configuration information of the microservice; The execution control information management procedure manages execution control information for each of the constituent systems, The execution control information includes type information of at least one microservice constituting the system and execution order information of the microservice; The execution control procedure controls execution of the microservice based on the setting information and the execution control information. A computer-readable recording medium on which a microservice collaboration support program for causing a computer to execute each of the above procedures is recorded.