Federated API Manager Pattern Recognition

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cloud platform API federation approaches often result in hard dependencies between APIs, making it difficult to modify or update individual APIs without breaking the federated API, and require manual coordination, which limits flexibility and agility.

Innovation Solution

A federated API manager that automatically identifies patterns and common features across multiple APIs, maps them to a unified schema, and performs consistency checks to ensure compatibility, allowing individual APIs to evolve without breaking the federated API, through element extension, composition, and conflict resolution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual coordination is used to federate APIs, then compatibility can be ensured, but the process requires significant manual intervention and is not scalable

Engineering Contradiction:
ImproveAPI compatibilityVSAvoidmanual coordination
Core Design Contradiction:
ReliabilityVSExtent of automation

Solution Approach 1:

The system performs self-service through automated pattern recognition and schema generation. The federated API manager automatically identifies patterns across multiple APIs, generates unified schemas, and performs consistency checks without requiring manual coordination, while still ensuring compatibility through systematic validation processes

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The manual mechanical process of API federation coordination is replaced with an automated computational system. The federated API manager uses algorithmic pattern recognition, automated schema generation, and programmatic consistency validation to substitute the manual coordination process, maintaining reliability while eliminating manual intervention

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Stability of the object's composition

If hard dependencies are created between federated APIs, then consistency can be maintained, but individual APIs cannot be modified or updated without breaking the federated API

Engineering Contradiction:
Improvefederated API consistencyVSAvoidAPI flexibility
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The system segments the federated API into independent feature components rather than creating hard dependencies between entire APIs. Each API is broken down into discrete features that can be independently identified, mapped, and validated, allowing individual APIs to be modified while maintaining overall federated consistency through selective feature-level coordination

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements dynamic adaptability where the federated API structure can accommodate changes in individual APIs. Through automated pattern recognition and schema generation, the system dynamically adjusts to API modifications while maintaining consistency, allowing the federation to evolve without rigid hard dependencies that would prevent updates

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11803428B2Feature based application programming interface federation
Publication Date: 2023.10.31 SALESFORCE INC
  • US11803428B2 patent drawing
  • US11803428B2 patent drawing
  • US11803428B2 patent drawing

AI summary

Methods, apparatuses, and computer program products for feature based application programming interface (API) federation are disclosed. In some examples, a federated API manager may receive user input indicating source APIs including features for data processing. The federated API manager may identify elements forming one or more patterns from the features based on federation protocols. The federated API manager may identify federated operations based on the identified elements and federation operation rules. The federated API manager may generate a federated API schema based on the federated operation rules, and the federated API schema may expose the federated operations.