Model Driven Microservices Development System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems for developing large-scale software applications are complex, time-consuming, and costly, with rigid legacy applications that struggle to incorporate modern technologies like IoT, cloud, and microservices, making it difficult to keep up with market trends and requiring significant maintenance.

Innovation Solution

A processor-implemented method and system that models microservices designs using component modelers, validates design consistency, generates codes, customizes them based on technologies, containerizes, and deploys applications, enabling efficient development and deployment of microservice applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If conventional systems are used for developing large-scale software applications, then application functionality can be achieved, but the development process becomes complex and time-consuming

Engineering Contradiction:
Improveapplication development speedVSAvoiddevelopment process complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent uses model-driven architecture where application models serve as templates that can be copied and instantiated multiple times. The models capture the essential structure and behavior of applications, allowing rapid replication across different domains and technologies without recreating everything from scratch.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system allows dynamic configuration of application parameters through model instantiation. By changing parameters such as technology stack, domain specifics, and deployment targets, the same base model can generate different applications, reducing development complexity while maintaining productivity.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If legacy applications are maintained, then existing functionality is preserved, but maintenance costs increase and adaptability to new technologies decreases

Engineering Contradiction:
Improveadaptability to new technologiesVSAvoidmaintenance cost
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent segments applications into reusable models and components that can be independently maintained and updated. This modular approach allows specific parts of legacy applications to be modernized without rewriting entire systems, reducing maintenance costs while improving adaptability to new technologies.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The model-driven approach enables dynamic adaptation of applications to new technologies. Models can be updated to incorporate new technological standards and requirements, allowing legacy applications to evolve continuously without complete reimplementation, thus reducing long-term maintenance costs.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If microservices designs are implemented across multiple applications, then technology modernization is achieved, but development coordination becomes more challenging

Engineering Contradiction:
Improveimplementation of modern technologiesVSAvoiddevelopment coordination complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates universal models that can be instantiated across multiple applications with different microservices designs. These models encapsulate common patterns and best practices for microservices development, enabling consistent implementation across diverse applications while simplifying coordination through standardized templates.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The model-driven architecture acts as an intermediary between development requirements and implementation details. Models serve as the mediating layer that translates high-level application requirements into coordinated microservices designs, reducing the complexity of direct coordination between multiple applications and their underlying services.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11354105B2Model driven system and method for development of micro service applications
Publication Date: 2022.06.07 TATA CONSULTANCY SERVICES LTD
  • US11354105B2 patent drawing
  • US11354105B2 patent drawing
  • US11354105B2 patent drawing

AI summary

Conventional methods for application development are rigid, complex, costly and ineffective in implementing new and changing technologies. The embodiments herein provide a model driven system and method for development of micro service applications. A set of user interface components and one or more domain components for a plurality of micro services designs of a plurality of applications pertaining to one or more technologies are modeled and validated. Further, a plurality of codes are generated according to the one or more modeled domain components of the plurality of micro services designs of the plurality of applications satisfying one or more requirements. The plurality of generated codes are further customized and validated to ensure design and code consistency. The plurality of customized codes are further containerized to provide a plurality of containerized applications which are deployed into a target deployment environment for execution using a plurality of configuration files.