Aug 2026· International Journal of Combinatorial Optimization Problems and Informatics· Vol 17, pp. 233-251· 0 citations
Abstract
Migrating monolithic applications to microservice architectures offers benefits such as scalability, resilience, and continuous deployment. However, decomposing shared monolithic databases remains a major challenge due to strong structural and functional dependencies among application components and shared relational schemas. This paper proposes a semi-automatic decomposition method that identifies candidate microservices and service-specific databases through static analysis of use-case interaction sequences, source code dependencies, and database access relationships aligned with business capabilities. The proposed approach evaluates structural coupling using the Shared Table Coupling Index (IATC) indicator before and after migration. The method was validated through a case study and an empirical evaluation involving 17 monolithic systems from public repositories. The results show a statistically significant reduction in shared-data coupling, with an average reduction of approximately 91%, indicating the effectiveness of the proposed approach for reducing structural dependencies during monolith-to-microservices migration.
Spanish-language metadata / Metadatos en españolTítulo en español:Método para migrar sistemas de software monolíticos y su base de datos global hacia microservicios aislados
Resumen:La migración de aplicaciones monolíticas hacia arquitecturas de microservicios ofrece beneficios como escalabilidad, resiliencia y despliegue continuo. Sin embargo, la descomposición de bases de datos monolíticas compartidas continúa siendo un desafío importante debido a las fuertes dependencias estructurales y funcionales entre los componentes de la aplicación y los esquemas relacionales compartidos. Este artículo propone un método semiautomático de descomposición que identifica microservicios candidatos y bases de datos específicas para cada servicio mediante el análisis estático de las secuencias de interacción de los casos de uso, las dependencias del código fuente y las relaciones de acceso a la base de datos, en correspondencia con las capacidades del negocio. El enfoque propuesto evalúa el acoplamiento estructural mediante el indicador denominado Índice de Acoplamiento por Tablas Compartidas (IATC), antes y después de la migración. El método se validó mediante un estudio de caso y una evaluación empírica que incluyó 17 sistemas monolíticos procedentes de repositorios públicos. Los resultados muestran una reducción estadísticamente significativa del acoplamiento de datos compartidos, con una disminución promedio de aproximadamente el 91 %, lo que demuestra la eficacia del enfoque propuesto para reducir las dependencias estructurales durante la migración de sistemas monolíticos a microservicios.
Palabras Claves:sistemas monolíticos; migración a microservicios; descomposición de bases de datos; base de datos por servicio; análisis estático.
Smart citations:
https://scite.ai/reports/10.61467/2007.1558.2026.v17i4.1434Dimensions.Open Alex.
The migration of large-scale legacy monolithic systems to microservice architecture remains one of the pressing challenges in modern software engineering. This article examines methodological approaches to decomposing a Python-based monolith into an ecosystem of independently deployed microservices while preserving backward compatibility and ensuring controlled, non-disruptive data migration. The study is based on systematic analysis of peer-reviewed academic literature, industrial case studies, and the practical project experience of the author, including the transformation of a Python backend system that resulted in test coverage growth from 27% to 95% and database update acceleration by a factor of eighteen. The research identifies the Strangler Fig pattern combined with Domain-Driven Design (DDD) as the most evidence-supported decomposition strategy, proposes a six-stage migration roadmap incorporating dual-write data synchronization and API versioning, and formulates a risk matrix specific to Python ecosystems. The article contributes an original migration methodology that bridges the existing gap between theoretical decomposition frameworks and practical Python toolchain implementation. The results are of interest to software architects, backend engineers, and engineering managers engaged in system modernization projects.
D. Lunev· International Journal of Mod...· 0 citations
As legacy application architectures can limit the ability to deliver quickly, engineer for resilience, scale, and deploy independently, enterprise migration to microservices running on Kubernetes has emerged as a key modernization priority. This review analyzes peer-reviewed research in the field of migration patterns, service decomposition, containerization, orchestration, technical debt, organizational readiness and runtime governance in enterprise contexts. The literature suggests that full architectural replacement is seldom the most effective migration path. Instead, incremental extraction, a well-defined service-boundary understanding, platform engineering capability, observability maturity, data ownership redesign, and a staged coexistence between legacy and cloud-native elements are essential for durable modernization. Reported studies also highlight current shortcomings, such as poor longitudinal evidence, inconsistent migration measures, only minimal empirical validation for Kubernetes, and inadequate attention to regulated enterprise constraints. The review builds an abbreviated conceptual framework for migration to Kubernetes and draws inferences from comparative results from reported studies. It concludes that there needs to be more evidence in the field on production-scale economics of migration, platform reliability, socio-technical governance, and measurable results in different and diverse enterprise domains.
Shubham Srivastava· World Journal of Advanced En...· 0 citations
This paper analyzes the two software architectural approaches namely Monolithic Architecture vs Microservices Architecture when considering scalable software development, and puts the following into consideration: empirical trade-offs, scalability consideration, organizational implications, and development complexity.
Theophilus Bamise Ajala, A. Oduroye, I. Ayoade et al.· Asian journal of applied sci...· 0 citations
Microservices Architecture (MSA) has become a de-facto standard for designing cloud-native enterprise applications due to its efficient infrastructure setup, service availability, elastic scalability, dependability, and enhanced security. Transitioning existing monolithic systems to microservices is essential to leverage these benefits. However, manual decomposition of large-scale applications is labor-intensive and prone to errors. AI-based systems offer promising solutions for automating this process. This paper introduces CARGO (Context-sensitive lAbel pRopaGatiOn), a novel un-/semi-supervised partition refinement technique that utilizes a context- and flow-sensitive system dependency graph of monolithic applications. CARGO refines and enhances the partitioning quality of existing microservice partitioning algorithms. Experiments demonstrate that CARGO improves partition quality, reduces distributed transactions, and enhances performance metrics such as latency and throughput in microservice applications.
R. M· International Journal of Art...· 0 citations
The findings demonstrate that structural evaluations of LLM-generated decompositions should explicitly control for mapping coverage, as apparent differences between prompting strategies may otherwise reflect methodological bias rather than genuine architectural quality.
D. Silva, Renan Alves, E. Filho et al.· 0 citations
Microservice-based systems evolve continuously through API changes, service splits and merges, dependency churn, and deployment-topology drift driven by DevOps practices. This rapid evolution erodes the assumptions encoded in formal models, test suites, and architectural descriptions, leaving practitioners with limited guidance on how to keep verification artifacts aligned with evolving implementations. Prior surveys cover microservices design, deployment, performance, and isolated verification techniques, but, to our knowledge, none consolidate the intersection of evolution and formal/rigorous verification, nor map how repository-derived signals and CI/CD pipelines support continuous verification of microservice-based systems. This paper addresses that gap through a systematic literature review (SLR). Following the Kitchenham et al. guidelines and PRISMA-style reporting, we defined a review protocol with four research questions covering (i) formal modeling and verification approaches, (ii) the impact of architectural and API evolution on verifiability, (iii) repository-derived signals for updating formal artifacts, and (iv) continuous and incremental verification in CI/CD pipelines. Structured searches in IEEE Xplore, ACM Digital Library, SpringerLink, and Scopus returned 1187 records, which were screened in seven stages and reduced to 18 included studies (13 primary studies that supply evidence and five background studies retained for transparency and framing) through inclusion/exclusion criteria and a weighted 15-item quality-assessment instrument. We synthesized the included studies thematically and compared them along five dimensions: verification technique, evolution dimension, automation level, empirical evidence, and tool/artifact availability. The synthesis shows that actor-based model checking, TLA+ control-plane verification, static code analysis, continuous certification, and runtime/self-adaptive testing form five complementary clusters, but empirical evaluation is dominated by small academic case studies, only a minority of approaches automate model updates from repository signals, and few are integrated end-to-end into CI/CD. We discuss methodological limitations of the body of work, including a lack of industrial-scale validation and shared datasets, contrast intrinsic (build-time, model-driven) and extrinsic (recovery-based) verification strategies, and outline a research agenda toward repository-aware, pipeline-integrated verification for evolving microservices. The present synthesis distils a set of immediate, evidence-based actions for practitioners together with a focused agenda of open research challenges.
R. Gómez, Ebeid Elsayed, Enrique R. Zarate et al.· Software· 0 citations