Migrating Enterprise Legacy Source Code to Microservices: On Multitenancy, Statefulness, and Data Consistency

Furda, Andrei; Fidge, Colin; Zimmermann, Olaf; Kelly, Wayne; Barros, Alistair

doi:10.1109/ms.2017.440134612

Cited by 69 publications

(24 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Service cutting was postponed and then performed applying the strangler pattern [24] for ongoing development. A major technical challenge was removing the application's session state to achieve statelessness [25] and thus enable dynamic scaling.…”

Section: Interview Case Descriptionsmentioning

confidence: 99%

Microservices Migration in Industry: Intentions, Strategies, and Challenges

Fritzsch

Bogner

Wagner

et al. 2019

2019 IEEE International Conference on Software Maintenance and Evolution (ICSME)

View full text Add to dashboard Cite

To remain competitive in a fast changing environment, many companies started to migrate their legacy applications towards a Microservices architecture. Such extensive migration processes require careful planning and consideration of implications and challenges likewise. In this regard, handson experiences from industry practice are still rare. To fill this gap in scientific literature, we contribute a qualitative study on intentions, strategies, and challenges in the context of migrations to Microservices. We investigated the migration process of 14 systems across different domains and sizes by conducting 16 indepth interviews with software professionals from 10 companies. We present a separate description of each case and summarize the most important findings. As primary migration drivers, maintainability and scalability were identified. Due to the high complexity of their legacy systems, most companies preferred a rewrite using current technologies over splitting up existing code bases. This was often caused by the absence of a suitable decomposition approach. As such, finding the right service cut was a major technical challenge, next to building the necessary expertise with new technologies. Organizational challenges were especially related to large, traditional companies that simultaneously established agile processes. Initiating a mindset change and ensuring smooth collaboration between teams were crucial for them. Future research on the evolution of software systems will in particular profit from the individual cases presented.

show abstract

Section: Interview Case Descriptionsmentioning

confidence: 99%

Microservices Migration in Industry: Intentions, Strategies, and Challenges

Fritzsch

Bogner

Wagner

et al. 2019

2019 IEEE International Conference on Software Maintenance and Evolution (ICSME)

View full text Add to dashboard Cite

show abstract

“…F I G U R E 1 Richardson approach: Extracting service 13 [Color figure can be viewed at wileyonlinelibrary.com] Furda 21 presents an approach for identifying challenges (multi-tenancy, statefulness, and data consistency) in legacy code and applying refactoring and architectural pattern-based migration techniques to deal with these challenges and migrate to microservices architectures.…”

Section: Related Work: Migration From Monolithic Applications To Microservicesmentioning

confidence: 99%

Migrating production monolithic systems to microservices using aspect oriented programming

et al. 2021

View full text Add to dashboard Cite

Several organizations need to address the challenge to migrate current traditional monolithic applications in production to microservices, preferably, without having to schedule maintenances to take the application offline. This article presents an approach for migrating to microservices with almost zero downtime and minimal changes in the monolithic code. The approach is based on the concepts of aspect-oriented programming (AOP) and reflection to enable to intercept calls inside the monolith and transform them into service requests invoking the newly built microservices using the concept of around advices. The aspects do the "dirty work" of decoupling what will be refactored and which service to call and practically "zero" code changes need to be done in the original monolithic code. This enables one key novel contribution of our migration approach which is the ability to revert code and data changes without having to take the system offline. Two applications are used as proofs of concept to demonstrate that the proposed approach enables to go "forward" or "backward" among different versions of the application with minimal code or data changes. An evaluation performed in the cloud demonstrates that this work does not introduce significant performance or cost overhead when compared to the current state of the art and to the original monolith. K E Y W O R D Saspect-oriented programming, microservice architecture, system migration INTRODUCTIONMicroservices is a recent advance to distributed software development that focuses on building a single application as a set of independent, autonomous, and scalable services. [1][2][3] Each service is developed, scaled, and deployed separately as different deployment units usually as a process running on a container such as Docker. Large-scale industrial projects have already proven the value of this architectural style such as Netflix and Amazon. The motivation behind microservices was to overcome some limitations of traditional application development such as applications developed as a single large deployment unit, called monolith. Some of these limitations are:• Monolithic applications contain a single code base and tend to become complex and large over time;• With a large code size, maintenance becomes more complex as well as build and deployment gets costly;

show abstract

“…misuse persist. teams [7] g [8] w [12] w [13] w [15] g [21] g [39] g [40] g [41] w [51] g [55] w [56] w [64] w [69] w [72] g [74] g [75] g [91] g [92] g [95] w [99] w We hereafter illustrate how (according to the authors of the selected studies) each design principle can be affected by each corresponding architectural smell, as well as how each smell can be resolved by applying a corresponding refactoring. When multiple refactorings are applicable to resolve an architectural smell, to provide a first measurement of how much a refactoring is used to resolve it, we display the weight 3 of each refactoring by exploiting %-based pie charts.…”

Section: A Taxonomy For Design Principles Architectural Smells and Rmentioning

confidence: 99%

Analysing and Deploying (Micro)service-Based Applications

Neri

2020

Communications in Computer and Information Science

View full text Add to dashboard Cite

Migrating Enterprise Legacy Source Code to Microservices: On Multitenancy, Statefulness, and Data Consistency

Cited by 69 publications

References 15 publications

Microservices Migration in Industry: Intentions, Strategies, and Challenges

Microservices Migration in Industry: Intentions, Strategies, and Challenges

Migrating production monolithic systems to microservices using aspect oriented programming

Analysing and Deploying (Micro)service-Based Applications

Contact Info

Product

Resources

About