Queue-Based Update Aggregation for Distributed Database Throughput

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed databases face issues with throughput limits and throttling due to frequent updates, leading to performance bottlenecks, increased latency, and reduced accuracy and reliability.

Innovation Solution

Implementing a queue-based system that aggregates update expressions before applying them to the database, using batch parameters to trigger aggregation, thereby reducing the number of updates and ensuring a single source for updates, thus maintaining throughput and precision.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If frequent updates are applied to the distributed database, then the database remains up-to-date with all changes, but throughput limits are exceeded and throttling occurs

Engineering Contradiction:
Improvedata update accuracyVSAvoiddatabase throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

Multiple individual update expressions targeting the same item are merged into a single aggregated update expression. The system groups update messages by item identifier and combines their update operations (such as incrementing counters or adding to sets) into one consolidated update, reducing the total number of database operations while preserving all data changes.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system performs preliminary aggregation of update expressions in a queue before applying them to the database. Update messages are collected, grouped, and combined in advance, so that when updates are applied to the database, they are already consolidated into efficient batch operations rather than individual frequent updates.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If multiple update expressions are applied separately to the same item, then each update is processed individually, but the number of operations increases causing latency and throttling

Engineering Contradiction:
Improveupdate processing simplicityVSAvoidupdate latency
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

Multiple separate update expressions are merged into a single aggregated update expression per item. The system combines operations such as incrementing counters, adding to sets, or modifying document fields into one consolidated update operation, reducing the number of round trips to the database and lowering latency.

Inventive Principle:
Principle #5Merging (Combining)

3Productivity

If update expressions are aggregated into batches, then the number of database operations is reduced improving throughput, but system complexity increases due to queue management

Engineering Contradiction:
Improvedatabase throughputVSAvoidupdate aggregation system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

An update aggregation queue serves as an intermediary component between update message sources and the distributed database. This queue manages the buffering, grouping, and aggregation of update expressions, handling the complexity of batch processing while presenting a simple interface for receiving updates and applying them to the database.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If frequent updates are sent to the distributed database, then all changes are captured, but throttling occurs reducing reliability

Engineering Contradiction:
Improveupdate application reliabilityVSAvoidthrottling
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

Multiple update expressions are merged into aggregated updates that capture all changes in fewer operations. By combining update operations for the same item (such as multiple increments or modifications to the same document), the system reduces the frequency of database writes while ensuring all changes are preserved, avoiding throttling conditions.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS20250265241A1Aggregating updates for a distributed database using a queue
Publication Date: 2025.08.21 CAPITAL ONE SERVICES LLC
  • US20250265241A1 patent drawing
  • US20250265241A1 patent drawing
  • US20250265241A1 patent drawing

AI summary

In some implementations, a device may receive a set of update expressions associated with updating one or more items in the distributed database. The device may store the set of update expressions in an input queue. The device may aggregate, based on a value of a parameter satisfying a threshold, the set of update expressions to obtain aggerated update values for respective items of the one or more items, wherein the aggregated update values are summed values indicated by update expressions, of the set of update expressions, for the respective items of the one or more items. The device may generate, for each item, an aggregated update expression that indicates an aggregated update value, of the aggerated update values, for that item. The device may update the one or more items in the distributed database using the aggregated update expression for each item.