Microservice Boundary Identification from Monolith Database Aggregates

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods for identifying microservices in monolith applications often result in incorrect decomposition, leading to distributed monoliths that lose their utility, necessitating a need for accurate analysis to decompose monolith applications into manageable microservices based on business capabilities.

Innovation Solution

A method and system that classify database tables as aggregate roots using parameters like entity relationship, foreign key references, entity size, datatypes, secondary indexes, and ACID transactions, and identify dependent tables and functions to generate cohesive microservices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If conventional techniques are used for microservice identification, then the decomposition process can be performed, but the identification accuracy deteriorates leading to incorrect microservices and distributed monoliths

Engineering Contradiction:

Improvemicroservice identification accuracyVSAvoiddecomposition quality

Core Design Contradiction:

Measurement precisionVSReliability

Solution Approach 1:

The patent segments the decomposition process into multiple phases: analyzing business capabilities, identifying aggregates, identifying microservices, and validating the decomposition. This structured segmentation ensures that each phase focuses on specific criteria, improving overall identification accuracy and preventing formation of distributed monoliths.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent incorporates validation as a feedback mechanism where the identified microservices are checked against business capability requirements and dependency relationships. This feedback loop allows correction of identification errors and ensures the decomposition produces reliable, functional microservices rather than incorrect distributed monoliths.

Inventive Principle:

Principle #23Feedback

2Adaptability or versatility

If the monolith application is decomposed into microservices, then scalability and development flexibility improve, but the complexity of the decomposition process increases

Engineering Contradiction:

Improvedevelopment scalabilityVSAvoiddecomposition process complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent employs automated analysis of business capabilities, aggregates, and dependencies to perform the decomposition process. The system self-determines microservice boundaries by analyzing the monolith's internal structure against defined business capabilities, reducing the need for manual intervention and simplifying the decomposition process while maintaining scalability.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent transforms the decomposition problem into parameter-based classification by analyzing multiple parameters such as business capability ownership, aggregate root relationships, and dependency graphs. By changing the approach from structural splitting to parameter-based identification, the complexity of determining microservice boundaries is significantly reduced.

Inventive Principle:

Principle #35Parameter changes

3Productivity

If microservices are identified based on technical capabilities, then the decomposition can be performed quickly, but the microservices lose business context and utility

Engineering Contradiction:

Improvedecomposition speedVSAvoidbusiness capability context

Core Design Contradiction:

ProductivityVSLoss of information

Solution Approach 1:

Instead of decomposing based on technical layers (database tables, API endpoints), the patent inverts the approach by first identifying business capabilities and then mapping technical elements to those capabilities. This inversion ensures that microservices are defined by business context rather than technical structure, preventing loss of business information while maintaining decomposition speed.

Inventive Principle:

Principle #13The other way round (Inversion)

Solution Approach 2:

The patent creates a universal decomposition framework that works across different monolith applications by using business capability models as a common reference. This universal approach allows the same methodology to be applied to any monolith, maintaining speed while preserving business context through standardized business capability analysis.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS12517930B2Method and system for identifying microservices in a monolith application

Publication Date: 2026.01.06 HCL TECH LTD

AI summary

The disclosure relates to method and system for identifying microservices in a monolith application. In an embodiment, the method may include classifying a Table of a plurality of Tables associated with a database of the monolith application as an aggregate root Table, and identifying one or more dependent-Tables associated with the aggregate root Table. The method may further include identifying one or more Functions associated with the aggregate root Table and each of the one or more dependent-Tables associated with the aggregate root Table, and generating a microservice by collating the aggregate root Table, the one or more dependent-Tables associated with the aggregate root Table, and the one or more Functions associated with the aggregate root Table and each of the one or more dependent-Tables associated with the aggregate root Table.