API Component Consolidation via Global Search Mediator

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The decentralization of computing tasks in cloud environments leads to difficulties in discovering and reusing application interface data components across isolated repositories, resulting in increased computational resource consumption and API development time, due to fragmented documentation and interoperability issues among disparate APIs.

Innovation Solution

An application interface integration design management platform that analyzes distinctive repositories to identify and consolidate application interface files and data components, creating a unified search capability for API components, thereby reducing redundancy and facilitating real-time access to up-to-date API documentation across multiple repositories.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If application interface data structures are distributed across distinctive repositories, then each repository can be independently managed and developed, but it becomes difficult to discover and reuse API components across repositories

Engineering Contradiction:
ImproveIndependent repository managementVSAvoidAPI component discoverability
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces a global search application as an intermediary layer between developers and distributed repositories. This mediator consolidates API component data from multiple repositories and provides unified search capabilities, enabling developers to discover and reuse components without needing to access each repository individually.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent adds a new dimensional layer (the global search application layer) above the distributed repository structure. This creates a virtual consolidation of repositories without physically merging them, allowing unified access while preserving independent repository management.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Adaptability or versatility

If each development team maintains separate API documentation in isolated repositories, then team autonomy is preserved, but computational resource consumption increases due to redundancy

Engineering Contradiction:
ImproveTeam autonomyVSAvoidComputational resource consumption
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent merges the search functionality across multiple repositories into a single global search application. Instead of each team maintaining separate documentation systems, the global search consolidates API component data from all repositories, eliminating redundant computational resources while preserving team autonomy in repository management.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The global search application serves as a universal access point for all repositories, providing a single multi-functional system that replaces multiple individual documentation systems. This reduces overall computational resource consumption while maintaining team independence.

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

3Adaptability or versatility

If API documentation is stored in fragmented repositories, then each repository can be independently updated, but accessibility of API documentation is reduced during repository outages

Engineering Contradiction:
ImproveIndependent repository updatesVSAvoidAPI documentation accessibility
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The global search application acts as a mediator that caches and provides access to API component data from multiple repositories. During repository outages, the global search can serve cached data, ensuring continued accessibility of API documentation while repositories maintain independent update capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system prepares for potential repository outages by maintaining a consolidated view of API components in the global search application. This beforehand cushioning ensures that even if individual repositories become inaccessible, developers can still access API documentation through the global search.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

4Ease of manufacture

If separate web pages are created for each API documentation, then each API can be documented independently, but information common to multiple APIs is omitted

Engineering Contradiction:
ImproveIndependent API documentationVSAvoidCommon API information
Core Design Contradiction:
Ease of manufactureVSLoss of information

Solution Approach 1:

The global search application provides a universal interface that aggregates API documentation from multiple sources. It enables developers to access both API-specific information and common information shared across multiple APIs through a single consolidated search system, eliminating information loss while preserving independent documentation capabilities.

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

Solution Approach 2:

The patent merges the information from multiple separate API documentation pages into a unified global search index. This combining allows the system to present comprehensive information including common elements shared across multiple APIs, while each API maintains its independent documentation structure.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11720418B2Distillation of various application interface data structures distributed over distinctive repositories to form a data source of consolidated application interface data components
Publication Date: 2023.08.08 STOPLIGHT INC
  • US11720418B2 patent drawing
  • US11720418B2 patent drawing
  • US11720418B2 patent drawing

AI summary

Various embodiments relate generally to computer software and systems, including a subset of intermediary executable instructions constituting an communication interface between various software and/or hardware platforms, and, more specifically, to an application interface integration design management platform configured to analyze distinctive repositories (e.g., version-control application-based repositories) and identify application interface files and data components to form a consolidated data source with which to perform a unified search (e.g., a global search) to implement different portions of various application interfaces in development of application program interfaces (“APIs”), and the like. For example, a method may include indexing portions of application interfaces disposed in distinctive repositories, extracting the portions of application interfaces for storage in a consolidated data storage to facilitate, among other things, a unified search operation over data derived from multiple repositories.