Asynchronous Database Command Forwarding Between Nodes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Database systems face inefficiencies in workload distribution between read-only and read-write nodes, requiring clients to manually divide requests, which can hinder performance and increase resource utilization burdens.

Innovation Solution

Implementing asynchronous forwarding of database commands allows read-only nodes to support both read and write requests, enabling them to forward write operations to read-write nodes, thereby eliminating the need for manual workload division and enhancing resource utilization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If read-only nodes are used to serve read requests, then read performance is improved, but write operations cannot be handled by these nodes

Engineering Contradiction:
Improveread performanceVSAvoidrequest type handling capability
Core Design Contradiction:
SpeedVSAdaptability or versatility

Solution Approach 1:

The patent implements multi-functionality by enabling read-only nodes to handle both read requests and write requests. The read-only node receives a write request, determines whether to forward it to a read-write node, and can execute the write operation locally if appropriate. This allows the same node type to serve multiple purposes, improving adaptability while maintaining read performance benefits.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Ease of operation

If clients manually divide requests between read-only and read-write nodes, then workload distribution is controlled, but system complexity increases and performance is hindered

Engineering Contradiction:
Improveworkload distribution controlVSAvoidrequest routing complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent implements self-service by enabling read-only nodes to autonomously determine whether to execute write requests locally or forward them to read-write nodes. The node automatically evaluates the write request and makes routing decisions without requiring client intervention or manual workload division, thereby reducing system complexity while maintaining operational ease.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If read-only nodes forward write requests to read-write nodes, then write operations are handled, but resource utilization efficiency decreases

Engineering Contradiction:
Improvewrite request handling capabilityVSAvoidresource utilization efficiency
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent applies partial action by having read-only nodes selectively forward only those write requests that cannot be executed locally, rather than forwarding all write requests. This partial forwarding approach allows the system to leverage local execution capabilities when available, improving resource utilization efficiency while still maintaining the ability to handle write operations through forwarding when necessary.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11816073B1Asynchronously forwarding database commands
Publication Date: 2023.11.14 AMAZON TECH INC
  • US11816073B1 patent drawing
  • US11816073B1 patent drawing
  • US11816073B1 patent drawing

AI summary

Database commands may be asynchronously forwarded between nodes of a database system. A read-only node may receive a request, such as a read request or write request, and determine that the request should be forwarded to a read-only node for performance. A thread that handles the request may forward the request to the read-only node and register a call-back event for a response to the request and be made available to perform other work. When the response from the read-write node is received, the call-back event may be triggered and return a response to the request using the same or different thread.