Javascript must be enabled to continue!
Api Slicer: A Feature-Based Approach to Decomposing Monolithic Apis into Microservices
View through CrossRef
Many approaches related to decomposing monolithic applications have been proposed in recent studies. However, such studies are not sensitive to the decomposition of Monolithic APIs into microservices, resulting in the manual decomposition of monolithic APIs, based solely on the developer's experience. This article introduces the API Slicer, a similarity level-based approach between features, which uses the execution trace to understand the monolithic API and generate suggestions for microservices. The API Slicer stands out for showing which functionalities should be transformed into microservices and which should remain in the monolithic API, being agnostic of the technology, as long as the target application is object-oriented, and the similarity is made based on the list of packages that the user provides at the beginning of the recommendation process. The new aspect of our article is the proposed feature-based approach to decompose monolithic APIs into microservices. Furthermore, we propose an intelligible workflow and an architectural model for assisting software developers in the decomposition of monolithic APIs. Developers benefit from the API Slicer because it allows the semi-automatic decomposition of a monolithic API. The approach was evaluated through a case study, where 3 target applications were tested to verify the effectiveness of the microservice recommendation.
Title: Api Slicer: A Feature-Based Approach to Decomposing Monolithic Apis into Microservices
Description:
Many approaches related to decomposing monolithic applications have been proposed in recent studies.
However, such studies are not sensitive to the decomposition of Monolithic APIs into microservices, resulting in the manual decomposition of monolithic APIs, based solely on the developer's experience.
This article introduces the API Slicer, a similarity level-based approach between features, which uses the execution trace to understand the monolithic API and generate suggestions for microservices.
The API Slicer stands out for showing which functionalities should be transformed into microservices and which should remain in the monolithic API, being agnostic of the technology, as long as the target application is object-oriented, and the similarity is made based on the list of packages that the user provides at the beginning of the recommendation process.
The new aspect of our article is the proposed feature-based approach to decompose monolithic APIs into microservices.
Furthermore, we propose an intelligible workflow and an architectural model for assisting software developers in the decomposition of monolithic APIs.
Developers benefit from the API Slicer because it allows the semi-automatic decomposition of a monolithic API.
The approach was evaluated through a case study, where 3 target applications were tested to verify the effectiveness of the microservice recommendation.
Related Results
Systematic Mapping of Monolithic Applications to Microservices Architecture
Systematic Mapping of Monolithic Applications to Microservices Architecture
Purpose- The aim of this paper to provide the solution
microservices architecture as a popular alternative to monolithic
architecture. It discusses the advantages of microservices ...
The Secure Computation Application Programming Interface Using The ARAS Method
The Secure Computation Application Programming Interface Using The ARAS Method
An Application Programming Interface (API) entails guidelines, Principles and an
array of utilities, it stands as distinct software Applications interacting with one another
commun...
A service graph based extraction of microservices from monolith services of service‐oriented architecture
A service graph based extraction of microservices from monolith services of service‐oriented architecture
AbstractService‐oriented architecture (SOA) has been widely used to design enterprise applications in the past two decades. The services in SOA are becoming complex with the increa...
Performance Comparison of Monolithic and Microservices Architectures in Handling High-Volume Transactions
Performance Comparison of Monolithic and Microservices Architectures in Handling High-Volume Transactions
Monolithic and microservices are two distinct approaches for designing and developing applications. However, these architectures exhibit contrasting characteristics. In monolithic ...
Malware and Windows APIs: A Dangerous Duo
Malware and Windows APIs: A Dangerous Duo
This paper introduces its interaction with malware and Windows APIs (application programming interface). The first section describes malware and investigates various types such as ...
Decomposing Monolithic to Microservices: Keyword Extraction and BFS Combination Method to Cluster Monolithic’s Classes
Decomposing Monolithic to Microservices: Keyword Extraction and BFS Combination Method to Cluster Monolithic’s Classes
Abstract
Microservices architecture is widely used because of the ease of maintaining its microservices, as opposed to encapsulating functionality in a monolithic, which may...
An Empirical Study of Security Practices for Microservices Systems
An Empirical Study of Security Practices for Microservices Systems
Despite the numerous benefits of microservices systems, security has been a critical issue in such systems. Several factors explain this difficulty, including a knowledge gap among...
Silymarin PlantCrystals for Improved Dermal Drug Delivery
Silymarin PlantCrystals for Improved Dermal Drug Delivery
Background/Objectives: PlantCrystals (PCs) are submicron particles derived from plants or parts of plants that can be produced by bead milling and/or high-pressure homogenization. ...

