Adaptive Database Updates in Publish Subscribe Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Publish and subscribe systems face challenges in maintaining database consistency due to factors like connection stealing and server failures, leading to inefficiencies in update processing and potential duplicate client IDs, especially in distributed environments with high throughput.

Innovation Solution

A processor in a publish and subscribe system receives updates, generates optimistic updates, and adaptively updates the database using either bulk optimistic updates or read-modify-write sequences, switching between methods based on failure rates to ensure efficient and consistent database operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If read-modify-write sequences are used to update the database, then database consistency is maintained, but processing time and power consumption increase

Engineering Contradiction:
Improvedatabase consistencyVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system dynamically switches between read-modify-write sequences and bulk optimistic updates based on detected failure rates. When failure rates are low, bulk optimistic updates are used for faster processing; when failure rates exceed thresholds, the system transitions to read-modify-write sequences to ensure consistency, making the update strategy adaptive rather than static

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the parameter of update strategy based on the failure rate threshold. By monitoring failure rates and adjusting the update method parameter (either read-modify-write or bulk optimistic update), the system optimizes the trade-off between consistency and processing speed according to current system conditions

Inventive Principle:
Principle #35Parameter changes

2Productivity

If bulk optimistic updates are used to reduce processing time, then processing efficiency improves, but database consistency may be compromised

Engineering Contradiction:
Improveprocessing efficiencyVSAvoiddatabase consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system implements feedback by monitoring bulk optimistic update failure rates and using this information to adjust the update strategy. When failure rates exceed the threshold, the system responds by switching to read-modify-write sequences, creating a closed-loop control system that maintains consistency while maximizing efficiency when conditions permit

Inventive Principle:
Principle #23Feedback

3Reliability

If read-modify-write sequences are used for all updates, then database integrity is maintained, but power consumption increases

Engineering Contradiction:
Improvedatabase integrityVSAvoidpower consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system dynamically adjusts its update strategy based on monitored failure rates, switching between power-intensive read-modify-write sequences and more efficient bulk optimistic updates. This dynamic adaptation allows the system to maintain integrity when necessary while reducing power consumption when conditions allow for optimistic updates

Inventive Principle:
Principle #15Dynamics

4Productivity

If adaptive switching between update methods is implemented, then processing efficiency and consistency are optimized, but system complexity increases

Engineering Contradiction:
Improveprocessing efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The adaptive switching mechanism uses simple feedback based on failure rate thresholds to determine which update method to use. This feedback-driven approach optimizes efficiency and consistency without requiring complex decision-making logic, keeping the system relatively simple while achieving sophisticated adaptive behavior

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11526499B2Adaptively updating databases of publish and subscribe systems using optimistic updates
Publication Date: 2022.12.13 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11526499B2 patent drawing
  • US11526499B2 patent drawing
  • US11526499B2 patent drawing

AI summary

An example system includes a processor to receive updates for a database of a publish and subscribe system. The processor is to generate an optimistic update based on the received updates. The processor is also to adaptively update the database using the optimistic update. In some examples, the processor generates a bulk optimistic update based on the optimistic update and adaptively updates the database using the bulk optimistic update or a read-modify-write sequence.