ML Microservice Generation via Layer-Based Code Mechanism

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The process of transforming a machine learning (ML) model into production-ready microservices or functions is time-consuming and requires multiple areas of expertise, involving cross-team collaboration and often results in vendor lock-in, sub-optimal performance, and difficulty in integrating with existing systems.

Innovation Solution

A layer-based code and artifact generation mechanism that automatically turns an ML model into fully functional, robust, and scalable microservices, along with CI/CD and deployment artifacts, annotates workloads with metadata for intelligent scheduling, and enables automated transformation across execution platforms, allowing for efficient deployment and integration with ERP systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual transformation of ML models into production microservices is performed, then model accuracy and performance are maintained, but development time and complexity increase significantly

Engineering Contradiction:
Improvemodel performanceVSAvoiddevelopment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system enables automated self-service transformation where the ML model and metadata automatically generate production-ready microservices without manual intervention. The code generation mechanism uses the ML model's metadata to autonomously create deployment configurations, container definitions, and integration code, eliminating the need for manual transformation while preserving model performance characteristics.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by capturing and storing comprehensive metadata about the ML model during its creation phase. This metadata includes performance characteristics, resource requirements, and operational parameters that are later automatically utilized to generate production microservices, eliminating the need for repeated manual analysis and transformation steps.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If automated code generation is used to transform ML models into microservices, then development time is reduced, but integration complexity with existing systems increases

Engineering Contradiction:
Improvedeployment speedVSAvoidintegration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system implements universal integration capabilities by generating standardized microservice code that can interface with multiple types of existing systems (ERP, CRM, legacy applications). The code generation mechanism incorporates universal communication protocols and adapter patterns that enable seamless integration across diverse system landscapes without requiring system-specific customization.

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

Solution Approach 2:

The system introduces intermediary components in the form of standardized adapters and interface layers that mediate between the generated microservices and existing enterprise systems. These intermediaries handle protocol translation, data format conversion, and compatibility management, simplifying integration while maintaining high deployment speed.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If cross-team collaboration is required for ML model deployment, then model robustness is improved, but coordination overhead and time consumption increase

Engineering Contradiction:
Improvemodel robustnessVSAvoidcoordination complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system merges previously separate responsibilities (data science, software development, DevOps, infrastructure) into a unified automated transformation process. By consolidating these functions into a single code generation mechanism that consumes ML model metadata and produces complete production artifacts, the system maintains model robustness while eliminating the need for complex cross-team coordination.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system segments the deployment process into distinct, independently manageable components: metadata extraction, code generation, configuration creation, and deployment orchestration. Each segment can be independently validated and executed, reducing coordination complexity while maintaining the comprehensive quality checks that ensure model robustness.

Inventive Principle:
Principle #1Segmentation

4Productivity

If vendor-specific platforms are used for ML deployment, then implementation speed is improved, but flexibility and portability decrease

Engineering Contradiction:
Improveimplementation speedVSAvoidplatform flexibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The system implements platform-agnostic code generation that produces vendor-neutral microservices capable of deploying to multiple cloud providers and execution environments. The generated code incorporates universal containerization standards and configuration formats that enable seamless portability across different platforms while maintaining implementation efficiency.

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

Data Source

PatentUS11586916B2Automated ML microservice and function generation for cloud native platforms
Publication Date: 2023.02.21 EMC IP HLDG CO LLC
  • US11586916B2 patent drawing
  • US11586916B2 patent drawing
  • US11586916B2 patent drawing

AI summary

One example method includes receiving, as an input, an ML pipeline definition, identifying a group of layers required to be created for the ML pipeline definition, for one of more of the layers, receiving input concerning one or more characteristics of the layer, creating the layers for which input has been received, and packaging the created layers with the ML pipeline definition to create a production-ready ML model.