JP7065697B2 - System and service control method - Google Patents

Description

The present invention relates to a system for developing and executing a service combining microservices.

In recent years, a development method that provides one service by combining small services developed individually has attracted attention. These are known as microservices, SaaS (Software as a service), SOA (Service Oriented Architecture), and the like. In the following description, when the development method is expressed, it is described as a microservice architecture, and a group of services developed using the microservice architecture is described as a microservice.

In the microservices architecture, services are developed by combining multiple microservices. The developed service can be incorporated as a microservice that constitutes another service.

Services developed using the microservice architecture are processed via a network in a private cloud built on the customer site, a public cloud outside the customer site, and the like. In order to facilitate service development using a microservice architecture, it is the mainstream to provide a development platform PaaS (Platform AS a Service) that easily connects APIs provided by a microservice architecture.

For example, Patent Document 1 discloses a technique for providing various microservices on the cloud by connecting APIs with each other by an interconnection platform. In addition, a method of providing a platform for easily developing an application by arranging a processing server based on a GUI and connecting the processing servers to each other for microservice processing is widespread. For example, Node-RED provided as OSS. In Node-RED, a process element called a node that realizes a specific function is connected to generate one flow (microservice).

US Patent Application Publication No. 2016/0124742

Services developed using the microservice architecture are processed for each microservice that constitutes the service. Therefore, when a plurality of microservices are arranged in a system connected via a network, the execution speed of the services is reduced by the communication between the microservices, and the consumption of communication resources is increased.

A typical example of the invention disclosed in the present application is as follows. That is, it is a system that provides a service composed of a plurality of microservices and includes a plurality of computer systems capable of executing the microservices, and the plurality of computer systems includes a plurality of computers and the plurality of micros. It has a service order control unit that controls the execution order of services, and the service order control unit has a plurality of execution microservices for providing the first service, their execution order, and arrangement conditions of the plurality of execution microservices. The execution computer system for executing the plurality of execution microservices is determined so as to acquire the information regarding the above, satisfy the arrangement condition, and reduce the communication at the time of execution of the plurality of execution microservices, and determine the plurality of execution microservices. The execution computer system that generates the execution order of the execution microservices and the processing management information including the plurality of execution computer systems, transmits the processing management information to the plurality of execution computer systems, and receives the processing management information is the execution computer system. When there are a plurality of the execution microservices to be executed, the computer for executing the plurality of execution microservices so as to satisfy the arrangement condition and reduce communication at the time of execution of the plurality of execution microservices. A decision is made, and based on the decision, the plurality of execution microservices are deployed to the computer, and when the service order control unit detects the execution trigger of the first service, it is based on the processing management information. The execution computer system that selects one execution computer system, sends an execution request including the execution order of the execution microservices executed by the selected execution computer system, and executes a plurality of execution microservices. Is characterized in that data indicating a processing result is transmitted after executing all of the plurality of execution microservices .

According to one embodiment of the present invention, the execution speed of the service developed by using the microservice architecture can be improved, and the consumption of communication resources can be reduced. Issues, configurations and effects other than those mentioned above will be clarified by the description of the following examples.

It is a figure which shows the configuration example of the computer system of Example 1. FIG. It is a block diagram which shows the configuration example of the base server of Example 1. FIG. It is a block diagram which shows the configuration example of the service processing sir of Example 1. FIG. It is a figure which shows an example of the data structure of the processing management information of Example 1. FIG. It is a figure which shows an example of the data structure of the service control system information of Example 1. FIG. It is a figure which shows an example of the GUI provided by the development infrastructure processing part of Example 1. FIG. It is a flowchart explaining the process executed by the base server of Embodiment 1. FIG. It is a flowchart explaining the microservice arrangement optimization process executed by the base server of Example 1. FIG. It is a flowchart explaining the process to execute when the service process server of Example 1 accepts the deployed microservice (executable file). It is a flowchart explaining the process which the base server of Example 1 executes at the time of providing a service. It is a figure which shows an example of the GUI provided by the development infrastructure processing part of Example 2. FIG. It is a flowchart explaining the microservice arrangement optimization process executed by the base server of Example 2. It is a flowchart explaining the microservice arrangement optimization process executed by the base server of Example 2. It is a flowchart explaining the process which the base server of Example 2 executes at the time of providing a service. It is a flowchart explaining the process to execute when the base server of Example 3 sends a process request. It is a flowchart explaining the process which the base server of Example 4 executes at the time of providing a service. It is a figure which shows an example of the portal presented by the development infrastructure processing part of Example 5. It is a figure which shows an example of the GUI provided by the development infrastructure processing part of Example 5. It is a figure which shows an example of the GUI provided by the development infrastructure processing part of Example 5. It is a figure which shows an example of the GUI provided by the development infrastructure processing part of Example 5.

In the present specification, various information may be described by the expression of "aaa table", but various information may be expressed by a data structure other than the table. The "aaa table" can also be referred to as "aaa information" to show that it does not depend on the data structure.

In the present specification, the configuration of each table is an example, and one table may be divided into two or more tables, or all or a part of two or more tables may be one table. ..

As used herein, an "interface" may include one or more communication interface devices. The one or more communication interface devices may be one or more similar communication interface devices such as NIC (Network Interface Card) and HBA (Host Bus Adapter), or two or more different types of communication interface devices. There may be.

In the present specification, when the processing is described with the program as the subject, it is shown that the processing is executed by the arithmetic unit such as the processor and the CPU (Central Processing Unit) and the computer having the arithmetic unit.

In the present specification, the controller included in the storage system or the like may include an arithmetic unit or a hardware circuit that performs a part or all of the processing performed by the controller.

In the present specification, the program may be stored in the computer in advance, or may be installed in the computer from the program source. The program source may be, for example, a program distribution server or a computer-readable (eg, non-temporary) storage medium. Further, in the following description, two or more programs may be realized as one program, or one program may be realized as two or more programs.

Although the ID is described as an example of the element identification information in the present specification, other identification information may be used instead of the ID, or other identification information may be used together with the ID.

In the present specification, when not distinguishing the same kind of elements, the same reference code is used, and when distinguishing the same kind of elements, the same kind of distinguishable reference code is used.

As used herein, a distributed system includes one or more physical computers. The one or more physical computers may include at least one of a physical server and a physical storage. As the physical computer, a virtual computer such as a VM (Virtual Machine) may be executed, or SDx (Software-Defined answering) may be executed. As the SDx, for example, SDS (Software Defined Storage) or SDDC (Software-defined Storage), which is an example of a virtual storage device, can be adopted.

FIG. 1 is a diagram showing a configuration example of the computer system of the first embodiment.

The computer system is composed of a basic system 100 and a plurality of data centers 101-1 and 101-2. The infrastructure system 100 and the data centers 101-1 and 101-2 are connected to each other via the network 102. The network 102 is, for example, a WAN (Wide Area Network), a LAN (Local Area Network), a SAN (Storage Area Network), the Internet, a public line, a dedicated line, and the like. The connection method of the network 102 may be either wired or wireless.

In this specification, when data centers 101-1 and 101-2 are not distinguished, they are referred to as data center 101. When the infrastructure system 100 and the data center 101 are not distinguished, they are described as a processing system.

The computer system provides services realized by a combination of multiple microservices. Microservices consist of processes that realize at least one function. In this specification, a processing element that realizes a specific function is referred to as a node.

Here, the deployment method of microservices in the microservice architecture will be described. As a method of deploying microservices, there are a method of deploying a plurality of microservices to one processing system and a method of deploying a plurality of processing systems so as to distribute each of the plurality of microservices. "Deployment" in the present specification means that the service is placed in the execution environment in an executable state.

The former method can be considered as a service using artificial intelligence or the like. Artificial intelligence builds a model by learning using raw data, for example, and discriminates data and determines behavior based on the model. A computer (server) that stores data used for learning is made to execute a microservice to provide the service. The latter method improves the performance of services by distributing microservices to multiple processing systems.

The infrastructure system 100 is a system that provides computer resources and software that realizes the development infrastructure 120 of microservices. The infrastructure system 100 also provides an execution infrastructure 121 for microservices. The data center 101 is a system that provides an execution platform 121 for microservices.

The board system 100 is a system that provides a board, and is composed of a plurality of board servers 110. The configuration of the base server 110 will be described with reference to FIG.

The data center 101 is a system that manages data and executes processing using the data, and is composed of a plurality of service processing servers 111. The data A170 is stored in the data center 101-1 and the data B171 is stored in the data center 101-2. The configuration of the service processing server 111 will be described with reference to FIG.

As used herein, the term "base" shall include computer resources and programs and APIs that provide specific functions.

In this specification, when the service processing servers 111-1 and 111-2 are not distinguished, they are referred to as the service processing server 111. When the base server 110 and the service processing server 111 are not distinguished, they are described as a server.

The board server 110 has a function of providing the development board 120 and the execution board 121. The service processing server 111 has a function of providing the execution platform 121. The development platform 120 is a platform for developing microservices. The execution platform 121 is a platform for executing microservices.

In the first embodiment, it is assumed that a service including process A, process B, process C, process D, process E, process F, and process Z representing microservices is provided. For the sake of simplicity, it is assumed that one process corresponds to one node.

It is assumed that the processes are executed in the order of process A, process B, process C, process D, process E, process F, and process Z. The processing A150, processing B151, processing C152, processing D153, processing E154, processing F155, and processing Z156 on the development platform 120 are treated as data in the form of source code or the like. Further, the process A160, the process B161, the process C162, the process D163, the process E164, the process F165, and the process Z166 on the execution board 121 are treated as data such as an execution format file.

In the computer system of the first embodiment, the microservices constituting the service developed by using the development platform 120 are converted into execution format data and deployed on the execution platform 121 on the platform system 100.

In this specification, in the development of the service using the development platform 120, it is assumed that the deployment destination of each microservice is set as follows. The process A160, the process C162, and the process F165 are deployed on the execution board 121 of the board server 110. Process B161 and process D163 are deployed on the execution platform 121 of the data center 101-1. The process E164 and the process Z166 are deployed on the execution platform 121 of the data center 101-2.

Further, in the present specification, it is assumed that the process A160 can be executed only by the infrastructure server 110 of the infrastructure system 100, and the processes B161 and D163 can be executed only by the service processing server 111-1 of the data center 101-1. , Processing E and processing Z166 can be executed only by the service processing server 111-2 of the data center 101-2. The server that executes the process C162 and the process F165 is not limited.

In the traditional method, microservices are deployed to the processing system according to the default settings. In this case, in executing the service, the infrastructure server 110, the service processing server 111-1, and the service processing server 111-2 of each processing system transmit and receive data by communication via the network 102. Therefore, the delay in the execution speed of the service and the increase in the consumption of communication resources become problems.

In the system of the first embodiment, in the execution platform 121 on the platform system 100, the execution order of the microservices is analyzed, and based on the analysis result, a processing system that deploys the microservices so as to solve the above problems is provided. It is determined.

In the example shown in FIG. 1, the process A160 is deployed on the execution platform 121 of the infrastructure server 110, the process B161, the process C162, and the process D163 are deployed on the execution platform 121 of the service processing server 111-1, and the process E164 and the process F165 are deployed. , And the processing Z166 are deployed on the execution platform 121 of the service processing server 111-2.

FIG. 2 is a block diagram showing a configuration example of the base server 110 of the first embodiment.

The board server 110 has a CPU 200, a memory 201, a storage device 202, and a network interface 203. The hardware is connected to each other via the internal bus 204.

The CPU 200 executes a program stored in the memory 201. When the CPU 200 executes processing according to a program, it operates as a functional unit (module) that realizes a specific function of the base server 110.

The memory 201 is a storage device composed of a volatile storage element such as a DRAM (Dynamic Random Access Memory) or a non-volatile storage element such as a Story Class Memory. The memory 201 stores a program executed by the CPU 200 and information used by the program. The memory 201 is also used as a cache area for temporarily storing user data and a work area used by the program.

The memory 201 of the first embodiment stores a program that realizes the development infrastructure processing unit 210, the service order control unit 211, and the service execution unit 212. Further, the memory 201 stores the processing management information T100 and the service control system information T110.

The development infrastructure processing unit 210 provides various functions for realizing the development infrastructure 120. The service order control unit 211 determines a processing system to which the microservice is optimally deployed, and sends a processing request including an execution order to the processing system. Further, the service order control unit 211 determines a server to be deployed in the processing system of the deployed microservice. The service execution unit 212 provides various functions for realizing the execution platform 121. In addition, the service execution unit 212 executes the deployed microservice.

The processing management information T100 is information for managing the microservice, and is generated when the microservice is deployed. The data structure of the processing management information T100 will be described with reference to FIG. The service control system information T110 is information for controlling a server that executes microservices, and is set in advance in the base server 110. The data structure of the service control system information T110 will be described with reference to FIG.

The storage device 202 is a storage device such as an HDD (Hard Disk Drive) and an SSD (Solid State Drive). The storage device 202 permanently stores the data.

Although the program and information are described as being stored in the memory 201, they may be stored in the storage device 202. In this case, the CPU 200 reads the program and information from the storage device 202 and loads them on the memory 201.

The network interface 203 is an interface for connecting to another device via a network.

The board server 110 may have an input device such as a keyboard, a mouse, and a touch panel, and an output device such as a display and a printer.

FIG. 3 is a block diagram showing a configuration example of the service processing server 111 of the first embodiment.

The service processing server 111 includes a CPU 300, a memory 301, a storage device 302, and a network interface 303. The hardware is connected to each other via the internal bus 304.

The CPU 300, the memory 301, the storage device 302, and the network interface 303 are the same hardware as the CPU 200, the memory 201, the storage device 202, and the network interface 203.

The memory 301 stores a program that realizes the service order control unit 211 and the service execution unit 212, and also stores the processing management information T100 and the service control system information T110. The processing management information T100 stores information related to the microservice deployed on the service processing server 111.

FIG. 4 is a diagram showing an example of the data structure of the processing management information T100 of the first embodiment.

The processing management information T100 includes an entry composed of a processing order C101, a processing name C102, an arrangement change flag C103, a processing system information C104, and a change processing system information C105. One entry corresponds to one microservice.

The processing order C101 is a field for storing the execution order of the microservices. The process name C102 is a field for storing the name of the microservice. The process name C102 may store an ID or the like assigned to the microservice instead of the name of the microservice.

The placement change flag C103 is a field for storing a flag indicating whether or not the processing system to which the microservice is deployed can be changed. The placement change flag C103 stores either "OK" indicating that the processing system to which the microservice is deployed can be changed or "No" indicating that the processing system to which the microservice is deployed cannot be changed. ..

The processing system information C104 is a field for storing information for accessing the processing system to be the default deployment destination of the microservice. For example, when each server sends and receives a request and a response based on the http protocol, the URL is stored in the processing system information C104.

The change processing system information C105 is a field for storing information for accessing the processing system to which the microservice changed by the service order control unit 211 is deployed. The change processing system information C105 of the entry corresponding to the microservice whose processing system has not been changed is blank.

The values stored in the process name C102, the arrangement change flag C103, and the processing system information C104 are included in the metadata of the source code defining the microservice or the execution file of the microservice. The processing order C101 is determined when the microservice is deployed (compiled) from the development base 120 to the execution base 121. The change processing system information C105 is updated based on the processing result of the service order control unit 211.

When a unique microservice (node) is developed on the development platform 120, the arrangement change flag C103 is set to "No" for the microservice. At this time, the change processing system information C105 may store a "Local Node" indicating that the server to be deployed is the base server 110 that developed the microservice.

FIG. 5 is a diagram showing an example of the data structure of the service control system information T110 of the first embodiment.

The service control system information T110 includes an entry composed of the service order control unit information C111 and the offload flag C112. One entry corresponds to the service sequence control unit 211 included in one server.

The service order control unit information C111 is a field for storing information indicating the service order control unit 211 that controls the execution order of the microservices. In the service order control unit information C111, for example, a value in which a control name such as "Control" is added after the domain name of the URL indicating the server is stored.

The offload flag C112 requests processing from the processing system to which the next microservice of the last executed microservice is deployed after all the microservices deployed in the processing system corresponding to the service order control unit information C111 are completed. This field stores a flag indicating whether or not to send. In the present specification, the above-mentioned processing is referred to as an offload processing. The offload flag C112 stores either "OK" indicating that the offload processing is permitted or "No" indicating that the offload processing is not permitted.

The details of the processing using the service control system information T110 will be described in the fourth embodiment.

FIG. 6 is a diagram showing an example of the GUI provided by the development infrastructure processing unit 210 of the first embodiment.

When developing a service, the development infrastructure processing unit 210 displays the GUI 600 as shown in FIG. 6 to the user. The GUI 600 is composed of a palette 610, a workspace 620, a console 630, and a deploy button 640.

The pallet 610 is a column for displaying microservices. An icon representing a microservice is displayed on the pallet 610. Workspace 620 is a column for configuring a flow of microservices that realize services. The console 630 is a column for setting and displaying attributes such as output of microservice processing results and default server information. The deploy button 640 is an operation button for deploying the flow of the microservice set by using the workspace 620.

The user drags and drops the microservices process from palette 610 to workspace 620. In addition, the user connects the microservices arranged in the workspace 620 and generates a flow for providing the service. In addition, the user confirms and sets the attributes of the microservice using the console 630 as necessary. The user operates the deploy button 640 after making the necessary settings.

For example, when the user operates the deploy button 640, an executable file to which the flow information set in the workspace 620 and the information set using the console 630 are added as metadata is generated. Further, the service control system information T110 is generated based on the setting of the console 630.

FIG. 7 is a flowchart illustrating a process executed by the base server 110 of the first embodiment. When the deploy button 640 is operated by the user, the process described below is executed.

First, the base server 110 executes the microservice arrangement optimization process (step S101). The details of the microservice arrangement optimization process will be described with reference to FIG.

Next, the base server 110 notifies the processing system to which the microservice is deployed the result of the microservice placement optimization process (step S103). For example, the service order control unit 211 of the base server 110 notifies the base server 110 or the service processing server 111 included in the processing system of the entry corresponding to the microservice deployed from the processing management information T100. In this case, the service processing server 111 generates the processing management information T100 including the entry in the memory 301.

Next, the base server 110 deploys the microservice to the processing system (step S105).

FIG. 8 is a flowchart illustrating a microservice arrangement optimization process executed by the base server 110 of the first embodiment. In this optimization process, it is investigated whether the processing system that performs the processing for each processing can be changed, and the processing that is adjacent in the processing order is optimized to be processed by the same processing system.

When the node is compiled by the development infrastructure processing unit 210 and the execution file of the node is generated, the service order control unit 211 generates the processing management information T100 (step S201). Specifically, the following processing is executed.

The service order control unit 211 generates entries in the processing management information T100 for the number of microservices arranged in the workspace 620. Further, the development infrastructure processing unit 210 acquires a value from the metadata of the execution file of the microservice, and sets the acquired value in the entry processing name C102, the arrangement change flag C103, and the processing system information C104. These metadata are described in setting information such as node properties. Further, the development infrastructure processing unit 210 sets the execution order in the processing order C101 of each entry based on the metadata. At this time, the service order control unit 211 sorts the entries of the processing management information T100 based on the execution order.

Further, the service order control unit 211 initializes the variable N and the variable M. Specifically, the service order control unit 211 sets the variable N to "1" and the variable M to "0". The variable N is used to identify the microservices being processed, and the variable M is used to identify the microservices to be compared.

Next, the service order control unit 211 selects the target microservice (step S203).

Specifically, the service order control unit 211 selects an entry in which the processing order C101 matches the variable N from the processing management information T100.

Next, the service order control unit 211 determines whether or not the arrangement change flag C103 of the entry corresponding to the target microservice is “possible” (step S205).

When the arrangement change flag C103 of the entry corresponding to the target microservice is determined to be “OK”, the service order control unit 211 proceeds to step S213.

If it is determined in step S205 that the placement change flag C103 of the entry corresponding to the target microservice is not "possible", the service order control unit 211 determines whether or not the variable M is 0 (step S207). ..

If it is determined that the variable M is 0, the service order control unit 211 proceeds to step S211.

When it is determined that the variable M is not 0, the service order control unit 211 transfers the microservice processing system between the entry matching the variable M of the processing management information T100 to the entry matching the variable N-1 to the same system. Change (step S209). After that, the service order control unit 211 proceeds to step S211.

Specifically, the service order control unit 211 has the Mth entry in the change processing system information C105 of all the entries existing between the entry in which the processing order C101 is M and the entry in which the processing order C101 is N. Set the value of the processing system information C104 of.

Further, it may be changed to the entry processing system C104 whose entry is M, the entry processing system C104 whose entry is N-1, or the entry processing system C104 which is in between. You may.

By changing the processing system that executes the microservice based on the above-mentioned processing procedure, it is possible to reduce the communication between the processing systems associated with the execution of the microservice. For example, when N is 7 and M is 5, the processing system that executes the microservice corresponding to the entry whose processing order C101 is 6 is changed. The above is the description of the process of step S209.

The service order control unit 211 updates the variable M with the variable N (step S211). After that, the service order control unit 211 proceeds to step S213.

In step S213, the service order control unit 211 determines whether or not all the microservices have been selected (step S213).

When it is determined that all the microservices are not selected, the service order control unit 211 sets the value obtained by adding 1 to the variable N in the variable N (step S219), and then returns to the step S203.

If it is determined that all the microservices have been selected, the service order control unit 211 proceeds to step S215.

The service order control unit 211 determines whether M is smaller than N (step S215). If M is not less than N, the service order control unit 211 ends the microservice placement optimization process.

When M is smaller than N, the service order control unit 211 performs the same processing as in S209 between M and N (step 217). After that, the microservice placement optimization process is terminated.

By the above processing, the combination of the processing system to be deployed and the microservice to be deployed is determined, and two or more microservices executed in the same processing system are executed in the same processing system to reduce the communication processing. Can be made to.

FIG. 9 is a flowchart illustrating a process of deploying a microservice (executable file) to the service processing server when the service processing server 111 of the first embodiment receives the received microservice optimum arrangement information. In particular, this process executes the microservice optimal placement process in the same data center when the microservice is executed in a plurality of different servers in the same data center.

The service order control unit 211 of the service processing server 111 receives the microservice optimum placement process created by the service order control unit 211 of the development platform server 110 (step S301).

The service order control unit 211 of the service processing server 111 determines whether or not the deployed microservice is executed by a plurality of servers in the same data center (step S303).

For example, the service order control unit 211 determines whether or not a plurality of entries exist in the processing management information T100. Further, the service order control unit 211 counts the number of deployed microservices and determines whether or not the number of microservices is two or more.

If it is determined that there is only one deployed microservice, the service order control unit 211 determines the service processing server 111 to deploy the microservice, and deploys the microservice to the determined service processing server 111 (. Step S307). The present invention is not limited to the method of determining the service processing server 111 for deploying the microservice. After that, the service order control unit 211 ends the process.

If it is determined in step S303 that there are a plurality of microservices executed in the same data center, the service order control unit 211 executes the microservice arrangement optimization process (step S305). The microservice arrangement optimization process is the same process as the process from step S203 to step S223. However, the difference is that the deployment destination is the server.

Next, the service order control unit 211 deploys the microservice to the determined service processing server 111 based on the processing result of the microservice arrangement optimization processing (step S307). After that, the service order control unit 211 ends the process.

FIG. 10 is a flowchart illustrating a process executed by the base server 110 of the first embodiment when providing a service.

When the service sequence control unit 211 of the base server 110 detects the execution trigger of the service, the service sequence control unit 211 starts the process described below. As a service execution trigger, it is conceivable that a service execution request is received from a user or the like, and that a certain period of time has elapsed.

The service order control unit 211 of the base server 110 refers to the processing system information C104 and the change processing system information C105 of the processing management information T100 to determine the order of the processing systems for transmitting the processing requests (step S401). At this time, the initial value "1" is set in the variable i representing the order of the processing system for transmitting the processing request.

Next, the service order control unit 211 of the base server 110 transmits the first processing request to the i-th processing system (step S403).

Specifically, the service order control unit 211 of the base server 110 transmits the first processing request including the input parameters and the execution order of the microservices to the i-th processing system. The service execution unit 212 of the processing system that has received the first processing request executes the deployed microservice according to the processing request.

When one microservice is deployed in the i-th processing system, the service order control unit 211 of the base server 110 transmits a second processing request to the processing system. The second processing request includes input parameters, but does not include the execution order of microservices.

The processing request may be transmitted as data in XML format or JSON format, for example, or may be transmitted as a parameter of HTTP communication.

When executing the distributed processing, the following processing is executed. When the processing request is received as XML format or JSON format data, the service execution unit 212 registers the data as a microservice setting file and executes the microservices in the designated order. When a processing request is received as a parameter of HTTP communication, the service execution unit 212 converts the parameter into XML format or JSON format data, registers the data as a microservice setting file, and microservices in the specified order. To execute.

Next, the service order control unit 211 of the base server 110 receives the processing result from the service execution unit 212 of the processing system that has transmitted the first processing request (step S405).

Next, the service order control unit 211 of the base server 110 determines whether or not all the microservices have been executed (step S407).

If it is determined that all the microservices have not been executed, the service order control unit 211 of the base server 110 adds 1 to the variable i (step S409), returns to step S403, and executes the same process.

When it is determined that all the microservices have been executed, the service order control unit 211 of the base server 110 outputs a response obtained from the processing results of the series of microservices (step S411), and ends the processing.

Here, a specific example of the processing of FIG. 10 when the microservice is deployed as shown in FIG. 1 will be described.

(1) First, the base server 110 receives a service execution request including the input A from the user. The service order control unit 211 of the infrastructure server 110 determines to transmit processing requests in the order of the infrastructure system 100, the data center 101-1, and the data center 101-2. The service order control unit 211 of the board server 110 transmits a first processing request to the board system 100. The service execution unit 212 of the base server 110 executes the process A160 and outputs the output A as the process result. The service execution unit 212 of the base server 110 transmits the output A to the service order control unit 211 of the base server 110.

(2) The service order control unit 211 of the base server 110 transmits the first processing request including the execution order of the output A and the microservices (processing B161, processing C162, processing D163) to the data center 101-1.

(3) The service execution unit 212 of the service processing server 111-1 executes the process B161 based on the output A to output the output B, executes the process C162 based on the output B, and outputs the output C. The process D163 is executed based on the output C, and the output D is output. The service processing server 111-1 transmits the output D to the service order control unit 211 of the base server 110.

(4) The service order control unit 211 of the base server 110 transmits a first processing request including the order of the output D and the microservices (processing E164, processing F165, processing Z166) to the data center 101-2.

(5) The service execution unit 212 of the service processing server 111-2 executes the process E164 based on the output D to output the output E, executes the process F165 based on the output E, and outputs the output F. Processing Z166 is executed based on the output F, and the output Z is output. The service execution unit 212 of the service processing server 111-2 transmits the output Z to the service order control unit 211 of the base server 110.

(6) The service order control unit 211 of the board server 110 outputs the output Z as a response to the user.

According to the first embodiment, the server (base server 110) that controls the service is the deployment destination of the microservice so that the data is not frequently transmitted and received between the processing systems (between the servers) in which the microservice is arranged. Determine the processing system. Further, the server that controls the service (base server 110) transmits a processing request including the execution order to the processing system when the service is executed. As a result, the transmission and reception of data between the processing systems associated with the execution of the service is reduced, so that the problems of the decrease in execution speed and the increase in the consumption of communication resources can be improved.

In the first embodiment, the microservice placement optimization process is executed for all the microservices constituting the service. In the second embodiment, the microservice placement optimization process is executed for some of the microservices constituting the service. To achieve this, limit the microservices to which the microservice placement optimization process is applied. Hereinafter, Example 2 will be described with a focus on the differences from Example 1.

The configuration of the computer system of the second embodiment is the same as that of the first embodiment. The configuration of the base server 110 and the service processing server 111 of the second embodiment is the same as that of the first embodiment. Further, the data structure of the information held by the infrastructure server 110 and the service processing server 111 of the second embodiment is the same as that of the first embodiment.

In the second embodiment, the microservices provided in the development platform 120 are partially different. FIG. 11 is a diagram showing an example of a GUI provided by the development infrastructure processing unit 210 of the second embodiment.

The batch process start node 157 and the batch process end node 158 are displayed on the palette 610 of the GUI 600 of the second embodiment in order to indicate the range to which the microservice arrangement optimization process is applied. The batch processing start node 157 is a node (microservice) indicating the start point of the microservice placement optimization processing, and the batch processing end node 158 is a node (microservice) indicating the end point of the microservice placement optimization processing. It is assumed that the batch processing start node 157 and the batch processing end node 158 are arranged on the base server 110.

In the example shown in FIG. 11, the processes B151 to F155 are the targets of the microservice arrangement optimization process.

12A and 12B are flowcharts illustrating the microservice arrangement optimization process executed by the base server 110 of the second embodiment.

After the processing in step S203, the service order control unit 211 of the base server 110 determines whether or not the node corresponding to the target microservice is the batch processing start node 157 (step S251).

When it is determined that the node corresponding to the target microservice is the batch processing start node 157, the service order control unit 211 of the base server 110 sets the batch processing flag to “ON” (step S253). After that, the service order control unit 211 of the board server 110 proceeds to step S259.

When it is determined that the node corresponding to the target microservice is not the batch processing start node 157, the service order control unit 211 of the base server 110 determines whether or not the node is the batch processing end node 158 (step S255). ).

When it is determined that the node corresponding to the target microservice is the batch processing end node 158, the service order control unit 211 of the base server 110 sets the batch processing flag to "OFF" (step S257). After that, the service order control unit 211 of the board server 110 proceeds to step S259.

If it is determined that the node corresponding to the target microservice is not the batch processing end node 158, the service order control unit 211 of the base server 110 proceeds to step S259.

In step S259, the service order control unit 211 of the base server 110 determines whether or not the batch processing flag is “ON” (step S259).

If it is determined that the batch processing flag is "ON", the service order control unit 211 of the base server 110 proceeds to step S205.

If it is determined that the batch processing flag is "OFF", the service order control unit 211 of the base server 110 proceeds to step S213.

FIG. 13 is a flowchart illustrating a process executed by the base server 110 of the second embodiment when the service is provided.

After the processing in step S401, the service order control unit 211 of the base server 110 determines whether or not the microservice executed by the i-th processing system is the batch processing start node 157 (step S421).

When it is determined that the microservice executed by the i-th processing system is the batch processing start node 157, the service order control unit 211 of the base server 110 sets the batch processing flag to "ON" (step S423). After that, the service order control unit 211 of the board server 110 proceeds to step S409.

When it is determined that the microservice executed by the i-th processing system is not the batch processing start node 157, the service order control unit 211 of the base server 110 determines whether or not the microservice is the batch processing end node 158. (Step S425).

When it is determined that the microservice executed by the i-th processing system is the batch processing end node 158, the service order control unit 211 of the base server 110 sets the batch processing flag to "OFF" (step S427). After that, the service order control unit 211 of the board server 110 proceeds to step S409.

When it is determined that the microservice executed by the i-th processing system is not the batch processing end node 158, the service order control unit 211 of the base server 110 determines whether or not the batch flag is "ON" (step). S429).

If it is determined that the batch flag is "ON", the service order control unit 211 of the base server 110 proceeds to step S403.

When it is determined that the batch flag is "OFF", the service order control unit 211 of the base server 110 transmits a second processing request to the i-th processing system (step S431). The second processing request does not include the execution order of the microservices. After that, the service order control unit 211 of the board server 110 proceeds to step S405. When the service execution unit 212 receives the second processing request, the service execution unit 212 executes the process corresponding to the node and then responds with the processing result.

The process to be executed when the service processing server 111 receives the deployed microservice (executable file) is the same as that in the first embodiment.

According to the second embodiment, the same effect as that of the first embodiment can be obtained, and the load on the server (base server 110) that controls the service can be reduced. Even if the batch processing start node 157 and the batch processing end node 158 are arranged in different computer systems, if the computer system is a movable microservice, all the microservices to be batch processed are arranged in the same computer system. It may be possible to perform batch processing.

In the third embodiment, the processing at the time of transmitting the processing request is different. Hereinafter, Example 3 will be described with a focus on the differences from Example 1.

The configuration of the computer system of the third embodiment is the same as that of the first embodiment. The configuration of the base server 110 and the service processing server 111 of the third embodiment is the same as that of the first embodiment. Further, the data structure of the information held by the infrastructure server 110 and the service processing server 111 of the third embodiment is the same as that of the first embodiment.

The microservice allocation optimization process and the process executed when the service process server 111 accepts the deployed node (executable file) are the same as those in the first embodiment.

The flow of processing executed by the base server 110 when the service is provided is the same as that of the first embodiment. However, the process of step S403 is different.

FIG. 14 is a flowchart illustrating a process to be executed when the base server 110 of the third embodiment transmits a process request. The process described below is the process executed in step S403.

The service order control unit 211 of the base server 110 analyzes the microservice (step S501), and determines whether or not other microservices are included in the iterative processing included in the microservice based on the analysis result. (Step S503).

For example, the service order control unit 211 determines whether or not the for statement contains a code instructing the execution of another microservice.

The microservice analysis may be executed in the microservice placement optimization process. In this case, a field for storing information related to repetitive processing is added to the processing management information T100. In step S201, the service order control unit 211 of the base server 110 stores the analysis result of the source code in the field.

When it is determined that the iterative processing included in the microservice does not include other microservices, the service order control unit 211 of the base server 110 transmits the first processing request to the i-th processing system (step). S505). After that, the service order control unit 211 of the board server 110 proceeds to step S405. The process of step S505 is the same as the process of step S403.

When it is determined that other microservices are included in the iterative processing included in the microservice, the service order control unit 211 of the base server 110 includes information for changing the iterative processing to asynchronous communication processing. The processing request is transmitted to the i-th processing system (step S507). After that, the service order control unit 211 of the board server 110 proceeds to step S405.

Specifically, the service order control unit 211 of the base server 110 transmits a third processing request including input parameters and execution order of microservices, names of other microservices included in the iterative processing, and the number of iterations. ..

When the service execution unit 212 of the service processing server 111 receives the processing request, it issues a job ID and responds with the job ID issued to the service order control unit 211 of the base server 110. After that, the service execution unit 212 of the service processing server 111 executes the iterative processing.

The service order control unit 211 of the base server 110 makes an inquiry to grasp the progress status of the iterative process using the job ID. When the service execution unit 212 of the service processing server 111 receives a progress inquiry for the job ID, it responds with a value indicating the current progress.

According to the third embodiment, it is possible to reduce the transmission and reception of data between the processing systems in which the microservices frequently executed by the iterative processing are arranged.

In the fourth embodiment, the process executed by the base server 110 when the service is provided is different from that of the first embodiment. Hereinafter, Example 4 will be described with a focus on the differences from Example 1.

The configuration of the computer system of the fourth embodiment is the same as that of the first embodiment. The configuration of the base server 110 and the service processing server 111 of the fourth embodiment is the same as that of the first embodiment. Further, the data structure of the information held by the infrastructure server 110 and the service processing server 111 of the fourth embodiment is the same as that of the first embodiment.

The microservice allocation optimization process and the process executed when the service processing server 111 receives the deployed microservice (executable file) are the same as those in the first embodiment.

FIG. 15 is a flowchart illustrating a process executed by the base server 110 of the fourth embodiment when providing a service.

After the processing in step S401, the service order control unit 211 of the base server 110 refers to the service control system information T110 and determines whether the offload flag C112 of the entry corresponding to the i-th processing system is "possible". (Step S441).

If it is determined that the offload flag C112 of the entry corresponding to the i-th processing system is not "OK", the service order control unit 211 of the base server 110 proceeds to step S403.

When the offload flag C112 of the entry corresponding to the i-th processing system is determined to be "OK", the service sequence control unit 211 of the base server 110 transmits the fourth processing request to the i-th processing system. (Step S443).

Specifically, the service order control unit 211 of the base server 110 determines the execution order of the microservices deployed in all the i-th and subsequent processing systems. The service order control unit 211 of the base server 110 transmits a fourth processing request including information associated with the execution order of the processing system and the microservice and an input parameter to be input to the i-th processing system.

When the service sequence control unit 211 of the i-th and subsequent processing systems receives the fourth processing request, the service execution unit 212 instructs the service execution unit 212 to execute the microservice deployed on the local server. Further, the service order control unit 211 of the i-th and subsequent processing systems executes the same processing as the processing shown in FIG. However, in step S401, (i + 1) is set in the variable i instead of determining the order of the servers. Further, the service order control unit 211 of the processing system that has received the fourth processing request directly from the base server 110 transmits the processing result of the microservice obtained from the i-th and subsequent processing systems to the base server 110.

Next, the service order control unit 211 of the base server 110 receives the processing result from the server that transmitted the fourth processing request (step S445). After that, the service order control unit 211 of the board server 110 proceeds to step S411.

A specific example of the processing of FIG. 15 when the microservice is deployed as shown in FIG. 1 will be described.

(1) First, the base server 110 receives a service execution request including the input A from the user. The service order control unit 211 of the infrastructure server 110 determines to transmit processing requests in the order of the infrastructure system 100, the data center 101-1, and the data center 101-2. The service order control unit 211 of the base server 110 transmits a first processing request to the base server 110. The service execution unit 212 of the base server 110 executes the process A160 and outputs the output A as the process result. The service execution unit 212 of the base server 110 transmits the output A to the service order control unit 211 of the base server 110.

(2) The service order control unit 211 of the base server 110 includes information corresponding to the execution order of the service processing server 111-1 and the microservices (processing B161, processing C162, processing D163), the service processing server 111-2, and the micro. The information associated with the execution order of the services (process E164, process F165, process Z166) and the fourth process request including the output A are transmitted to the service process server 111-1.

(3) The service execution unit 212 of the service processing server 111-1 executes the process B161 based on the output A to output the output B, executes the process C162 based on the output B, and outputs the output C. The process D163 is executed based on the output C, and the output D is output. The service order control unit 211 of the service processing server 111-1 includes information corresponding to the execution order of the service processing server 111-2 and the microservices (process E164, process F165, process Z166), and the first process including the output D. Send the request.

(4) The service execution unit 212 of the service processing server 111-2 executes the process E164 based on the output D to output the output E, executes the process F165 based on the output E, and outputs the output F. Processing Z166 is executed based on the output F, and the output Z is output. The service execution unit 212 of the service processing server 111-2 transmits the output Z to the service processing server 111-1.

(5) The service order control unit 211 of the service processing server 111-1 transmits the output Z to the base server 110. The service order control unit 211 of the service processing server 111-1 may generate one output from the processing results of the microservices deployed on the service processing server 111-1 and the service processing server 111-2.

(6) The service order control unit 211 of the board server 110 outputs the output Z as a response to the user.

According to the fourth embodiment, since it is not necessary to communicate with the base server 110 every time the processing system executes the microservice, the execution speed of the service can be further improved, and the consumption of the communication resource can be further reduced.

The unit of the node (microservice) to be provided differs depending on the use case and requirements or the skill of the developer. This means that the units of API to be provided are different, and it comes down to the problem of how much processing should be executed by one microservice.

Therefore, it is conceivable to decompose services into small units of microservices (small-scale processing) and combine small-unit microservices to provide appropriate microservices (medium-scale or large-scale processing). However, in a service composed of small units of microservices, communication between microservices frequently occurs, so that there are problems that the execution speed of the service is slowed down and the consumption of network resources is increased.

Therefore, the above-mentioned problems can be solved by using the inventions shown in Examples 1 to 4.

In the fifth embodiment, after the microservice arrangement optimization process is completed, the service order control unit 211 generates a microservice in which a plurality of microservices are combined based on the result of the process. For example, the service sequence control unit 211 creates a combination of microservices in which communication between processing systems does not occur as a new microservice. Further, the development infrastructure processing unit 210 displays the newly generated microservice on the GUI 600 when the service is generated.

In a service composed of microservices combining a plurality of microservices, the microservice placement optimization process and the microservice are executed in consideration of the minimum microservice. Specifically, it is a process for a small unit microservice (node) constituting one microservice (node).

FIG. 16 is a diagram showing an example of the portal 1600 presented by the development infrastructure processing unit 210 of the fifth embodiment.

The portal 1600 is a GUI for searching the API desired by the user (developer). The portal 1600 includes a keyword input field 1610 and a search result display field 1620.

The keyword input field 1610 is a field for inputting a keyword used for API search. The search result display field 1620 is a field for displaying search results. In the search result display field 1620, for example, information on the processing server that provides the API is displayed.

The user drags and drops the processing server onto the development platform 120, or downloads JSON representing a microservice to the development platform 120. This makes it possible to use the API on the development platform 120.

Processes B-C1611 and DF1612 are microservices that combine a plurality of processes.

The development infrastructure processing unit 210 may display the portal 1600 after executing the user authentication process. Further, the development infrastructure processing unit 210 may have different searchable microservices for each user.

17A, 17B, and 17C are diagrams showing an example of the GUI provided by the development infrastructure processing unit 210 of the fifth embodiment.

In the workspace 620 of the GUI 600, the processes B-C 1611 and the processes D-F 1612 corresponding to the microservices searched by using the portal 1600 are displayed.

In the GUI 600 shown in FIG. 17A, when the process B-C1611 displayed in the workspace 620 is double-clicked, the workspace 620 switches to the display as shown in FIG. 17B.

Further, a GUI 600 as shown in FIG. 17C is also conceivable. In the GUI 600 of FIG. 17C, the workspace 620 includes tabs. In FIG. 17C, the whole tab and the detail tab are included.

When the user operates the whole tab, the workspace 620 displays the flow of microservices constituting the service as shown in the workspace 620 of the GUI 600 of FIG. 17A. When the user operates the details tab, the workspace 620 of the GUI 600 in FIG. 17C contains detailed node configurations of the processes BC1611 and the processes DF1612, which are microservices composed of a plurality of microservices. Is displayed. A tab may be provided for each microservice.

According to the fifth embodiment, the optimum microservice can be generated for each user based on the deployment result of the smallest unit microservice.

The present invention is not limited to the above-described embodiment, and includes various modifications. Further, for example, the above-described embodiment describes the configuration in detail in order to explain the present invention in an easy-to-understand manner, and is not necessarily limited to the one including all the described configurations. Further, it is possible to add, delete, or replace a part of the configuration of each embodiment with other configurations.

Further, each of the above configurations, functions, processing units, processing means and the like may be realized by hardware by designing a part or all of them by, for example, an integrated circuit. The present invention can also be realized by a software program code that realizes the functions of the examples. In this case, a storage medium in which the program code is recorded is provided to the computer, and the processor included in the computer reads out the program code stored in the storage medium. In this case, the program code itself read from the storage medium realizes the function of the above-described embodiment, and the program code itself and the storage medium storing it constitute the present invention. Examples of the storage medium for supplying such a program code include a flexible disk, a CD-ROM, a DVD-ROM, a hard disk, an SSD (Solid State Drive), an optical disk, a magneto-optical disk, a CD-R, and a magnetic tape. Non-volatile memory cards, ROMs, etc. are used.

In addition, the program code that realizes the functions described in this embodiment can be implemented in a wide range of programs or script languages such as assembler, C / C ++, perl, Shell, PHP, and Java (registered trademark).

Further, by distributing the program code of the software that realizes the functions of the embodiment via the network, the program code is stored in a storage means such as a hard disk or a memory of a computer or a storage medium such as a CD-RW or a CD-R. The processor included in the computer may read and execute the program code stored in the storage means or the storage medium.

In the above-described embodiment, the control lines and information lines show what is considered necessary for explanation, and do not necessarily indicate all the control lines and information lines in the product. All configurations may be interconnected.

100 Infrastructure system 101 Data center 102 Network 110 Infrastructure server 111 Service processing server 120 Development infrastructure 120 Infrastructure server 120 Development environment 121 Execution infrastructure T100 Processing management information T110 Service control system information 200, 300 CPU
201, 301 Memory 202, 302 Storage device 203, 303 Network interface 204, 304 Internal bus 600 GUI
610 Palette 620 Workspace 630 Console 640 Deploy button 1600 Portal 1610 Keyword input field 1620 Search result display field

Claims (10)

A system that provides services consisting of multiple microservices.
Including multiple computer systems capable of performing the microservices
The plurality of computer systems include a plurality of computers, and have a service order control unit that controls the execution order of the plurality of microservices.
The service order control unit acquires information on a plurality of execution microservices for providing the first service, their execution orders, and arrangement conditions of the plurality of execution microservices, satisfies the arrangement conditions, and An execution computer system for executing the plurality of execution microservices is determined so that communication during execution of the plurality of execution microservices is reduced, and the execution order of the plurality of execution microservices and the plurality of execution computer systems are determined. Generates processing management information including, and sends it to the plurality of execution computer systems.
When the execution computer system that has received the processing management information has a plurality of the execution microservices executed by the execution computer system, the execution computer system satisfies the arrangement condition and the communication at the time of execution of the plurality of execution microservices is performed. To reduce the number of execution microservices, a computer is determined to execute the plurality of execution microservices, and based on the determination, the deployment of the plurality of execution microservices to the computer is executed.
When the service sequence control unit detects the execution trigger of the first service, the service sequence control unit selects one execution computer system based on the processing management information, and the execution micro is executed by the selected execution computer system. Send an execution request including the execution order of the service,
The execution computer system for executing a plurality of the execution microservices is a system characterized in that data indicating a processing result is transmitted after executing all of the plurality of execution microservices . The system according to claim 1.
The service order control unit is a system characterized in that the execution computer system is determined so that batch processing for collectively processing a plurality of microservices can be performed. The system according to claim 1.
When the plurality of execution microservices having a continuous execution order include a repetitive process of repeatedly processing the execution microservice, the service order control unit changes the communication of the process to asynchronous communication.
The execution computer system that performs the iterative process is a system that executes the iterative process and, when an inquiry is received from the service order control unit, performs a response related to the iterative process. The system according to claim 1.
The service order control unit is a system characterized in that it receives data indicating the processing result from the plurality of execution computer systems and outputs data relating to the first service. The system according to claim 1.
The service order control unit is a system characterized in that the execution computer system transmits data indicating the processing result to the execution computer system to be selected next. A service control method executed by a system that provides a service consisting of multiple microservices.
The system includes a plurality of computer systems capable of performing the microservices.
The plurality of computer systems include a plurality of computers, and have a service order control unit that controls the execution order of the plurality of microservices.
The service control method is
The service order control unit acquires information on a plurality of execution microservices for providing the first service, their execution order, and arrangement conditions of the plurality of execution microservices, satisfies the arrangement conditions, and An execution computer system for executing the plurality of execution microservices is determined so that communication during execution of the plurality of execution microservices is reduced, and the execution order of the plurality of execution microservices and the plurality of execution computer systems are determined. The first step of generating the processing management information to be included and transmitting it to the plurality of execution computer systems, and
When the execution computer system that has received the processing management information has a plurality of the execution microservices executed by the execution computer system, the execution computer system satisfies the arrangement condition and the communication at the time of execution of the plurality of execution microservices is performed. A second step of determining the computer to execute the plurality of execution microservices so as to be less, and executing the deployment of the plurality of execution microservices to the computer based on the determination.
When the service order control unit detects the execution trigger of the first service, the execution computer system is selected based on the processing management information, and the execution micro is executed by the selected execution computer system. The third step of sending an execution request, including the execution order of the services,
A service control comprising the fourth step of transmitting data indicating a processing result after the execution computer system executing the plurality of execution microservices has executed all of the plurality of execution microservices. Method. The service control method according to claim 6.
The first step is a service control method including a step of determining the execution computer system so that the service order control unit can perform batch processing for batch processing a plurality of microservices. The service control method according to claim 6.
In the first step, when the service order control unit includes a repetitive process of repeatedly processing the execution microservices in the plurality of execution microservices having a continuous execution order, the communication of the processes is asynchronous. Including the step to change to communication
The service control method is characterized by including a step of performing a response related to the iterative process when the execution computer system performing the iterative process executes the iterative process and receives an inquiry from the service order control unit. Service control method. The service control method according to claim 6.
The third step is a service control method comprising a step in which the service order control unit receives data indicating the processing result from the plurality of execution computer systems and outputs data relating to the first service. .. The service control method according to claim 6.
The third step is a service control including a step in which the service sequence control unit causes the execution computer system to transmit data indicating the processing result to the execution computer system to be selected next. Method.

Images