Systematic Mapping of Monolithic Applications to Microservices Architecture

TL;DR

This paper explores the transition from monolithic to microservices architecture, proposing techniques for identifying microservices in legacy systems through a case study and domain-driven development.

Contribution

It introduces a novel technique for identifying microservices in monolithic systems, aiding organizations in migration efforts with practical case study insights.

Findings

Proposed technique improves work performance in microservice identification

Clear models are established for complex systems

Technique may be less effective for low-complexity systems

Abstract

The aim of this paper to provide the solution microservices architecture as a popular alternative to monolithic architecture. It discusses the advantages of microservices and the challenges that organizations face when transitioning from a monolithic system. It presents a case study of a financial application and proposed techniques for identifying microservices on monolithic systems using domain-driven development concepts. In recent years, microservices architecture has emerged as a new architectural style in the software development industry. As legacy monolithic software becomes too large to manage, many large corporations are considering converting their traditional monolithic systems into small-scale, self-contained microservices. However, migrating from monolithic to microservices architecture is a difficult and challenging task. It presents a comparison of the two architectural styles and discusses the difficulties that led companies to switch to microservices. The study's findings suggest that the proposed technique can improve work performance and establish clear models, but it may not be useful for systems with lower levels of complexity. This research paper has practical implications for software architects and developers who are considering migrating from monolithic to microservices architecture.