CDN Mapping Cache for Multi-Source UI Data Retrieval

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern web applications face challenges in efficiently retrieving and combining datasets from various sources due to differing structuring and formatting techniques, requiring significant developer effort and impacting web page rendering times.

Innovation Solution

A system involving a content delivery network with a server-side cache, a mapping engine, and a data store is used to generate and cache mappings from multiple datasets, allowing for efficient data retrieval and rendering by determining cache hits or misses, and parsing mappings to serve data to browsers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data is retrieved from multiple different data sources, then data completeness and user experience are improved, but data normalization complexity and developer effort increase

Engineering Contradiction:
Improvedata completenessVSAvoiddata normalization complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a mapping engine as an intermediary component that automatically generates and maintains mappings between multiple data sources and the application's data model. This mapping layer acts as a mediator that handles data normalization automatically, eliminating the need for developers to manually normalize data from different sources. The mapping engine translates data from various sources into a unified format that the application can use directly.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements preliminary action by pre-generating mappings between data sources and the application model before runtime data retrieval. These mappings are created and stored in advance, allowing the system to quickly retrieve and combine data from multiple sources without performing complex normalization operations at request time. The mappings are cached and reused for subsequent data retrieval operations.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If data is retrieved and combined from multiple sources, then user experience is improved, but web page rendering time increases

Engineering Contradiction:
Improvedata availabilityVSAvoidweb page rendering time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-computing and caching mappings between data sources and the application model. When data is requested, the system checks if the required mappings are already cached and available, avoiding time-consuming data retrieval and normalization operations. The mapping engine prepares data combinations in advance, so that when the application needs data from multiple sources, it can quickly assemble the required information using pre-established mappings.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating and storing copy representations of data relationships in the form of mappings. Instead of repeatedly accessing and processing raw data from multiple sources, the system maintains cached copies of the mapping structures that define how data from different sources should be combined. These mapping copies enable fast data assembly without requiring actual data retrieval and processing from all source systems.

Inventive Principle:
Principle #26Copying

3Manufacturing precision

If developers manually normalize and combine datasets, then data integration accuracy is improved, but development time and resource allocation increase

Engineering Contradiction:
Improvedata integration accuracyVSAvoiddevelopment efficiency
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The patent implements self-service by enabling the mapping engine to automatically generate, maintain, and update mappings between data sources and the application model without requiring manual developer intervention. The system self-manages the data integration process by automatically discovering data relationships, creating appropriate mappings, and keeping them synchronized with changes in data sources. This automated self-service approach maintains high data integration accuracy while eliminating the time-consuming manual normalization work that previously required significant developer effort.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12524493B1Data aggregation layering
Publication Date: 2026.01.13 FANDUEL LTD
  • US12524493B1 patent drawing
  • US12524493B1 patent drawing
  • US12524493B1 patent drawing

AI summary

Systems, methods, and computer-readable media for fetching data associated with one or more mappings for rendering with a user interface. A method may include receiving a request from the browser for the data at the content delivery network, querying the server-side cache of the content delivery network to determine if the one or more mappings within the data is within the server-side cache, receiving information indicative of a cache hit or a cache miss from the server-side cache, if the information is the cache miss, retrieving the one or more mappings from the data store, parsing the one or more mappings to obtain the data; and serving the data to the browser for rendering the user interface.