KR102337962B1 - System and method for executing application based on microservice architecture and computer program for the same - Google Patents

Abstract

A microservice architecture (MSA) application execution system includes: a computing device configured to send, in response to a service request of a user, a service and resource request to a storage server; and a storage server configured to store service information and resource information associated with one or more services of a microservices architecture application, and provide the service information and the resource information in response to the service and resource request. The computing device is further configured to perform the service of the application corresponding to the service request by using the service information and the resource information received from the storage server. When the MSA application execution system is used, all class and resource information is stored in a storage server, and the necessary information is received and used at the execution time for each container, thereby creating a monolithic architecture. There is an advantage of being able to provide services developed based on MSA in the form of MSA.

Description

SYSTEM AND METHOD FOR EXECUTING APPLICATION BASED ON MICROSERVICE ARCHITECTURE AND COMPUTER PROGRAM FOR THE SAME

Embodiments relate to a microservice architecture (MSA) application execution system and method, and a computer program therefor. More specifically, the embodiments store all class and resource information in an external server and receive and use the class and resource information required at the execution time for each container, thereby providing a monolithic architecture (monolithic architecture). architecture) based on the service developed in the form of MSA.

Monolithic architecture refers to the existing traditional application development form, and refers to a service form that includes all components related to all functions of the application and logic for processing them in one packaging file. do. An application based on a monolithic architecture has a structure in which each component calls each other using a function.

According to the monolithic architecture, since the entire application is processed as one, there is an advantage in that application development, deployment, and testing on a development framework are easy. On the other hand, when developing a large-scale application with a monolithic structure, it is necessary to understand the structure of the entire system during development, because performance problems or failures in a specific component or module affect other components. And it takes a long time for distribution and startup of a server to run an application, and there is the inconvenience of having to redistribute the entire application even if a specific component is modified.

As large-capacity web services increase, a microservice architecture (MSA) has been defined to overcome the shortcomings of the existing monolithic architecture. In MSA, each component is implemented in the form of a service, and is configured to communicate with other services using an application programming interface (API). For example, Korean Patent Publication No. 10-2027749 discloses a microservice system and method that provides a control and management function for communication occurring between each service of the MSA.

However, when the service developed based on the monolithic architecture is executed in the form of an MSA, it is impossible to check the information about the dependency relationship between services or the resource called by each service, so conventionally all information is stored in each server We used an alternative to save and run any service on each server. However, in this case, the advantage as an MSA disappears and there is a limitation in that it is a configuration that simply increases the number of servers.

Registered Patent Publication No. 10-2027749

According to one aspect of the present invention, by storing all class and resource information in an external storage server and receiving and using the class and resource information required at the execution time for each container, monolithic architecture It is possible to provide an MSA application execution system and method capable of providing a service developed based on a monolithic architecture in the form of an MSA, and a computer program for the same.

MicroService Architecture (MSA) application execution system according to an aspect of the present invention, in response to a service request of a user, a computing device configured to transmit a service and resource (resource) request to a storage server; and a storage server configured to store service information and resource information associated with one or more services of a microservices architecture application, and provide the service information and the resource information in response to the service and resource request. The computing device is further configured to perform the service of the application corresponding to the service request by using the service information and the resource information received from the storage server.

In an embodiment, the computing device is further configured to retrieve the service information and the resource information from an internal storage of the computing device before sending the service and resource request to the storage server.

In one embodiment, the computing device is further configured to provide a development framework configured to constitute one or more containers of the application and to transmit the service information and the resource information to the storage server.

A storage server for a microservices architecture application operation according to an aspect of the present invention includes: a storage unit configured to store service information and resource information for service execution of the microservices architecture application; and an information return unit configured to receive a service and resource request for executing the service from a computing device, and provide the service information and the resource information to the computing device in response to the service and resource request.

A microservices architecture application execution method according to an aspect of the present invention comprises the steps of: storing service information and resource information for service execution of a microservices architecture application in a storage server; receiving, by the storage server, a service and resource request for service execution of the application from a computing device; and providing, by the storage server, the service information and the resource information to the computing device in response to the service and resource request.

The method of executing a microservices architecture application according to an embodiment further includes, before receiving the service and resource request, the computing device retrieving the service information and the resource information from an internal storage of the computing device.

The microservices architecture application execution method according to an embodiment includes, by the computing device, performing a service of the application corresponding to a service request of a user by using the service information and the resource information received from the storage server include more

The computer program according to an aspect of the present invention is combined with hardware to execute the microservices architecture application execution method according to the embodiments, and may be stored in a computer-readable recording medium.

According to the microservice architecture (MSA) application execution system and method according to an aspect of the present invention, all information required for service operation of the existing monolithic architecture method is stored in an external server, and a container ( container), configure the service using a custom class loader, etc. and control access to resources through BCI (Byte Code Insertion), etc. It has the advantage of being able to serve as

1 is a schematic block diagram of a development framework for the development of a microservice architecture (MSA) application according to an embodiment.
FIG. 2 is a flowchart illustrating a container distribution process using the development framework shown in FIG. 1 .
3 is a flowchart illustrating an execution process of an MSA container by an MSA application execution system according to an exemplary embodiment.
4 is a schematic block diagram of a storage server of an MSA application execution system according to an embodiment.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

1 is a schematic block diagram of a development framework for the development of a microservice architecture (MSA) application according to an embodiment.

Embodiments of the present invention relate to a system configured to execute an application having an MSA service type using a container. In the present specification, the MSA container collectively refers to a computing device that executes one or more services of an MSA-based application and provides a result of the execution to a user and a software driving means thereof. For example, MSA-based applications provide services by loading images from Docker running on a virtualization server and executing them, and MSA containers conceptually refer to computing devices such as virtualization servers and software means executed by them. .

The MSA container is executed by a virtualization server, and in the following specification, it is assumed that the development framework providing system 3 communicating with the developer's user device 1 performs the function of the virtualization server according to the embodiments. Describes the MSA application execution system. However, the virtualization server for the MSA application may be executed by the user device 1 or any other computing device. Accordingly, the computing device in the claims set out below is intended to refer to the user device 1 of FIG. 1 , the development framework providing system 3 or any virtualization server not shown in the figure but configured to run an MSA container, It is not limited to a specific device or system.

Referring to FIG. 1 , the development framework providing system 3 is configured to be able to communicate with the user device 1 and/or the external storage server 2 , so that the developer of the application uses the user device 1 . It plays a role of creating a monolithic architecture or MSA container using the source information input through the

The devices described herein may be wholly hardware, or may have aspects that are partly hardware and partly software. For example, the development framework providing system 3 according to the embodiments and each system, device, server and each unit included therein communicating therewith transmit and receive data in a specific format and content in an electronic communication method A device for and related software may be collectively referred to. As used herein, terms such as “unit”, “module”, “server”, “system”, “platform”, “device” or “terminal” refer to a combination of hardware and software driven by the hardware. it is intended to For example, the hardware herein may be a data processing device including a CPU or other processor. In addition, software driven by hardware may refer to a running process, an object, an executable file, a thread of execution, a program, and the like.

The user device 1 is a device for use by a developer who wants to develop an application using the development framework providing system 3 . Although the user device 1 is illustrated in the form of a notebook computer in FIG. 1 , this is an example, and the user device 1 is a mobile communication terminal such as a smartphone, a personal computer, and a personal digital assistant (PDA). ), a tablet computer, a set-top box for IPTV (Internet Protocol Television), etc. may be implemented in the form of any computing device.

In the development framework providing system 3, the developer inputs source information to the development framework providing system 3 and input information such as the architecture type of the application to be developed, so that a container for the operation of the application can be created. It functions as a platform that allows

For example, the development framework providing system 3 is a web server that provides a user interface such as a management screen to be displayed on the user device 1 connected to the development framework providing system 3 . server) or may be implemented in the form of an application service server (application service server), but is not limited thereto.

In Figure 1, for convenience of explanation, the user device 1 and the development framework providing system 3, which are devices used by developers, are shown as separate devices, and the embodiments of the present specification are the development framework providing system 3 It is assumed that the user device 1 and the user device 1 are separate devices. However, this is exemplary, and in another embodiment, the development framework providing system 3 itself may be implemented in the form of a developer's user device.

In an embodiment, the development framework providing system 3 includes a storage unit 30 , an input/output unit 31 , a source analysis unit 33 , and a container configuration unit 34 . In an embodiment, the development framework providing system 3 may further include a compile unit 32 . Also, in one embodiment, the development framework providing system 3 may further include a transmitter 35 .

In the present specification, each part constituting the development framework providing system 3 is not necessarily intended to refer to physically separate separate components. That is, each part 30-35 constituting the development framework providing system 3 in FIG. 1 is shown as a separate block that is distinguished from each other, but this is the operation performed by the development framework providing system 3 functionally separated by According to an embodiment, some or all of the above-described units may be integrated in the same single device, or one or more units may be implemented as separate devices physically separated from other units. For example, each part 30-35 of the development framework providing system 3 may be components communicatively connected to each other in a distributed computing environment.

The input/output unit 31 is a part for receiving a developer's input through the user device 1 and providing a corresponding processing result to the user device 1 . That is, the input/output unit 31 may receive the source information of the application from the developer. In the following specification, the source information is described by taking the source code of the application based on the Java language as an example. However, the type of programming language that can be used in the development framework providing system 3 according to the embodiments is not limited thereto.

In addition, the input/output unit 31 may receive a container creation request related to the application from the developer, and in this case, the container creation request may include input information on the architectural form of the application.

The compilation unit 32 is a part for converting the source information input by the developer into a form executable by the computing device (eg, a binary file or an intermediate language file, etc.). Since this can be easily understood by a person skilled in the art from a conventional compiler, a detailed description will be omitted.

The source analysis unit 33 analyzes the source information converted by the compilation unit 32 and serves to generate relationship information related to a call relationship between one or more services included in the application. The operation of the source analysis unit 33 can be easily understood from known software tools such as doxygen that generates a document through comments on the code or graphviz that converts a function call in the source code into a graph. can

In embodiments of the present invention, an application may include one or more services, and source information is configured such that each service prohibits direct calls to each other except for a common library. That is, the call between each service of the application is configured to be made in a URL (Uniform Resource Locator) call method using a predefined input/output domain. It allows a call relationship to be created as relationship information.

The source analysis unit 33 may store the generated relationship information in the storage unit 30 . In addition, when a change occurs in the call relationship by the developer modifying the existing source information, the source analyzer 33 may update the relationship information pre-stored in the storage unit 30 using the newly created relationship information. . In this case, the relationship information may include package information defining service information and resource information such as a class and a jsp file required for the operation of the corresponding service in relation to each service of the application.

The container configuration unit 34 serves to configure a container based on relationship information stored in the storage unit 20 in response to a container creation request for a specific service or previously generated specific package information from a developer. In this case, the container runs in an environment isolated from the operating system of the computing device, and performs functions such as creating and returning a response to the request by creating an object corresponding to the request and calling a function using it as an argument, for example, This includes Docker and the like.

In this specification, configuring a container by the container configuration unit 34 may mean creating a new container or transmitting information to an existing container based on package information and relationship information. At this time, service information and resource information for service operation are extracted based on the relationship information and automatically included in the container.

When the container configured by the container configuration unit 34 is an MSA container, the transmitter 35 stores service information and resource information in the external storage server 2 to load it when the container is executed. plays a role For example, the service information may include a class file, a jsp file, and the like, and the resource information may include files such as txt and xml required for the operation of the service. The operation of the transmitter 35 and the storage server 2 will be described later in detail with reference to FIGS. 4 and 5 .

2 is a flowchart illustrating a container distribution process using a system for providing a development framework according to an embodiment. For convenience of description, a container distribution process will be described with reference to FIGS. 1 and 2 .

Referring to FIG. 2 , when the developer commits source information to the development framework providing system 3 using the user device 1 ( S21 ), the compilation unit 32 of the development framework providing system 3 . ) may compile it into a class file or the like (S22). When an error such as a grammar error occurs during compilation, the compilation unit 32 may transmit error information to the developer's user device 1 ( S23 ).

The source analysis unit 33 of the development framework providing system 3 may analyze the source information at the same time or after the compilation of the source information is made to generate relationship information indicating a call relationship between services (S24). ). This may mean generating package information that identifies other services called by the corresponding service for one or more services included in the application, and defines service information and resource information necessary for the operation of the corresponding service and the called services. . Also, in this specification, a service refers to a collective unit (eg, user management, bulletin board, etc.) of functions performed through an application.

If an error is detected during source analysis, the source analyzer 33 may transmit verification error information to the user device 1 so that the developer knows that the error has occurred (S25). In this case, the verification error refers to a case in which it is at least partially impossible to create a call relationship between services, such as other services called by a specific service do not exist, or a package or class called by a specific service does not exist.

When the relationship information is generated, the source analysis unit 33 may store the relationship information in the storage unit 30 of the development framework providing system 3 (S26). On the other hand, in the storage unit 30 of the development framework providing system 3, in addition to the relationship information, the source information itself committed by the developer or the compiled file, service information, resource information, etc. previously generated in relation to the application are stored. it may have been

In one embodiment, the transmitting unit 35 of the development framework providing system 3 transmits service information and resource information related to the application developed through the development framework providing system 3 to the storage server 2 and transmits these The information may be stored in the storage server 2 (S27).

Meanwhile, the developer may input management information defining the service type of the application he/she develops into the development framework providing system 3 ( S28 ). This may mean defining the service type of the application as monolithic architecture or MSA through the management screen provided by the development framework providing system 3 . Although the step of inputting management information ( S28 ) is shown as a separate step for convenience of description in the drawings, the designation of the service type of the application may be performed simultaneously with the commit of the source information according to an embodiment.

When a service type is input from the developer, the container configuration unit 34 of the development framework providing system 3 may configure the container using the relationship information stored in the storage unit 30 (S29). For example, when the service type is monolithic architecture, the container configuration unit 34 configures the container so that all information necessary for the operation of the application, for example, common library, service information, and resource information, etc. are included in one container. can This may mean creating a new container or deploying information to an existing container.

Alternatively, when the service type is MSA, the container configuration unit 34 may configure the container so that other services called by each service and information for their operation are included in one container. For example, when class information related to a specific service is updated, the container configuration unit 34 identifies containers corresponding to other services calling the service whose class information is updated from the package information of the relationship information, and the package information Based on this, information can be distributed to each container related to other services that call the service.

In one embodiment, the input/output unit 31 of the development framework providing system 3 may be further configured to transmit the processing result for the container configuration to the user device 1 of the developer ( S30 ).

According to the embodiment described above with reference to FIGS. 1 and 2, when a developer develops an application, there is no need to specify a service type as either monolithic or MSA, and if the desired architecture is specified through the management screen, the development frame The work providing system 3 automatically configures a monolithic container or MSA container based on the call relationship between services. Therefore, it is easy to change the service type, and even a developer who is not familiar with MSA type service development has the advantage of enabling MSA service development.

3 is a flowchart illustrating an execution process of an MSA container by the MSA application execution system according to an embodiment, and FIG. 4 is a schematic block diagram of a storage server of the MSA application execution system according to an embodiment.

3 and 4 , a user who wants to execute an MSA-based application may request a service from the MSA container 4 using the user device 1 ( S41 ). In this case, the MSA container 4 collectively refers to a computing device such as a virtualization server that executes one or more services of an MSA-based application and provides the execution result to a user and a software driving means thereof. For example, the user device 1 or the development framework providing system 3 of FIG. 1 , or a virtualization server not shown in the figure may constitute an MSA application execution system together with the storage server 2 as such a computing device. have.

The MSA container 4 requests service information (eg, class file, jsp file) and resource information (eg, txt, xml file, etc.) necessary for the operation of the requested service to the storage server 2 (S43), and stores it The server 2 may return requested service and resource information to the MSA container 4 (S44). For the above operation, as shown in FIG. 4 , the storage server 2 includes a storage unit 21 in which service and resource information for a service operation of the MSA container 4 are stored, and a request for the MSA container 4 . It may include an information return unit 22 that returns the requested information as a response.

In one embodiment, the MSA container 4 retrieves the necessary information from the internal storage (ie, internal cache) of the MSA container 4 before requesting the information from the storage server 2, and if the information is not retrieved It may be configured to request service information and resource information only necessary for the storage server 2 .

The MSA container 4 may receive service information and resource information from the information return unit 22 of the storage server 2 , and use the received service information to perform a service requested by the user ( S45 ). Also, the MSA container 4 may transmit a result of performing a service requested by the user to the user device 1 (S46).

For the above operation, the MSA container 4 may be configured to perform a service using a custom classloader that operates using service information received from the outside. In addition, the MSA container 4 utilizes external resource information in a class file compiled into byte code to perform a service, so that resource information in a manner such as Byte Code Insertion (BCI) may be configured to receive input and generate a response based on it.

According to this embodiment, when the service provided in the existing monolithic form is implemented in the MSA form, it is not necessary to store all information in the virtualization server in which each MSA container is executed, and all information for the existing monolithic service is stored. There is an advantage that each MSA container can fetch the necessary information from the server 2 and perform the service.

The operation by the MSA application execution method according to the embodiments described above may be implemented at least partially as a computer program and recorded in a computer-readable recording medium. A computer-readable recording medium in which a program for implementing the operation according to the method according to the embodiments is recorded includes all types of recording devices in which computer-readable data is stored. Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, and optical data storage device. In addition, the computer-readable recording medium may be distributed in a network-connected computer system, and the computer-readable code may be stored and executed in a distributed manner. In addition, functional programs, codes, and code segments for implementing the present embodiment may be easily understood by those skilled in the art to which the present embodiment belongs.

In addition, each block or each step shown in the flowcharts herein may represent a module, segment, or portion of code that includes one or more executable instructions for executing the specified logical function(s). It is also possible for the functions recited in blocks or steps to occur out of order in some alternative embodiments. For example, it is possible that two blocks or steps shown one after another may in fact be performed substantially simultaneously, or that the blocks or steps may sometimes be performed in the reverse order according to the corresponding function.

Although the present invention as described above has been described with reference to the embodiments shown in the drawings, it will be understood that these are merely exemplary, and that various modifications and variations of the embodiments are possible therefrom by those of ordinary skill in the art. However, such modifications should be considered to be within the technical protection scope of the present invention. Accordingly, the true technical protection scope of the present invention should be defined by the technical spirit of the appended claims.

Claims (8)

a computing device configured to send, in response to a user's service request for a microservices architecture application running using the one or more microservices architecture containers, service and resource requests to the storage server; and
a storage server configured to store service information and resource information associated with one or more services of the microservices architecture application, and in response to the service and resource request, provide the service information and the resource information to the microservices architecture container; including,
The computing device is further configured to perform the service of the application corresponding to the service request by using the service information and the resource information received from the storage server,
The service information includes a class file compiled into byte code,
The microservices architecture container comprises:
The service is performed using a custom class loader that operates using the service information received from the outside,
A microservices architecture application execution system, configured to receive the resource information into the class file in a bytecode insertion manner and generate a response corresponding to the service of the application.
The method of claim 1,
The computing device is further configured to retrieve the service information and the resource information from an internal storage of the computing device before sending the service and resource request to the storage server.
The method of claim 1,
The computing device is further configured to provide a development framework that constitutes one or more containers of the application and is configured to transmit the service information and the resource information to the storage server.
delete storing service information and resource information for service execution of a microservice architecture application in a storage server;
receiving, by the computing device, a service request from a user for a microservices architecture application that is executed using one or more microservices architecture containers;
receiving, by the storage server, a service and resource request for service execution of the application from the computing device;
providing, by the storage server, the service information and the resource information to the microservice architecture container in response to the service and resource request; and
Comprising, by the computing device, performing the service of the application corresponding to the user's service request by using the service information and the resource information received from the storage server,
The step of performing the service of the application includes, by the computing device, performing the service using a custom classloader that operates using the service information received from the outside,
The service information includes a class file compiled into byte code,
The step of performing the service using the custom classloader includes, by the computing device, receiving the resource information into the class file in a bytecode insertion method and generating a response corresponding to the service of the application. How to run a service architecture application.
6. The method of claim 5,
and before receiving the service and resource request, the computing device retrieving the service information and the resource information from an internal storage of the computing device.
delete A computer program stored in a computer-readable recording medium in combination with hardware to perform the microservices architecture application execution method according to claim 5 or 6.

Images