Extracting Candidates of Microservices from Monolithic Application Code

Kamimura, Manabu; Yano, Keisuke; Hatano, Tomomi; Matsuo, Akihiko

doi:10.1109/apsec.2018.00072

Cited by 37 publications

(41 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Lastly, coupling by contribution, based on Conway [9] law expressing that the structure of the software represents the structure of the organization, thus, specific modules that receive changes by a specific group of people/teams should be maintained together. Kamimura et al [19] propose a solution heavily focused on clustering. The clustering technique used by them is proposed by Kobayashi et al [21] and has the main goal to undermine the importance of modules that are omnipresent in the project, enabling a better identification of components [22].…”

Section: Related Workmentioning

confidence: 99%

“…The relevance of the functional decomposition of systems initially mentioned by Parnas was reinforced by the demand to distribute complex systems through network infrastructures such as web services and remote objects resulting from efforts to deal with systems of greater dimension and complexity [19].…”

mentioning

confidence: 99%

“…In order to benefit from MA such legacy software systems -that we call monolithic software systems -need to be refactored into a semantically equivalent microservice-based one. Performing such refactoring manually is both complex/time consuming and prone to errors, and its quality is often strongly linked to the experience and knowledge of the specialist leading said refactoring [19,30]. The refactoring is typically done following a Strangler pattern, that is, incrementally migrating and replacing modules of the system into a new architecture until the migrated systems overcome the old system.…”

mentioning

confidence: 99%

“…The identification of microservices in legacy monolithic systems is still an open problem with just a few proposed approaches [8,15,[17][18][19]26]. Most of these proposals, however, use their own quality metrics to assess the quality of the achieved transformation.…”

mentioning

confidence: 99%

See 3 more Smart Citations

Identification of microservices from monolithic applications through topic modelling

Brito

Cunha

Saraiva

2021

Proceedings of the 36th Annual ACM Symposium on Applied Computing

View full text Add to dashboard Cite

Section: Related Workmentioning

confidence: 99%

mentioning

confidence: 99%

mentioning

confidence: 99%

mentioning

confidence: 99%

See 2 more Smart Citations

Identification of microservices from monolithic applications through topic modelling

Brito

Cunha

Saraiva

2021

Proceedings of the 36th Annual ACM Symposium on Applied Computing

View full text Add to dashboard Cite

“…Legacy Modernization approach consists of two major phases called the Assessment phase and Implementation phase. Organizations are migrating their existing legacy applications to modern technologies with the help of microservices architecture patterns [28] [24] [22] [18] [15]. Microservices architecture promises high maintainability for software modernization [30], including decomposing the application into microservices-based on experience.…”

Section: Introductionmentioning

confidence: 99%

Legacy Digital Transformation: TCO and ROI Analysis

Mallidi

Sharma

Singh

2021

Int. j. electr. comput. eng. syst. (Online)

View full text Add to dashboard Cite

Legacy Digital Transformation is modernizing or migrating systems from non-digital or older digital technology to newer digital technologies. Digitalization is essential for information reading, processing, transforming, and storing. Social media, Cloud, and analytics are the major technologies in today's digital world. Digitalization (business process) and Digital Transformation (the effect) are the core elements of newer global policies and processes. Recent COVID pandemic situation, Organizations are willing to digitalize their environment without losing business. Digital technologies help to improve their capabilities to transform processes that intern promote new business models. Applications cannot remain static and should modernize to meet the evolving business and technology needs. Business needs time to market, Agility, and reduce technical debt. Technology needs consist of APIs, better Security, Portability, Scalability, Cloud support, Deployment, Automation, and Integration. This paper elaborates different transformation/modernization approaches for Legacy systems written in very long or End of Life (EOL) systems to newer digital technologies to serve the business needs. EOL impacts application production, supportability, compliance, and security. Organizations spend money and resources on Digital Transformation for considering Investment versus Return on Investment, Agility of the System, and improved business processes. Migration and Modernization are critical for any Legacy Digital Transformation. Management takes decisions to proceed with Digital Transformation for considering Total Cost Ownership (TCO) and Return on Investment (ROI) of the program. The paper also includes a TCO-ROI calculator for Transformation from Legacy / Monolithic to new architectures like Microservices.

show abstract

A service graph based extraction of microservices from monolith services of service‐oriented architecture

Raj

Sadam

2022

Softw Pract Exp

View full text Add to dashboard Cite

Service-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 increase in changing user requirements and SOA is still seen as monolithic from a deployment perspective. Monolithic services make the application complex, and it becomes difficult to maintain. With the evolution of microservices architecture, software architects started migrating legacy applications to microservices. However, existing migration approaches in the literature mostly focus on migrating monolithic applications to microservices. To the best of our knowledge, very few works have been done in migrating SOA applications to microservices. One of the major challenges in the migration process is the extraction of microservices from the existing legacy applications. To address this, we propose an approach to extract the candidate microservices using graph based algorithms. In particular, four algorithms are defined: (i) construction of service graph (SG), (ii) construction of task graph (TG) for each service of the a SOA application, (iii) extraction of candidate microservices using the SG of SOA application, and (iv) construction of a SG for a microservices application to retain the dependencies between the generated microservices. We chose a SOA-based web application to demonstrate the proposed microservices extraction approach and extracted the microservices. Additionally, we have evaluated the extracted microservices and compared them with SOA based services.

show abstract

Extracting Candidates of Microservices from Monolithic Application Code

Cited by 37 publications

References 19 publications

Identification of microservices from monolithic applications through topic modelling

Identification of microservices from monolithic applications through topic modelling

Legacy Digital Transformation: TCO and ROI Analysis

A service graph based extraction of microservices from monolith services of service‐oriented architecture

Contact Info

Product

Resources

About