Intermediate Server for Database Update Mediation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for database synchronization are time-consuming and error-prone due to manual updates between distinct systems, and reconfiguring them for direct communication increases operational load.

Innovation Solution

An intermediate server retrieves and combines data from primary and secondary databases, presenting it to client devices for input and updates, determining synchronization with either server to minimize load on primary and secondary servers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If manual updates are used between distinct systems, then system complexity is reduced, but time consumption and error rate increase

Engineering Contradiction:
Improvesystem complexityVSAvoidtime consumption
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The patent introduces an intermediate server that acts as a mediator between the primary and secondary databases. This server receives data from one database, processes and validates it, then transmits to the other database. This intermediary approach eliminates the need for direct system reconfiguration while automating the update process, thereby reducing both time consumption and error rates without significantly increasing system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If systems are reconfigured to enable direct communication, then update speed improves, but operational load on systems increases

Engineering Contradiction:
Improveupdate speedVSAvoidoperational load
Core Design Contradiction:
SpeedVSUse of energy by moving object

Solution Approach 1:

The intermediate server handles all communication and data processing tasks, preventing direct interaction between the primary and secondary databases. This approach maintains faster update speeds compared to manual processes while distributing the operational load to the intermediate server, thereby protecting the primary and secondary systems from excessive load.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The intermediate server autonomously retrieves data from one database, validates it against predefined criteria, and automatically transmits updates to the other database without requiring manual intervention. This self-service capability accelerates the update process while managing system load efficiently through automated validation and error handling.

Inventive Principle:
Principle #25Self-service

3Device complexity

If manual updates are used, then system reconfiguration is minimized, but error rate increases

Engineering Contradiction:
Improvesystem reconfigurationVSAvoiderror rate
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The intermediate server serves as an automated intermediary that validates, transforms, and transmits data between databases according to predefined rules. This automation eliminates human errors associated with manual updates while maintaining simple system architecture. The server's validation logic ensures data integrity and consistency, significantly reducing error rates without requiring complex reconfiguration of the existing database systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11500902B2Method, system and apparatus for intermediating database updates
Publication Date: 2022.11.15 PERRY CURRIER
  • US11500902B2 patent drawing
  • US11500902B2 patent drawing
  • US11500902B2 patent drawing

AI summary

A method in an intermediate server of initiating updates to a secondary database based on activity in a primary database includes: retrieving primary data from a primary server hosting the primary database; retrieving secondary data from a secondary server hosting the secondary database; storing a combined data set including the primary data and the secondary data; responsive to receiving a request from a client device, presenting a portion of the combined data set to the client device; receiving, from the client device, input data associated with the portion of the combined data set and updating the combined data set in the memory; determining whether to synchronize the updated combined data set with at least one of the primary server and the secondary server; and when the determination is affirmative, selecting a subset of the combined data set for transmission to at least one of the primary and secondary servers.