Stateless File Sync Nodes With Separate State Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing file sync solutions lack direct access to hosted file endpoints for end-users or applications, and require state persistence across sync nodes, limiting scalability and resource management.

Innovation Solution

A system allowing client devices to directly access hosted file stores with stateless sync roles that maintain synchronization state separately, enabling scalable and efficient resource utilization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a hosted endpoint is used to sync files between endpoints, then file synchronization is enabled, but direct access to files is not possible and the endpoint serves only as an intermediate hub

Engineering Contradiction:
Improvedirect access to filesVSAvoidintermediate access layer
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent extracts the state maintenance functionality from the sync role, separating it into a dedicated state store. This allows the sync role to be stateless and focused solely on processing synchronization requests, while direct file access is enabled through the hosted endpoint without requiring the sync role to maintain file state.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a state store as an intermediary component that maintains synchronization state separately from the sync role. This mediator allows the stateless sync role to process requests while the state is persisted independently, enabling both direct file access and synchronization functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If sync state is persisted in the servicing node, then synchronization can be maintained, but the system cannot scale out as the process is tied to a specific node

Engineering Contradiction:
Improvesynchronization state maintenanceVSAvoidsystem scalability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the synchronization system into two independent components: a stateless sync role that processes requests and a separate state store that persists synchronization state. This segmentation allows the sync role to be stateless and horizontally scalable, while the state store maintains reliability through dedicated persistence.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent moves the state persistence from the horizontal dimension (servicing nodes) to a vertical dimension (dedicated state store). This dimensional change allows multiple sync roles to access the same persistent state without competing for node resources, enabling system scalability while maintaining synchronization reliability.

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

3Productivity

If multiple sync roles are used to handle requests, then resource utilization improves, but state management becomes complex if state is tied to specific roles

Engineering Contradiction:
Improveresource utilizationVSAvoidstate management
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent extracts state management from the sync role, allowing multiple stateless sync roles to handle requests without complex state coordination. The state is taken out and managed independently by the state store, simplifying role management and improving resource utilization.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS12627732B2Hosted file sync with stateless sync nodes
Publication Date: 2026.05.12 MICROSOFT TECHNOLOGY LICENSING LLC
  • US12627732B2 patent drawing
  • US12627732B2 patent drawing
  • US12627732B2 patent drawing

AI summary

Disclosed herein is a system and method to synchronize files from a hosted file system where the client endpoint devices have direct access to the files stored on a hosted file store. When the client desires to synchronize with the files stored on the hosted file store the process identifies a sync role that can process the request. The particular sync role does not need to maintain state with the client device or the file store. The state necessary for the processing of the synchronization process is maintained separate from the sync role such that any sync role in the system can pick up the requests and process the requests. Once the role has been selected the synchronization process proceeds as normal. As state is not maintained by the sync role multiple roles can process the request or two roles can handle different portions of the process.