Systematic Mapping of Monolithic Applications to Microservices Architecture

Purpose- 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. Design/methodology/approach- 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. Findings- This research paper examines the challenges and benefits of migrating from monolithic to microservices architecture. 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. Practical implication- This research paper has practical implications for software architects and developers who are considering migrating from monolithic to microservices architecture. The paper provides a technique for identifying microservices on monolithic systems using domain-driven concepts and various communication protocols for service interaction. The study’s findings suggest that this proposed technique can help establish clear models and enhance work performance for complex systems. Originality/value- This paper contributes to the field of software development by providing valuable insights and practical solutions for companies considering a switch to microservices architecture. We compared the two architectural styles and talked about the difficulties that led to the companies’ decision to switch over microservices architectures. A case study of a financial application is presented, in which we discussed our technique for identifying microservices on monolithic systems using domain driven concepts, as well as various communication protocols for service interaction. The study’s findings showed that this proposed technique helped to establish clear models and enhanced work performance, but it may not be useful for systems with lower levels of complexity.