Portable Binary Federation Gateway for Browser-Based API Testing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional techniques for deploying and testing federated application programming interfaces (APIs) require costly cloud resources and involve complex resource provisioning, which is inefficient and resource-intensive, especially in development and testing environments.

Innovation Solution

Compiling the engine logic of the federation gateway service into a portable binary format, such as web assembly, for execution on client hosts like web browsers, eliminating the need for cloud-based compute resources and enabling testing and development without resource allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Power

If federated APIs are deployed on cloud-based compute resources, then the system can handle complex data aggregation and processing tasks, but the cost and resource provisioning complexity increase significantly

Engineering Contradiction:
Improvecompute capabilityVSAvoidresource provisioning complexity
Core Design Contradiction:
PowerVSDevice complexity

Solution Approach 1:

The patent compiles the federation gateway service engine logic into a portable binary format (WebAssembly) that can be copied and executed on client devices. This creates a local copy of the compute capability, eliminating the need for complex cloud resource provisioning while maintaining the same data aggregation and processing functions. The binary file contains the complete engine logic that can run independently on any compatible client device.

Inventive Principle:
Principle #26Copying

2Use of energy by moving object

If cloud resources are allocated for testing and development environments, then adequate computing power is available, but costs increase and resource management becomes burdensome

Engineering Contradiction:
Improvecompute resource availabilityVSAvoidcost
Core Design Contradiction:
Use of energy by moving objectVSLoss of energy

Solution Approach 1:

The patent enables client devices to self-serve by executing the federation gateway service locally through the portable binary format. Developers can run testing and development environments on their own devices without requesting cloud resources. The client device's own compute resources are utilized, eliminating the need for external cloud allocation and associated costs.

Inventive Principle:
Principle #25Self-service

3Power

If federated APIs are executed on remote servers, then processing power is sufficient for complex queries, but user interaction complexity and error rates increase

Engineering Contradiction:
Improveprocessing capabilityVSAvoiduser interaction simplicity
Core Design Contradiction:
PowerVSEase of operation

Solution Approach 1:

The patent extracts the federation gateway service engine from the remote server environment and embeds it directly into the client device via the portable binary format. This extraction brings the processing capability to the user's local environment, simplifying interactions by eliminating the need for complex remote server management and reducing errors associated with network-dependent operations.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS12493546B2Portable binary files for client side execution of federated application programming interfaces
Publication Date: 2025.12.09 SALESFORCE INC
  • US12493546B2 patent drawing
  • US12493546B2 patent drawing
  • US12493546B2 patent drawing

AI summary

A federation management service may receive, via a user interface of the federation management service, a first user input indicating a selection of a testing environment for testing a federated application programming interface (API). The federation management service may receive, in response to the first user input, a portable binary file for deployment in a web browser of a client host. In some examples, the portable binary file may include a first set of scripts for orchestrating query requests for the federated API and a second set of scripts for orchestrating communications between the web browser of the client host and the first set of scripts. The federation management service may then execute, within the web browser of the client host, a query of the federated API using the first set of scripts and the second set of scripts.