Session-Level Version Tokens for Read-Your-Writes Consistency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional distributed networking systems face inefficiencies and inaccuracies in data consistency, leading to slow-downs and outdated data responses due to mirroring latency and reliance on central repositories, particularly in applications like digital asset transactions.
Innovation Solution
Implementing a session-level user token system that generates and manages tokens to verify data consistency within a session, ensuring that client devices read the most up-to-date data by comparing version information across servers, thus avoiding global mirroring delays and central repository inefficiencies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is replicated to all servers before responding to requests, then data accuracy is guaranteed, but write throughput is bottlenecked
Solution Approach 1:
The patent segments the consistency verification process by introducing version tokens that are generated and propagated independently for each write operation. Instead of waiting for full replication, the system divides the consistency check into manageable version comparisons that can be performed locally at read servers, resolving the contradiction between ensuring data accuracy and maintaining write throughput.
Solution Approach 2:
The system performs preliminary actions by generating version tokens at the time of write operations and propagating them proactively to read servers. This preliminary version information allows read servers to verify data consistency independently without waiting for full replication completion, thus maintaining both data accuracy and write throughput.
2Reliability
If reads consult a central repository for version information, then data accuracy is guaranteed, but read throughput is bottlenecked
Solution Approach 1:
The patent extracts the version verification function from the central repository and embeds it directly in read servers through version tokens. Read servers now possess the necessary version information locally, eliminating the need to consult the central repository for each read operation. This resolves the contradiction by maintaining data accuracy through version verification while eliminating the read throughput bottleneck.
Solution Approach 2:
Read servers perform self-service by using locally cached version tokens to verify data consistency independently. Instead of relying on the central repository for each verification, read servers autonomously compare incoming data versions against their cached tokens, thereby maintaining data accuracy while significantly improving read throughput.
3Productivity
If writes do not wait for complete replication and reads do not consult central repository, then no bottlenecks are created, but data accuracy deteriorates
Solution Approach 1:
The patent introduces version tokens as intermediaries between write and read operations. These tokens carry version information that enables read servers to verify data consistency without consulting the central repository. This intermediary mechanism allows the system to operate without bottlenecks while maintaining data accuracy through efficient version verification.
Solution Approach 2:
The system changes the parameter of consistency verification from centralized query-based validation to decentralized token-based comparison. By transforming the verification mechanism into a local parameter comparison operation using version tokens, the system achieves both high throughput and data accuracy simultaneously.
Data Source
Figure 1
Figure 2A
Figure 2B
AI summary
The present disclosure relates to systems, non-transitory computer-readable media, and methods for consistently providing accurate versions of digital data within a distributed server network utilizing session-level user tokens. For example, in one or more embodiments, the disclosed systems generate a session-level user token that is specific to a client computing device participating in a session and in response to receiving a write request from the client computing device. As the client computing device initiates additional requests to read and write digital data from the distributed server network during the session, the disclosed systems maintain current version information within the session-level user token, and utilize this version information to verify that data provided to the client computing device from the distributed server network is accurate at the session-level.