Towards a Technique for Extracting Relational Actors from Monolithic Applications

Laigner, Rodrigo; Lifschitz, Sérgio; Kalinowski, Marcos; Poggi, Marcus; Salles, Marcos Antonio Vaz

doi:10.5753/sbbd.2019.8814

Cited by 3 publications

(1 citation statement)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…[...] people wanted to create a separate microservice, just because of 'size', and we end up having consistency problems." Even though initial work suggests considering database-related attributes such as relationships between relations to derive a functional partitioning [44], a thorough evaluation of such approaches with real-world systems requires further exploration. C10.…”

Section: C8mentioning

confidence: 99%

Data Management in Microservices: State of the Practice, Challenges, and Research Directions

Laigner,

Zhou,

Salles

et al. 2021

Preprint

Self Cite

View full text Add to dashboard Cite

We are recently witnessing an increased adoption of microservice architectures by the industry for achieving scalability by functional decomposition, fault-tolerance by deployment of small and independent services, and polyglot persistence by the adoption of different database technologies specific to the needs of each service. Despite the accelerating industrial adoption and the extensive research on microservices, there is a lack of thorough investigation on the state of the practice and the major challenges faced by practitioners with regard to data management.To bridge this gap, this paper presents a detailed investigation of data management in microservices. Our exploratory study is based on the following methodology: (i) we conducted a systematic literature review of articles reporting the adoption of microservices in industry settings, where more than 300 articles were filtered down to 11 representative studies; (ii) we analyzed a set of 9 popular open-source microservice-based applications, selected out of more than 20 open-source projects; furthermore, (iii) to strengthen our evidence, we conducted an online survey that we then used to crossvalidate the findings of the previous steps with the perceptions and experiences of over 120 practitioners and researchers.Through this process, we were able to categorize the state of practice and reveal several principled challenges that cannot be solved by software engineering practices, but rather need systemlevel support to alleviate the burden of practitioners. Based on the observations we also identified a series of research directions to achieve this goal. Fundamentally, novel database systems and data management tools that support isolation for microservices, which include fault isolation, performance isolation, data ownership, and independent schema evolution across microservices must be built to address the needs of this growing architectural style.

show abstract

Section: C8mentioning

confidence: 99%

Data Management in Microservices: State of the Practice, Challenges, and Research Directions

Laigner,

Zhou,

Salles

et al. 2021

Preprint

Self Cite

View full text Add to dashboard Cite

show abstract

Cromlech: Semi-Automated Monolith Decomposition Into Microservices

Quattrocchi,

Cocco,

Staffa

et al. 2024

IEEE Trans. Serv. Comput.

View full text Add to dashboard Cite

Microservices architectures conceive an application as a composition of loosely-coupled sub-systems that are developed, deployed, maintained, updated, and scaled independently. Compared to monoliths, microservices speed up evolution and increase flexibility. For these reasons they are becoming the reference architecture for many practitioners. A key challenge to embrace a microservices architecture is how to decompose an application into microservices: a choice that deeply affects all subsequent development phases in ways that are difficult to foresee and evaluate. Without any tool to support their reasoning, developers may erroneously evaluate the various alternatives, leading to inaccurate decomposition choices that would result in increased development, operations, and maintenance costs. This paper tackles the problem with Cromlech, a semi-automatic tool to decompose a software system into microservices. Cromlech (i) takes in input a high-level model of the system in terms of functionalities and data entities accessed by those functionalities, (ii) formulates decomposition as an optimization problem, and (iii) outputs a proposed placement of functionalities and data onto microservices, using a visual representation that helps reasoning on the resulting architecture. Cromlech evaluates design concerns, communication overheads, data management requirements, opportunities and costs of data replication. Our evaluation on a real-world industrial application shows that Cromlech consistently delivers more efficient solutions than simple heuristics and state-of-the-art approaches, and provides useful insights to developers.

show abstract

Data management in microservices

et al. 2021

View full text Add to dashboard Cite

Microservices have become a popular architectural style for data-driven applications, given their ability to functionally decompose an application into small and autonomous services to achieve scalability, strong isolation, and specialization of database systems to the workloads and data formats of each service. Despite the accelerating industrial adoption of this architectural style, an investigation of the state of the practice and challenges practitioners face regarding data management in microservices is lacking. To bridge this gap, we conducted a systematic literature review of representative articles reporting the adoption of microservices, we analyzed a set of popular open-source microservice applications, and we conducted an online survey to cross-validate the findings of the previous steps with the perceptions and experiences of over 120 experienced practitioners and researchers. Through this process, we were able to categorize the state of practice of data management in microservices and observe several foundational challenges that cannot be solved by software engineering practices alone, but rather require system-level support to alleviate the burden imposed on practitioners. We discuss the shortcomings of state-of-the-art database systems regarding microservices and we conclude by devising a set of features for microservice-oriented database systems.

show abstract

Towards a Technique for Extracting Relational Actors from Monolithic Applications

Cited by 3 publications

References 11 publications

Data Management in Microservices: State of the Practice, Challenges, and Research Directions

Data Management in Microservices: State of the Practice, Challenges, and Research Directions

Cromlech: Semi-Automated Monolith Decomposition Into Microservices

Data management in microservices

Contact Info

Product

Resources

About