Distributed Database Sequence Ranges for Low-Latency Unique IDs

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In distributed database management systems, efficiently generating unique sequence values is challenging due to the difficulty in coordinating sequence generation across multiple nodes.

Innovation Solution

A distributed database system that includes a default node maintaining global sequence state and router nodes generating sequence values within assigned ranges, allowing for scalable and fault-tolerant sequence generation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If sequence generation is coordinated across multiple nodes in a distributed database, then unique sequence values can be generated, but system complexity and coordination overhead increase

Engineering Contradiction:
Improveuniqueness of sequence valuesVSAvoidcoordination complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The sequence generation system is segmented into multiple independent sequence generators, each responsible for generating sequences within a specific range. Each node maintains local sequence state independently, eliminating the need for complex coordination while ensuring uniqueness through range partitioning. The sequence namespace is divided into multiple sequence identifiers that can be independently managed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The solution introduces an additional dimension of sequence identifiers to namespace sequences, allowing multiple independent sequence generations across different nodes. By adding the sequence identifier dimension, the system can generate unique sequences distributed across nodes without requiring complex inter-node coordination, as each node operates independently within its assigned namespace.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If sequence generation requires coordination across distributed nodes, then unique values can be ensured, but latency increases

Engineering Contradiction:
Improveuniqueness of sequence valuesVSAvoidsequence generation latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

By segmenting the sequence generation responsibility across multiple independent nodes, each node can generate sequences locally without waiting for coordination with other nodes. This segmentation eliminates coordination latency while maintaining uniqueness through proper range assignment and state isolation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Each sequence generator is self-sufficient, maintaining its own sequence state and generating values independently without requiring service from other nodes. The system achieves uniqueness through decentralized state management rather than centralized coordination, eliminating network round-trip delays.

Inventive Principle:
Principle #25Self-service

3Productivity

If sequence generation is distributed across multiple nodes, then scalability improves, but network traffic increases

Engineering Contradiction:
Improvesequence generation throughputVSAvoidnetwork traffic
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The solution extracts the coordination overhead from the sequence generation process by allowing each node to independently manage its own sequence state. Nodes only communicate when necessary for initial registration or state synchronization, rather than requiring continuous coordination traffic, thus reducing overall network traffic while maintaining scalability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Each node serves itself by maintaining local sequence state and generating values independently, eliminating the need for frequent inter-node communication. This self-service approach reduces network traffic to minimal levels required for initial setup and occasional state synchronization, while maintaining high throughput.

Inventive Principle:
Principle #25Self-service

4Device complexity

If centralized sequence generation is used, then coordination is simplified, but single point of failure risk increases

Engineering Contradiction:
Improvecoordination simplicityVSAvoidfault tolerance
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The sequence generation functionality is segmented across multiple independent nodes rather than centralized in a single point. Each node maintains its own sequence state and can continue operating independently if other nodes fail, providing fault tolerance while keeping coordination simple through independent operation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Each node has local knowledge of its assigned sequence range and state, making decisions independently based on local information. This local quality approach eliminates single points of failure while maintaining simple coordination rules, as each node operates autonomously within its designated scope.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12572533B1Sequence generation in a distributed database
Publication Date: 2026.03.10 AMAZON TECH INC
  • US12572533B1 patent drawing
  • US12572533B1 patent drawing
  • US12572533B1 patent drawing

AI summary

A distributed database receive a request to provide a sequence of unique values to one or more nodes of the distributed database. The distributed database stores an indication of a first range of the sequence of unique numbers on a first node of the distributed database, and provides a value within the first range in response to a query. The distributed database is caused to process the query using the value within the first range.