From a Monolith to a Microservices Architecture: An Approach Based on Transactional Contexts

Nunes, Luís; Santos, Nuno; Silva, António Rito

doi:10.1007/978-3-030-29983-5_3

Cited by 37 publications

(34 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Silhouette score. Nunes, Santos & Rito Silva (2019) define the silhouette score as “the difference between the mean nearest-cluster distance a and the mean intra-cluster distance b divided by the greatest of a and b . This score ranges its values from −1 to 1, representing incorrect clustering (samples on wrong clusters) and highly dense clustering, respectively.…”

Section: Resultsmentioning

confidence: 99%

Defining and measuring microservice granularity—a literature overview

Vera-Rivera

Gaona

Astudillo

2021

PeerJ Computer Science

View full text Add to dashboard Cite

Background Microservices are an architectural approach of growing use, and the optimal granularity of a microservice directly affects the application’s quality attributes and usage of computational resources. Determining microservice granularity is an open research topic. Methodology We conducted a systematic literature review to analyze literature that addresses the definition of microservice granularity. We searched in IEEE Xplore, ACM Digital Library and Scopus. The research questions were: Which approaches have been proposed to define microservice granularity and determine the microservices’ size? Which metrics are used to evaluate microservice granularity? Which quality attributes are addressed when researching microservice granularity? Results We found 326 papers and selected 29 after applying inclusion and exclusion criteria. The quality attributes most often addressed are runtime properties (e.g., scalability and performance), not development properties (e.g., maintainability). Most proposed metrics were about the product, both static (coupling, cohesion, complexity, source code) and runtime (performance, and usage of computational resources), and a few were about the development team and process. The most used techniques for defining microservices granularity were machine learning (clustering), semantic similarity, genetic programming, and domain engineering. Most papers were concerned with migration from monoliths to microservices; and a few addressed green-field development, but none address improvement of granularity in existing microservice-based systems. Conclusions Methodologically speaking, microservice granularity research is at a Wild West stage: no standard definition, no clear development—operation trade-offs, and scarce conceptual reuse (e.g., few methods seem applicable or replicable in projects other than their initial proposal). These gaps in granularity research offer clear options to investigate on continuous improvement of the development and operation of microservice-based systems.

show abstract

Section: Resultsmentioning

confidence: 99%

Defining and measuring microservice granularity—a literature overview

Vera-Rivera

Gaona

Astudillo

2021

PeerJ Computer Science

View full text Add to dashboard Cite

show abstract

“…Like model-based techniques, graph-based analysis depends on representing the microservice system as a graph and then analyzing that structure, exploiting microservices' natural graph-like connections. Graph-based techniques are commonly used for detecting faults or performing root cause analysis [47,52,54,55], as well as performing monolithto-microservice migration by representing an existing monolith as a graph that can be segmented into microservices [23,24,48,49]. However, it can also be used in tracing patterns [27,28].…”

Section: Rq1: Methods and Techniques Usedmentioning

confidence: 99%

“…This allows the concepts identified by the static analysis to be ranked based on their significance. Nunes et al [49] use an approach based on static analysis of monolithic source code to develop a text-call graph. Next, the call graph is used to generate a dendrogram, which is then cut into a set of clusters.…”

Section: Graph-based Analysismentioning

confidence: 99%

“…Cerny et al [14] explain the potential pitfalls of converting a system from a monolithic architecture to a microservice architecture while also discussing the value of static-code analysis in microservice systems. Nunes et al [49] aim to assist the decomposition of monolithic applications to microservice-based ones by proposing the decomposition be done by identifying where a business transaction is divided into several transactional contexts. This identification of transactional contexts groups domain entities by where they are executed instead of by their structural domain inter-relationships, allowing developers to determine the impacts of decomposition.…”

Section: Migration To Microservicesmentioning

confidence: 99%

“…Another common topic addressed was migration to microservice-based architectures either by providing tools to decompose monolithic architectures into microservices [15,16,19,32,50,56] or to assist in deciding if migration is beneficial and feasible [21,48,49,64]. Although we could assume a silver bullet by now when it comes to the design of microservice systems, there is no perfect guidance for engineers managing legacy systems.…”

Section: Rq2: Goals Addressed By the Papersmentioning

confidence: 99%

See 2 more Smart Citations

On Microservice Analysis and Architecture Evolution: A Systematic Mapping Study

et al. 2021

View full text Add to dashboard Cite

Microservice architecture has become the leading design for cloud-native systems. The highly decentralized approach to software development consists of relatively independent services, which provides benefits such as faster deployment cycles, better scalability, and good separation of concerns among services. With this new architecture, one can naturally expect a broad range of advancements and simplifications over legacy systems. However, microservice system design remains challenging, as it is still difficult for engineers to understand the system module boundaries. Thus, understanding and explaining the microservice systems might not be as easy as initially thought. This study aims to classify recently published approaches and techniques to analyze microservice systems. It also looks at the evolutionary perspective of such systems and their analysis. Furthermore, the identified approaches target various challenges and goals, which this study analyzed. Thus, it provides the reader with a roadmap to the discipline, tools, techniques, and open challenges for future work. It provides a guide towards choices when aiming for analyzing cloud-native systems. The results indicate five analytical approaches commonly used in the literature, possibly in combination, towards problems classified into seven categories.

show abstract

Identification of monolith functionality refactorings for microservices migration

Correia

Silva

2022

Softw Pract Exp

Self Cite

View full text Add to dashboard Cite

In the process of migrating a monolith to a microservice architecture, functionalities which execute on top of a single database as ACID transactions, have their execution split between several databases, one for each microservice.Therefore, the complexity of functionality migration increases, because of the lack of isolation of the functionality execution, which has to be handled by following an eventual consistency model. On the other hand, the object-oriented approach, commonly followed in the development of monolith systems, promotes fine-grained interactions in the functionalities implementation, which further increases the migration effort due to the large number of remote invocations between microservices, because it increases the number of microservices transactions that have to eventually be consistent. The main contribution of this paper is a heuristic method to help the software architect on the identification of functionality refactorings, to reduce the effort required to migrate the functionality to microservices when applying the SAGA pattern in the functionality microservices implementation. The heuristic accuracy and efficiency of the method is evaluated using a dataset extracted from 78 codebases and by comparing the results with expert refactorizations. Additionally, a performance analysis of the heuristic implementation is done.

show abstract

From a Monolith to a Microservices Architecture: An Approach Based on Transactional Contexts

Cited by 37 publications

References 21 publications

Defining and measuring microservice granularity—a literature overview

Defining and measuring microservice granularity—a literature overview

On Microservice Analysis and Architecture Evolution: A Systematic Mapping Study

Identification of monolith functionality refactorings for microservices migration

Contact Info

Product

Resources

About