Browser Cache Synchronization for Database Data Access

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional systems face limitations in providing flexible and capable interfaces for system-based services, particularly in communicating data efficiently and reliably between system databases and browser-based services, such as HTML UIs and Adobe Flash applications.

Innovation Solution

Implementing mechanisms and methods for communicating data between a database and a cache, allowing for improved application quality and performance by identifying a database and a separate cache associated with a browser-based application, and synchronizing data between them using a cache module and API, such as SOAP, to maintain object-level caching and asynchronous refreshing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If data is stored only in a system database, then data consistency and reliability are maintained, but access speed and application performance deteriorate

Engineering Contradiction:

Improvedata access speedVSAvoiddata consistency

Core Design Contradiction:

SpeedVSReliability

Solution Approach 1:

The patent creates a copy of the database in the browser cache, allowing fast local access to data while maintaining the ability to synchronize with the original database. The cache stores a copy of the database structure and data, enabling rapid retrieval without constantly querying the remote database, thus resolving the contradiction between speed and reliability.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The system performs preliminary actions by pre-loading and caching database data in the browser before it is needed. This allows the application to access data immediately from the cache without waiting for database queries, improving access speed while maintaining data consistency through subsequent synchronization mechanisms.

Inventive Principle:

Principle #10Preliminary action

2Adaptability or versatility

If system-based services are used, then data reliability is maintained, but interface flexibility and visual capabilities deteriorate

Engineering Contradiction:

Improveinterface flexibilityVSAvoiddata consistency

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a cache module as an intermediary between the system database and the browser-based application. This intermediary layer provides the interface flexibility and visual capabilities needed for modern web applications while maintaining reliable data communication with the database through standardized APIs and synchronization mechanisms.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system replaces traditional mechanical database connection mechanisms with asynchronous communication patterns and event-driven architecture. This allows the interface to be more flexible and responsive while maintaining data reliability through automated synchronization and conflict resolution mechanisms.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

3Reliability

If frequent database queries are made, then data freshness is maintained, but system performance and response time deteriorate

Engineering Contradiction:

Improvedata freshnessVSAvoidsystem performance

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by caching database data locally in the browser, eliminating the need for frequent queries to maintain data freshness. The cache is updated asynchronously in the background, allowing the application to maintain high performance while ensuring data remains fresh through periodic or event-triggered synchronization.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

Instead of continuous or frequent database queries, the system uses periodic action through asynchronous synchronization mechanisms. The cache is updated at appropriate intervals or when changes occur in the database, maintaining data freshness without degrading system performance through excessive querying.

Inventive Principle:

Principle #19Periodic action

4Reliability

If real-time database synchronization is implemented, then data consistency is maintained, but communication overhead and processing complexity increase

Engineering Contradiction:

Improvedata consistencyVSAvoidcommunication overhead

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies partial action by synchronizing only the necessary data and metadata between the database and cache, rather than transferring entire datasets. This selective synchronization maintains data consistency for critical information while reducing communication overhead and processing complexity by focusing only on changed or required data elements.

Inventive Principle:

Principle #16Partial or excessive action

Solution Approach 2:

The system implements feedback mechanisms that monitor database changes and trigger selective synchronization only when necessary. This feedback-driven approach maintains data consistency by responding to actual changes rather than performing continuous synchronization, thereby reducing communication overhead and processing complexity.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS9111006B2System, method and computer program product for communicating data between a database and a cache

Publication Date: 2015.08.18 SALESFORCE INC

AI summary

In accordance with embodiments, there are provided mechanisms and methods for communicating data between a database and a cache. These mechanisms and methods for communicating data between a database and a cache can enable improved application quality and performance, enhanced client application interaction, increased system performance, etc.