Distributed API Gateway for Microservices Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing and scaling large numbers of APIs in microservices architectures is challenging due to the need for individual tuning and configuration of each API, leading to inefficiencies and complexity, especially when dealing with tens of thousands of APIs and millions of clients.

Innovation Solution

A distributed API gateway architecture is implemented, where common API functionalities are bundled into gateway nodes that provide a core set of functionalities such as rate limiting, caching, authentication, logging, and security, reducing duplication and improving scalability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If individual APIs are configured and tuned separately, then each API can be optimized for its specific functionality, but the time and effort required to set up, scale, and maintain multiple APIs increases significantly

Engineering Contradiction:
ImproveAPI functionalityVSAvoidAPI setup and maintenance time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent combines multiple individual API configurations into a single gateway node that hosts multiple APIs. This allows common functionalities like authentication, rate limiting, and logging to be shared across all APIs, eliminating redundant setup and maintenance efforts while preserving individual API optimization capabilities.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The gateway node is designed to host multiple APIs with different functionalities while providing a unified configuration management system. This universal platform allows administrators to manage diverse APIs through a single interface, reducing the time required to set up and maintain individual APIs.

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

2Ease of manufacture

If multiple servers are individually set up to host APIs, then each API can be independently deployed, but the complexity of managing and scaling the infrastructure increases

Engineering Contradiction:
ImproveAPI deploymentVSAvoidInfrastructure management complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent consolidates multiple API hosting functions into a single gateway node, reducing infrastructure complexity. Instead of managing separate servers for each API, the gateway node provides a unified platform that simplifies deployment while maintaining independent API lifecycles.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The gateway node architecture allows APIs to be segmented as independent services within a unified host. Each API can be independently deployed, configured, and scaled while sharing common infrastructure resources, balancing ease of deployment with reduced complexity.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If common functionalities are implemented in each individual API, then each API can operate autonomously, but code duplication increases and maintenance becomes more difficult

Engineering Contradiction:
ImproveAPI autonomyVSAvoidCode duplication
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts common functionalities such as authentication, rate limiting, and logging from individual APIs and implements them at the gateway node level. This eliminates code duplication across multiple APIs while preserving their autonomous operation through configuration-based control.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The gateway node provides universal support for common API functionalities that can be applied across multiple APIs. This multi-functional approach allows single implementation of common features that serve all APIs, reducing code duplication while maintaining individual API autonomy through configurable parameters.

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

Data Source

PatentUS20250175398A1Microservices application network control plane
Publication Date: 2025.05.29 KONG INC
  • US20250175398A1 patent drawing
  • US20250175398A1 patent drawing
  • US20250175398A1 patent drawing

AI summary

Disclosed embodiments are directed at systems, methods, and architecture for operating a control plan of a microservices application. The control plane corresponds with data plane proxies associated with each of a plurality of APIs that make up the microservices application. The communication between the data plane proxies and the control plane enables automatic detection of service groups of APIs and automatic repair of application performance in real-time in response to degrading service node conditions.