TW201931144A - Serverless system and execution method thereof - Google Patents

Abstract

Serverless system and execution method thereof, which comprising: a setting module is used to set the upper and lower thresholds; a function statistics module is used to receive information on the execution of the function, and statistics on the number of executions of the function; a microservice management module is providing microservices equipped with this function; a container management module is providing the container equipped with this function; and a function execution selection module is used to compare the execution times of the function and the upper and lower thresholds and select the microservice management module or the container management module to execute the function according to the comparing results.

Description

Serverless system and execution method thereof

The present invention relates to a serverless technology, and more particularly to a serverless system that can accelerate execution efficiency and a method of executing the same.

Serverless is a kind of cloud server. Users don't need to set up a physical server. Users only need to provide appropriate code, and the rest are automatically managed by the cloud server.

There is no server system and a programming language interface allows the user to develop functions and then perform functions through a serverless system. In the past, when there was no server system to execute the function, the function was generated after the container was built and loaded, and the container with the function was removed after the function was executed. However, this method would have low performance. The problem.

Therefore, how to effectively improve the serverless performance is the technical problem to be solved by the present invention.

To overcome the lack of prior art, the present invention provides a serverless system, comprising: a setting module for setting an upper threshold and a lower threshold; and a function statistics module for receiving a function. Message, And counting the number of executions of the function; the micro service management module provides the function of generating, resetting, querying and executing the microservices of the microservices (Microservices) equipped with the function; the container management module is provided The function of the container is generated, removed, and executed in the container, wherein the container is removed after performing the function; and the function execution selection module is connected to the setting module, the function statistical module a group, the microservice management module, and the container management module, and the function execution selection module is configured to compare the number of executions of the function with the upper threshold and the lower threshold and query the microservice to compare the comparison The result of the microservice and the result of querying the microservice enable the microservice management module or the container management module to perform the function.

The invention further provides a serverless execution method, which comprises: (1) setting an upper threshold value and a lower threshold value; (2) receiving a message of execution of the function to obtain the number of executions of the function; (3) comparing the The number of executions of the function and the upper threshold and the lower threshold; and (4) selecting the microservice or container to perform the function according to the comparison result, wherein the container is removed after performing the function, and the micro The service will continue to be resident after the service has completed this function.

The technical features of the present invention are as follows:

1. The present invention can be executed by generating resident microservices for frequently executed functions, eliminating the need for multiple container generation and termination, and reducing execution time.

2. By reducing the number of times the container is generated and terminated, the system I/O frequency can be reduced and the overall system performance can be improved.

3. The present invention can also terminate the microservice conversion into a generation container execution when the number of function executions is reduced, thereby saving computational resources.

As can be seen from the above, according to the number of executions of the function, the microservices management module can generate the microservice resident carrying the function to perform the function or remove the microservice carrying the function, thereby eliminating the generation of multiple containers. And to remove, thereby reducing the time to perform the function and saving computing resources. Secondly, by reducing the number of times the container is generated and removed, the serverless I/O frequency can be reduced, and the overall performance of the serverless system can be improved.

100‧‧‧Users

102-1‧‧‧Micro Service 1

102-n‧‧‧Microservice n

103-1‧‧‧ Function 1

103-n‧‧‧ function n

104-1‧‧‧ Container 1

104-m‧‧‧ container m

105-x‧‧‧ function x

105-y‧‧‧ function y

200‧‧‧No server system

210‧‧‧Setting module

220‧‧‧Functional Statistics Module

230‧‧‧ Function Execution Selection Module

241‧‧‧Micro Service Management Module

242‧‧‧ Container Management Module

S301~S304‧‧‧Steps

1 is an operational architecture diagram of a serverless system of the present invention; FIG. 2 is a schematic architectural diagram of a serverless system of the present invention; and FIG. 3 is a flowchart of a method for executing a serverless invention of the present invention. flow chart.

The other embodiments of the present invention will be readily understood by those skilled in the art from this disclosure.

It is to be understood that the structure, the proportions, the size, and the like of the present invention are intended to be used in conjunction with the disclosure of the specification, and are not intended to limit the invention. The conditions are limited, so it is not technically meaningful. Any modification of the structure, change of the proportional relationship or adjustment of the size should remain in this book without affecting the effects and the objectives that can be achieved by the present invention. The technical content disclosed in the invention can be covered.

Please refer to FIG. 1 , which is an operation frame of the serverless system of the present invention. The user 100 can perform functions through the serverless system 200. There is two ways for the serverless system 200 to perform functions. The first method is to execute the function 103-1 through the microservices 102-1~102-n. ~103-n, the microservices 102-1~102-n are generated by the serverless system 200, are resident, can continuously receive requests from the serverless system 200 to perform function 1, and each microservice can only execute One function, the second is to execute the function 105-x~105-y through the containers 104-1~104-m, and when the user wants to perform the function 105-x~105-y, the container 104-1~104-m It will be generated by the serverless system 200. After the function functions 105-x~105-y are executed, the containers 104-1~104-m will be terminated and removed.

Figure 2 is a schematic architectural diagram of a serverless system of the present invention. As shown in the figure, the serverless system of the present invention includes: a setting module 210 for the user 100 to set the upper threshold and the lower threshold, wherein the upper threshold must be greater than the lower threshold; The group 220 is configured to receive a message that the user 100 proposes to perform the function, to count the number of executions of the function, and the micro service management module 241 provides the generation, removal, query, and execution of the micro service that carries the function. The function in the microservice; the container management module 242 provides the function of generating, removing, and executing the container carrying the function, wherein the container removes the container after performing the function; and the function The execution selection module 230 is connected to the setting module 210, the function statistics module 220, the micro service management module 241, and the container management module 242, and the function execution selection module 230 is configured to compare the execution of the function. And the threshold value and the lower threshold value are queried and the micro service is queried according to the comparison result and the micro service is queried As a result, the microservice management module or the container management module performs the function.

In one embodiment, the function statistics module system counts the number of executions of the function at a recent fixed time (eg, 30 minutes).

In an embodiment, when the number of executions of the function is greater than or equal to the upper threshold, the function execution selection module 230 queries the micro service management module 241 group whether there is a micro service carrying the function, and if so, the function The execution selection module 230 causes the micro service management module 241 to perform the function. If not, the function execution selection module 230 causes the micro service management module 241 to generate the micro service carrying the function to execute the micro service. Features.

In an embodiment, when the number of executions of the function is less than or equal to the lower threshold, the function execution selection module 230 queries the microservice management module 241 whether the microservice is equipped with the function, and if so, the function The execution selection module 230 causes the micro service management module 241 to remove the microservice that carries the function, and causes the container management module 242 to generate a container carrying the function and execute the function in the container, and if not, the The function execution selection module 230 causes the container management module 242 to generate a container carrying the function and perform the function within the container.

In an embodiment, when the number of executions of the function is less than the upper threshold and greater than the lower threshold, the function execution selection module 230 queries the microservice management module 241 for the microservice that carries the function. If yes, the function execution selection module 230 causes the micro service management module 241 to perform the function. If not, the function execution selection module 230 causes the container management module 243 to generate a container carrying the function and execute the container. This feature is inside.

Figure 3 is a flow chart showing the steps of the method for executing a serverless server of the present invention. As shown, the serverless execution method of the present invention includes the following steps.

In step S301, an upper threshold value and a lower threshold value are set.

In step S302, a message of execution of the function is received to obtain the number of executions of the function.

In step S303, the number of executions of the function and the upper threshold and the lower threshold are compared.

In step S304, the microservice or the container is selected to perform the function according to the comparison result, wherein the container removes the container after performing the function, and the microservice continues to be resident after performing the function.

In an embodiment, the step S302 is to obtain the number of executions of the function at the most recent fixed time (eg, 30 minutes).

In an embodiment, when the number of executions of the function is greater than or equal to the upper threshold, the step S304 includes querying whether the function is piggybacked in the microservice; if yes, selecting the microservice to perform the function, and if not, A microservice carrying the function is generated and the function in the microservice is executed.

In an embodiment, when the number of executions of the function is less than or equal to the lower threshold, the step S304 includes querying whether the function is piggybacked in the microservice; if yes, removing the microservice that carries the function, and generating the piggyback The container of the function executes the function in the container, and if not, the container carrying the function is generated and the function in the container is executed.

In an embodiment, when the number of executions of the function is less than the upper threshold and greater than the lower threshold, the step S304 includes querying the function. Whether it can be carried in the microservice; if so, the microservice is selected and the function is executed, and if not, the container carrying the function is generated and the function in the container is executed.

Three embodiments are provided below to illustrate the steps of performing the method illustrated in Figure 3 of the system operation of Figure 2.

In the first embodiment, it is assumed that the function of the function statistics module 220 is to calculate the number of function executions in the last 30 minutes, and the function execution time of the function F in the last 30 minutes is 1500. There is no micro service to carry the function F. The detailed operation steps are as follows:

In step S301, the user 100 inputs an upper threshold value of 1400 and an input lower threshold value of 1000 through the setting module 210.

In step S302, the user 100 proposes an execution function F to the serverless system 200, and the function statistics module 220 receives the message that the user 100 proposes to perform the function F, and obtains the number of executions of the function F in the last 30 minutes as 1500.

In step S303, the function execution selection module 230 obtains the upper and lower thresholds from the setting module 210 and obtains the number of executions of the function F in the last 30 minutes from the function statistics module, and compares the function F to the latest 30. The number of executions in minutes is 1500 or more, and the upper threshold is 1400.

In step S304, the function execution selection module 230 queries the micro service management module 241 to check whether the micro service is equipped with the function F. Since there is no micro service in the embodiment to carry the function F, the function execution selection module 230 is executed. The microservice management module 241 is configured to generate a microservice carrying the function F and execute the function F in the microservice.

In the second embodiment, it is assumed that the statistical mode of the function statistics module 220 is to calculate the number of function executions in the last 30 minutes, and the function execution time of the function F in the last 30 minutes is 900, and the micro service with the function F is present. The detailed operation steps are as follows:

In step S301, the user 100 inputs an input upper limit threshold of 1400 through the setting module 210, and the input lower threshold is 1000.

In step S302, the user 100 proposes an execution function F to the serverless system 200, and the function statistics module 220 receives the message that the user 100 proposes the function F to execute, and obtains the number of executions of the function F in the last 30 minutes is 900.

In step S303, the function execution selection module 230 obtains the upper and lower thresholds from the setting module 210 and obtains the number of executions of the function F in the last 30 minutes from the function statistics module, and compares the function F in the last 30 minutes. The number of executions is 900 or less and the lower threshold is 1000.

In step S304, the function execution selection module 230 queries the micro service management module 241 to check whether the micro service is equipped with the function F. In the embodiment, the micro service is provided with the function F, and the function execution selection module 230 The microservice management module 241 removes the microservice that carries the function F, and causes the container management module 242 to generate a container carrying the function F and execute the function F in the container.

In the third embodiment, it is assumed that the function of the function statistics module 220 is to calculate the number of function executions in the last 30 minutes, and the function execution time of the function F in the last 30 minutes is 1100. There is no micro service to carry the function F. The detailed operation steps are as follows:

In step S301, the user 100 inputs an input upper limit threshold of 1400 through the setting module 210, and the input lower threshold is 1000.

In step S302, the user 100 proposes an execution function F to the serverless system 200, and the function statistics module 220 receives the message that the user 100 proposes the function F to execute, and obtains the number of executions of the function F in the last 30 minutes as 1100.

In step S303, the function execution selection module 230 obtains the upper and lower thresholds from the setting module 210 and obtains the number of executions of the function F in the last 30 minutes from the function statistics module, and compares the function F in the last 30 minutes. The number of executions is 1100 less than the upper threshold value of 1400 and greater than the lower threshold value of 1000.

In step S304, the function execution selection module 230 queries the micro service management module 241 to check whether the micro service is equipped with the function F. Since there is no micro service in the embodiment to carry the function F, the function execution selection module 230 is executed. The container management module 242 is caused to generate a container carrying the function F and execute the function F in the container.

As can be seen from the above, according to the number of executions of the function, the microservices management module can generate the microservice resident carrying the function to perform the function or remove the microservice carrying the function, thereby eliminating the generation of multiple containers. And the removal, thereby reducing the time to perform the function and saving computing resources. Secondly, by reducing the number of times the container is generated and removed, the serverless I/O frequency can be reduced, and the overall performance of the serverless system is improved.

The above embodiments are intended to illustrate the principles of the invention and its effects, and are not intended to limit the invention. Anyone who is familiar with this skill can The above embodiments are modified without departing from the spirit and scope of the invention. Therefore, the scope of protection of the present invention should be as set forth in the appended claims.

Claims (10)

A serverless system includes: a setting module for setting an upper threshold value and a lower threshold value; and a function statistics module for receiving a function execution function to count the number of executions of the function; The service management module provides the function of generating, relocating, querying and executing the microservices of the microservices carrying the function; the container management module provides the generation, removal and execution of the container carrying the function. a function in the container, wherein the container is removed after performing the function; and a function execution selection module is connected to the setting module, the function statistics module, the micro service management module, and the container management a module, wherein the function execution selection module compares the number of executions of the function with the upper threshold and the lower threshold and queries the microservice to determine the result of the comparison and query the result of the microservice. The microservice management module or the container management module performs this function. The system of claim 1, wherein when the number of executions of the function is greater than or equal to the upper threshold, the function execution selection module queries the microservice management module to check whether the function has the micro function. The service, if yes, the function execution selection module causes the micro service management module to perform the function, and if not, the function execution selection module causes the micro service management module to generate the micro service carrying the function and execute the micro service This feature within the service. The system of claim 1, wherein the function is When the number of executions is less than or equal to the lower threshold, the function execution selection module queries the micro service management module whether there is a micro service carrying the function, and if so, the function executes the selection module to make the micro service management module The group removes the microservice that carries the function, and causes the container management module to generate the container carrying the function and executes the function in the container. If not, the function executes the selection module to enable the container management module to generate the load. The container of this function and performs this function within the container. The system of claim 1, wherein when the number of executions of the function is less than the upper threshold and greater than the lower threshold, the function execution selection module queries the microservice management module to have a microservice that carries the function, if yes, the function execution selection module causes the microservice management module to perform the function, and if not, the function execution selection module causes the container management module to generate a container carrying the function and Execute this function within the container. The system of claim 1, wherein the function statistical module system counts the number of executions of the function in the last 30 minutes. A serverless execution method includes: (1) setting an upper threshold and a lower threshold; (2) receiving a message of execution of the function to obtain the number of executions of the function; and (3) comparing the number of executions of the function And the upper threshold and the lower threshold; and (4) selecting the microservice or container to perform the function according to the comparison result, wherein the container is removed after performing the function, and The microservice will continue to be resident after performing this function. The execution method of claim 6, wherein when the number of executions of the function is greater than or equal to the upper threshold, the step (4) includes: querying whether the function is piggybacked in the microservice; and if The microservice is selected to perform the function, and if not, the microservice carrying the function is generated and the function in the microservice is executed. The execution method of claim 6, wherein when the number of executions of the function is less than or equal to the lower threshold, the step (4) includes: querying whether the function is piggybacked in the microservice; and if The microservice that carries the function is removed, and the container that carries the function is generated and the function in the container is executed. If not, the container carrying the function is generated and the function in the container is executed. The method of claim 6, wherein when the number of executions of the function is less than the upper threshold and greater than the lower threshold, the step (4) includes: querying whether the function is piggybacked on the micro In the service; and if so, the microservice is selected to perform the function, and if not, the container carrying the function is generated and the function in the container is executed. The execution method of claim 6, wherein the step (2) is to obtain the number of executions of the function in the last 30 minutes.