KR20210144044A - System for providing development framework which support both monolithic architecture and microservice architecture, method for developing application using the same and computer program for the same - Google Patents

Abstract

The present invention relates to a system for providing a development framework which supports both a monolithic architecture and a microservice architecture, a method for developing an application using the same and a computer program for the same, capable of automatically forming the container in a desired form. A system for providing a development framework includes: an input/output device configured to receive source information of an application to be developed and a request for producing a container associated with the application, from a user device; a source analyzing unit configured to analyze the source information and to produce relation information associated with a calling relation with at least one service of the application; a storing unit configured to store the relation information; and a container forming unit configured to form the container of the application, based on the relation information stored in the storing unit, in response to that the request for producing the container is received into the input/output device. When the system for providing the developing framework is used, and when the application is developed, the container may be automatically formed in a desire shape without selecting any one service form of a monolithic architecture or a microservice architecture.

Description

A system for providing a development framework supporting both monolithic architecture and microservice architecture, an application development method using the same, and a computer program for the same COMPUTER PROGRAM FOR THE SAME}

Embodiments relate to a system for providing a development framework, an application development method using the same, and a computer program for the same. More specifically, embodiments may automatically configure a container according to a desired form without having to select a service form in either a monolithic architecture or a microservice architecture when developing an application. A development framework that can relate to the technology will be there.

Monolithic architecture refers to the existing traditional application development form, and refers to a service form in which all components related to all functions of the application and logic for processing them are included 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 an inconvenience of having to redistribute the entire application even when 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 the 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 Registration No. 10-2027749 discloses a microservice system and method that provide control and management functions for communication occurring between MSA services.

In application development frameworks after MSA, the framework was configured to select either a monolithic architecture or a microservices architecture during development. However, in this case, there is a problem in that the service type must be changed during development or the development is difficult to proceed when the developer is not familiar with the development method of an architecture.

In addition, when a service developed based on the monolithic architecture is executed in the form of an MSA, it is not possible to check the information on 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, there is no need to select a service type in either a monolithic architecture or a microservice architecture when developing an application, and a container can be automatically configured according to a desired shape. It is possible to provide a system for providing a development framework that can be developed, an application development method using the same, and a computer program for the same.

A development framework providing system according to an aspect of the present invention includes an input/output unit configured to receive, from a user device, source information of an application to be developed and a request to create a container associated with the application; a source analyzer configured to analyze the source information to generate relationship information related to a call relationship between one or more services of the application; a storage unit configured to store the relationship information; and a container configuration unit configured to configure the container of the application based on the relation information stored in the storage unit in response to the container creation request being received by the input/output unit.

In one embodiment, the input information received from the user device includes a request for creation of a MicroService Architecture (MSA) container. In this case, the container configuration unit is further configured to generate one or more package information based on the relationship information and distribute the one or more package information to one or more microservice architecture containers.

The development framework providing system according to an embodiment further includes a transmitter configured to transmit resource information related to one or more services of the application to a storage server.

In one embodiment, the input information received from the user device includes a microservice architecture container creation request for monolithic package information. In this case, the container configuration unit extracts a business file from the monolithic package information based on the relationship information, and generates archive information for the operation of the microservice architecture container using the extracted business file. more composed.

In an embodiment, the container configuration unit is further configured to distribute the archive information to one or more microservice architecture containers.

An application development method according to an aspect of the present invention includes: receiving, by a development framework providing system, source information of an application to be developed from a user device; generating, by the development framework providing system, relationship information related to a call relationship between one or more services of the application by analyzing the source information; storing, by the development framework providing system, the relationship information in the development framework providing system; and configuring, by the development framework providing system, the container of the application based on the input information and the relation information received from the user device.

In one embodiment, the input received from the user device comprises a request to create a microservices architecture container. In this case, the step of configuring the container may include: generating, by the development framework providing system, one or more package information based on the relationship information; and distributing, by the development framework providing system, the one or more package information to one or more microservice architecture containers.

The application development method according to an embodiment further includes, before the step of configuring the container, transmitting, by the development framework providing system, resource information related to one or more services of the application to a storage server.

In one embodiment, the input information received from the user device includes a microservice architecture container creation request for monolithic package information. In this case, the step of configuring the container may include: extracting, by the development framework providing system, a business file from the monolithic package information based on the relationship information; generating, by the development framework providing system, archive information for the operation of the microservice architecture container using the extracted business file; and transmitting, by the development framework providing system, the archive information to the user device or an external server.

The application development method according to an embodiment further includes the step of distributing, by the development framework providing system, the archive information to one or more microservice architecture containers.

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

According to the development framework providing system and the application development method using the same according to an aspect of the present invention, direct calls between services are prohibited, the call relationship between services is checked during compilation, and package information is configured. By doing so, there is an advantage that containers can be automatically configured regardless of a monolithic architecture or a microservice architecture (MSA).

1 is a schematic block diagram of a system for providing a development framework according to an embodiment.
2 is a flowchart illustrating a container distribution process using a system for providing a development framework according to an embodiment.
3 is a flowchart illustrating a process of creating a microservice architecture (MSA) container from a monolithic package using a development framework providing system according to an embodiment.
4 is a schematic block diagram of a storage server of a system for providing a development framework 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 system for providing a development framework according to an embodiment.

Referring to FIG. 1 , the development framework providing system 3 according to the embodiments 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 is the user It serves to create a container based on a monolithic architecture or a microservice architecture (MSA) using source information input through the device 1 .

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 manner. 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 shown 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 a separate physically distinct component. 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. 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, source information is described by taking as an example the source code of the application based on the Java (JAVA) language. 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). Since this can be easily understood by a person skilled in the art from a conventional compiler, a detailed description thereof will be omitted.

The source analyzer 33 analyzes the source information converted by the compilation unit 32 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 analyzer 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. At this time, 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 the operation of the service 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 so that it can be loaded 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 FIG. 4 .

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 user device 1 of the developer (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. . In addition, 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 that another service called by a specific service does 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 transmission 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 a monolithic architecture or MSA through the management screen provided by the development framework providing system 3 . In the drawings, the step of inputting management information ( S28 ) is shown as a separate step for convenience of explanation, but according to an embodiment, the designation of the service type of the application may be made simultaneously with the commit of the source information.

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 a 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 corresponding 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).

3 is a flowchart illustrating a process of generating an MSA container from a monolithic package using a system for providing a development framework according to an embodiment.

1 and 3 , in this embodiment, the developer selects the package information that he is developing or pre-stored in the development framework providing system 3 through the development framework providing system 3, thereby corresponding to the MSA. Creation of a container may be requested (S31). For example, there may be a case where the service type of an application developed in the form of a monolithic architecture is changed to an MSA.

The container configuration unit 34 of the development framework providing system 3 is configured to, when an MSA container creation for specific package information is requested, based on the relation information stored in the storage unit 30, for the operation of the service of the corresponding package. It is possible to extract the business file (S22). This may mean extracting resource information or a common library file required for the operation of the service of the corresponding package from the storage unit 30 .

If there is an error in the process of extracting the business file based on the relationship information, the container configuration unit 34 may transmit the error information to the user device 1 (S33). For example, when the resource or library file related to the service of the corresponding package does not exist in the storage unit 30 , the container configuration unit 34 may generate error information to notify the developer thereof.

When the business file corresponding to the package for which MSA container creation is requested is extracted, the development framework providing system 3 may generate archive information including the corresponding business file (S34). In this case, the archive information may mean converting a business file into a file corresponding to a virtualization server on which the service is to be executed, for example, an ear, war, zip file, etc. so that the service can be executed using the corresponding business file in the MSA container.

Next, the container configuration unit 34 transmits the processing result for the creation of the archive to the user device 1 of the developer (S35), and when there is a request from the developer, the generated archive information is transferred to the user device 1 of the developer 1 ) can be transmitted to (S37). In this case, when a plurality of versions of the same archive are generated while application development is in progress, the developer may receive archive information by designating a version that he/she wants to download.

In one embodiment, the development framework providing system 3 may store the generated archive information in the storage unit 30 and distribute it to the related MSA container (S36). This may mean creating a new container or transferring an archive file to an existing container. Also, in one embodiment, the transmitting unit 34 of the development framework providing system 3 may be further configured to transmit the generated archive information to the external storage server 2 .

According to the embodiment described above with reference to FIGS. 1 to 3, when a developer develops an application, there is no need to designate a service type as either monolithic or MSA, and if a 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.

4 is a schematic block diagram of a storage server of a system for providing a development framework according to an embodiment.

1 and 4 , the storage server 2 includes a storage unit 21 storing service and resource information for service operation of the MSA container, and information returning requested information in response to a request from the MSA container. It may include a return unit 22 . In this case, 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, an MSA-based application provides a service by loading an image from Docker running on a virtualization server and executing it, and the MSA container conceptually refers to a computing device such as a virtualization server and a software means executed by it. can

In an embodiment, the MSA container 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 a user. Also, the MSA container may transmit a result of performing a service requested by the user to the user device 1 . For example, the MSA container requests the storage server 2 for service information (eg, class file, jsp file) and resource information (eg, txt, xml file, etc.) necessary for the operation of the requested service, and the storage server 2 may return requested service and resource information to the MSA container.

For the above operation, the MSA container 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 receives resource information through a method such as Byte Code Insertion (BCI) to perform services by utilizing external resource information in a class file compiled into byte code. It may be configured to generate a response based on this.

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 application development method according to the embodiments described above may be at least partially implemented as a computer program and recorded in a computer-readable recording medium. A computer-readable recording medium in which a program for implementing an operation according to the method according to the embodiments is recorded and includes all kinds of recording devices in which computer-readable data is stored. Examples of the computer-readable recording medium 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.

Further, 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 (11)

an input/output unit configured to receive, from a user device, source information of an application to be developed and a container creation request related to the application;
a source analyzer configured to analyze the source information to generate relationship information related to a call relationship between one or more services of the application;
a storage unit configured to store the relationship information;
and a container configuration unit configured to configure the container of the application based on the relation information stored in the storage unit in response to the container creation request being received by the input/output unit.
According to claim 1,
The input information received from the user device includes a request for creation of a microservices architecture container,
The container configuration unit is further configured to generate one or more package information based on the relationship information, and distribute the one or more package information to one or more microservice architecture containers.
According to claim 1,
The system further comprising a transmitter configured to transmit resource information related to one or more services of the application to a storage server.
According to claim 1,
The input information received from the user device includes a microservice architecture container creation request for monolithic package information,
The container configuration unit is a development framework further configured to extract a business file from the monolithic package information based on the relationship information, and to generate archive information for the operation of the microservice architecture container using the extracted business file. delivery system.
5. The method of claim 4,
The container configuration unit is further configured to distribute the archive information to one or more microservice architecture containers.
receiving, by the development framework providing system, source information of an application to be developed from a user device;
generating, by the development framework providing system, relationship information related to a call relationship between one or more services of the application by analyzing the source information;
storing, by the development framework providing system, the relationship information in the development framework providing system; and
The application development method comprising the step of configuring, by the development framework providing system, the container of the application based on the input information and the relationship information received from the user device.
7. The method of claim 6,
The input information received from the user device includes a request for creation of a microservices architecture container,
The step of constructing the container comprises:
generating, by the development framework providing system, one or more package information based on the relationship information; and
Application development method comprising the step of the development framework providing system distributing the one or more package information to one or more microservice architecture containers.
7. The method of claim 6,
Prior to the step of configuring the container, the development framework providing system, the application development method further comprising the step of transmitting resource information related to one or more services of the application to a storage server.
7. The method of claim 6,
The input information received from the user device includes a microservice architecture container creation request for monolithic package information,
The step of constructing the container comprises:
extracting, by the development framework providing system, a business file from the monolithic package information based on the relationship information;
generating, by the development framework providing system, archive information for the operation of the microservice architecture container using the extracted business file; and
Application development method comprising the step of the development framework providing system transmitting the archive information to the user device or an external server.
10. The method of claim 9,
The application development method further comprising the step of the development framework providing system distributing the archive information to one or more microservice architecture containers.
A computer program stored in a computer-readable recording medium to perform the application development method according to any one of claims 6 to 10 in combination with hardware.

Images