Microservice Generation Framework for Custom Service Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional cloud services systems do not provide a mechanism for custom development of services that can interact with standard services, limiting consumers' ability to utilize their own data and develop tailored analysis tools for industrial processes.

Innovation Solution

A multi-tenant custom microservice generation framework that allows consumers to develop and deploy custom microservices, integrating with standard services, using an integrated development environment, templates, deployment, debugging, and lifecycle management features, enabling interaction with existing microservices and proprietary data sources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional cloud services systems provide only standard services, then system simplicity and reliability are maintained, but consumer adaptability and customization capability are limited

Engineering Contradiction:
Improveconsumer customization capabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments services into standard microservices and custom microservices, allowing consumers to selectively use standard services or develop custom ones based on their specific needs. This segmentation enables adaptability without requiring complete system redesign, as consumers can choose to extend only the portions they need.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer (custom microservice generation framework) between consumers and standard services. This framework provides templates, deployment mechanisms, and integration interfaces that enable consumers to build custom services on top of standard ones, thereby enhancing customization capability while managing complexity through a structured approach.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If consumers can develop custom microservices, then service functionality and adaptability are enhanced, but development complexity and time requirements increase

Engineering Contradiction:
Improvetailored service functionalityVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system provides pre-defined templates and frameworks for custom microservices that are prepared in advance. Consumers can select from standardized templates (e.g., data processing, analysis, visualization) and customize them rather than building from scratch, significantly reducing development time while still achieving tailored functionality.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The custom microservice framework provides universal building blocks and reusable components that can be applied across different consumer needs. These universal templates can be adapted to multiple scenarios, reducing the time required for development by eliminating the need to recreate common functionality for each custom service.

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

3Adaptability or versatility

If custom microservices are integrated with standard services, then system functionality is enhanced, but integration complexity and compatibility challenges increase

Engineering Contradiction:
Improveservice integration capabilityVSAvoidintegration architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent ensures that both standard and custom microservices follow the same architectural patterns, communication protocols, and interface conventions. This homogeneity in service design allows custom microservices to integrate seamlessly with standard services without requiring special handling or complex adaptation layers, thereby reducing integration complexity.

Inventive Principle:
Principle #33Homogeneity

Solution Approach 2:

The system uses templates that replicate the structure and interfaces of standard microservices. By copying the same architectural patterns and communication mechanisms, custom services can be deployed and integrated in the same way as standard services, simplifying the integration process while maintaining full compatibility.

Inventive Principle:
Principle #26Copying

4Ease of manufacture

If a comprehensive development framework is provided, then ease of development is improved, but system complexity and resource requirements increase

Engineering Contradiction:
Improvemicroservice development easeVSAvoidframework complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

Instead of providing a complete development environment with all possible tools and configurations, the framework provides only the essential templates and mechanisms needed for microservice development. This partial provision of functionality reduces framework complexity and resource requirements while still making development easy for common use cases, allowing consumers to add complexity only when necessary.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11444852B2Microservice generation system
Publication Date: 2022.09.13 SAP SE
  • US11444852B2 patent drawing
  • US11444852B2 patent drawing
  • US11444852B2 patent drawing

AI summary

Systems and methods are provided for receiving, from a computing device, a selection of a template for a custom microservice and configuration parameters for the custom microservice, generating the template for the custom microservice using the configuration parameters, the template for the custom microservice comprising defined interfaces for accessing core microservices, defined integration points for integration with a system providing the core microservices, and stubs for custom components for the custom microservice, and providing the template for the custom microservice to the computing device, wherein custom components for the custom microservice are added to the template via the computing device using the stubs for the custom components. The systems and methods further provide for registering the custom microservice to be exposed to and accessed by a tenant with authorization to access the custom microservice along with the core microservices.