API Hub Synchronization for Independent Billing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems lack an efficient method to synchronize and manage calls to both public and private APIs independently, complicating user management and billing across different API hubs.
Innovation Solution
A method and apparatus for synchronizing a private API hub server with a public API hub server, enabling the generation and forwarding of API calls and responses, as well as computing and conveying performance metrics, to facilitate independent management and billing of APIs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a single hub server manages both public and private APIs, then API management is simplified, but user management and billing become complicated and cannot be handled independently
Solution Approach 1:
The system divides the API hub into separate public API hub server and private API hub server instances. Each server independently manages its own user authentication, API keys, and billing metrics. This segmentation allows independent control and customization for public and private APIs while maintaining separate user management and billing systems.
2Adaptability or versatility
If separate hub servers are used for public and private APIs, then independent user and billing management is enabled, but system complexity increases
Solution Approach 1:
Both public and private API hub servers implement a common framework that handles API request routing, metadata management, and performance metric collection. This universal architecture reduces complexity by reusing the same core components across both server types while allowing independent configuration for user management and billing.
3Device complexity
If all API calls are routed through one hub server, then centralized control is achieved, but performance monitoring and metrics collection become less accurate for specific API types
Solution Approach 1:
Performance metrics are collected and stored separately in the public API hub server and private API hub server. This segmentation enables precise measurement of performance specific to each API type (public or private) while maintaining centralized control through the coordinated operation of both servers. Each server tracks its own API call volumes, response times, and error rates independently.
Data Source
AI summary
A method, including receiving, by a first API hub server in communication with a set of private APIs and with a second API hub server that is in communication with a set of public APIs, metadata for the APIs, each of the APIs including one or more respective API calls. A request is received from a client computer to access a given endpoint of a given API, and using the metadata for the given API, an API call is generated. Upon determining that the given API includes a given private API the generated API call is conveyed to the given private API, and upon determining that the given API call includes a given public API, the generated API call is conveyed to the second API hub server. Finally, upon receiving a response to the conveyed API call, the response is forwarded to the client computer.