Migrating monolithic applications to function as a service

Abstract

SummaryFunction as a service (FaaS) promises low operating costs, reduced complexity, and good application performance. However, it is still an open question how to migrate monolithic applications to FaaS. In this paper, we present a guideline for software designers to split monolithic applications into smaller functions that can be executed in a FaaS environment. This enables independent scaling of individual parts of the application. Our approach consists of three steps: We first identify the main tasks (and their subtasks) of the application to split. Then, we define the program flow to be able to tell which application tasks can be converted to functions and how they interact with each other. In the final step, we specify actual functions and possibly merge those that are too small and which would produce too much communication overhead or maintenance effort. Compared to existing work, our approach applies to applications of any size and results in functions that are small enough—but not too small—for efficient execution in a FaaS environment. We evaluate the usefulness of our approach by applying it to a real‐world application for the storage of geospatial data. We describe the experiences made and finish the paper with a discussion, conclusions, and ideas for future work.

Special issue on efficient management of microservice‐based systems and applications

“…The proposed method employs a two-stage refactoring strategy, initially performing a coarse-grained decomposition followed by a fine-grained one. This approach streamlines the decomposition process into smaller, more manageable steps, providing adaptability to generate a solution at either the microservice or function level.In the fourth paper, Würz et al 4 identified the principal tasks and subtasks of the application for the purpose of partitioning. Subsequently, they outlined the program flow to ascertain which application tasks could be transformed into functions and elucidated their interdependencies.…”

“…In the fourth paper, Würz et al 4 identified the principal tasks and subtasks of the application for the purpose of partitioning. Subsequently, they outlined the program flow to ascertain which application tasks could be transformed into functions and elucidated their interdependencies.…”