Front-End Micro-Services Sharing One API Response Across Webpages

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Different webpages obtaining data from the same data source process it differently, leading to contradictory data and increased network overhead due to unnecessary updates, which compromises security and wastes processing resources.

Innovation Solution

Implementing front-end micro-services that perform a single API call to the data source, sharing the response among multiple instances, thereby reducing network overhead and conserving resources while ensuring data integrity and security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If each webpage performs separate API calls to obtain data from the same data source, then each webpage can process and display data independently, but network overhead increases and processing resources are wasted

Engineering Contradiction:

Improvedata processing independenceVSAvoidnetwork overhead

Core Design Contradiction:

ProductivityVSLoss of energy

Solution Approach 1:

Multiple webpage instances share a single API call response from the data source. The system merges the data retrieval operation into one unified request that serves multiple webpages, eliminating redundant network traffic while maintaining independent data processing capabilities for each webpage instance.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

A single API call response is designed to serve multiple webpage instances simultaneously. The data structure and response format are universalized to accommodate different webpage needs, allowing one response to fulfill multiple data retrieval functions across different webpages.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If each webpage processes data differently from the same data source, then each webpage can be customized for its specific function, but contradictory data appears on different webpages

Engineering Contradiction:

Improvewebpage customizationVSAvoiddata consistency

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary data validation and standardization at the data source before distributing data to multiple webpages. By establishing data consistency rules and validation logic in advance, the system ensures that all webpages receive verified, consistent data while still allowing custom processing afterward.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where webpage data processing results are monitored and compared against source data. When inconsistencies or contradictions are detected, the system can trigger corrective actions to realign data across webpages, ensuring ongoing data reliability while maintaining customization.

Inventive Principle:

Principle #23Feedback

3Reliability

If updates to a webpage trigger new calls to the data source, then the webpage data can be kept current, but more network overhead is generated

Engineering Contradiction:

Improvedata currencyVSAvoidnetwork overhead

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

Multiple webpage update requests are merged into a single API call. When any webpage needs data updates, the system consolidates all pending update requests and sends one unified call to the data source, maintaining data currency across all webpages while minimizing network overhead.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The system maintains continuous data synchronization by implementing a shared data cache that persists across webpage updates. Instead of triggering fresh API calls for each update, the system continuously serves updated data from the cache, reducing network overhead while keeping webpage data current through efficient cache refresh mechanisms.

Inventive Principle:

Principle #20Continuity of useful action

4Adaptability or versatility

If host applications can access and process data freely, then data can be manipulated for various purposes, but security is compromised and data tampering can occur

Engineering Contradiction:

Improvedata accessibilityVSAvoiddata tampering risk

Core Design Contradiction:

Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The system introduces an intermediary data validation layer between the data source and host applications. This intermediary verifies data integrity, enforces access controls, and prevents unauthorized tampering while still allowing legitimate data access and processing. The intermediary acts as a trusted mediator that maintains security without blocking legitimate data flows.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS20250278448A1Front-end micro-services that provide data consistency

Publication Date: 2025.09.04 CAPITAL ONE SERVICES LLC

AI summary

In some implementations, a user device may receive, from a web host, code associated with at least one webpage. The user device may initiate a plurality of instances of a micro-service using the code. The user device may perform a single application programming interface (API) call for a first instance in the plurality of instances. A response from the single API call is shared with remaining instances in the plurality of instances. The user device may render a plurality of web elements, corresponding to the plurality of instances, using the code and the response from the single API call. The user device may output the at least one webpage, including the plurality of web elements, to a user.