API Registry for Stable Microservice Redeployment Across Platforms

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing container platforms face challenges in efficiently deploying and managing microservices across multiple computing environments, particularly in maintaining stable service endpoints and generating compatible client libraries, while ensuring optimal deployment criteria such as security, availability, cost, and latency are met.

Innovation Solution

An API registry is integrated into the container platform, allowing services to be registered during development, which automatically generates client libraries and manages service endpoints, ensuring compatibility and optimal deployment based on predefined criteria, and dynamically updates bindings to maintain stable service calls.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If microservices are deployed across multiple computing environments, then service availability and flexibility are improved, but maintaining stable service endpoints and ensuring compatibility becomes more difficult

Engineering Contradiction:
Improveservice availabilityVSAvoidendpoint management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an API registry as an intermediary component that centralizes the management of service endpoints across multiple computing environments. The registry maintains a unified interface definition that mediates between clients and the distributed microservices, allowing endpoints to be relocated across environments without affecting service stability or compatibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If services are broken into multiple containerized microservices, then system flexibility and independent upgrading are improved, but deployment management and coordination become more complex

Engineering Contradiction:
Improveservice flexibilityVSAvoiddeployment management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by requiring service interfaces to be registered and defined in the API registry before deployment. This pre-registration establishes binding contracts between microservices, enabling independent development and upgrading of individual services while the registry ensures coordinated deployment across the distributed system.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If automatic client library generation is implemented, then development efficiency is improved, but system complexity increases

Engineering Contradiction:
Improvedevelopment efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent implements self-service by enabling the system to automatically generate client libraries from registered service interface definitions. The API registry extracts interface specifications and autonomously produces compatible client code libraries, eliminating manual code generation while managing the complexity through automated processes.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12450110B2Optimizing redeployment of functions and services across multiple container platforms and installations
Publication Date: 2025.10.21 ORACLE INT CORP
  • US12450110B2 patent drawing
  • US12450110B2 patent drawing
  • US12450110B2 patent drawing

AI summary

A method of distributing microservice containers for a service across a plurality of computing environments may include receiving a service that is built from a plurality of containerized microservices to be deployed in a container platform. The container platform may include a plurality of computing environments. The method may also include receiving a deployment criteria for deploying the service in the container platform; accessing characteristics of the plurality of computing environments; and deploying the plurality of containerized micro services across the plurality of computing environments based on the deployment criteria and the characteristics of the plurality of computing environments.