Collaborative Distributed Document Store with Fast-Forward Merge

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current document and key value stores lack collaboration capabilities at the item level with versioning and merging, as well as search capabilities at the system level, making it difficult to manage collaborative efforts effectively.

Innovation Solution

A system that defines user roles, utilizes downstream synchronization schematics, fast-forward merge techniques, and loose timestamp oriented versioning based on change-set management to enable collaborative distributed document stores with merge capabilities, versioning, context aware search, and geo redundancy, allowing for organized collaboration and data management across multiple users.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If downstream synchronization schematics and fast-forward merge techniques are implemented, then collaboration efficiency is improved, but system complexity increases

Engineering Contradiction:
Improvecollaboration efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system segments collaboration workflows into distinct operations (downstream synchronization, fast-forward merging, versioning) that can be independently managed and executed, reducing overall system complexity while maintaining high collaboration efficiency

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system uses copying mechanisms to create local replicas of document states for offline work, then synchronizes changes back to the central store using fast-forward merge techniques, enabling efficient collaboration without complex real-time conflict resolution

Inventive Principle:
Principle #26Copying

2Loss of information

If versioning capabilities and change-set management are implemented, then document history tracking is improved, but storage requirements increase

Engineering Contradiction:
Improvedocument history trackingVSAvoidstorage requirements
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The system applies local quality by storing complete version histories for frequently accessed documents while using change-set management (storing only differences) for less critical documents, optimizing storage usage based on document importance and access patterns

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system changes the storage parameter from storing complete document copies to storing only change-sets (differences between versions), significantly reducing storage requirements while maintaining full version history tracking capabilities

Inventive Principle:
Principle #35Parameter changes

3Reliability

If geo redundancy and high availability are implemented, then system reliability is improved, but data synchronization complexity increases

Engineering Contradiction:
Improvesystem reliabilityVSAvoiddata synchronization complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system introduces a centralized coordination layer that acts as an intermediary between geo-redundant nodes, managing synchronization protocols and conflict resolution, thereby simplifying the complexity of maintaining reliability across distributed locations

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10698957B1System, method, and computer program for managing collaborative distributed document stores with merge capabilities, versioning capabilities, high availability, context aware search, and geo redundancy
Publication Date: 2020.06.30 AMDOCS DEV LTD
  • US10698957B1 patent drawing
  • US10698957B1 patent drawing
  • US10698957B1 patent drawing

AI summary

A system, method, and computer program product are provided for managing collaborative distributed document stores with merge capabilities, versioning capabilities, high availability, context aware search, and geo redundancy. In operation, a system identifies at least one document for a plurality of users to collaborate work. The system defines user roles for the plurality of users associated with the at least one document, the user roles including at least one owner role and one or more viewer roles or contributor roles. The system utilizes downstream synchronization schematics, fast-forward merge techniques and easy versioning based on change-set management, and loose timestamp oriented versioning based on data branching to give an owner assigned to the at least one document an ability to invite collaborators to collaborate on work associated with the at least one document in a managed and organized manner via a collaborative distributed document store with merge capabilities, versioning capabilities, context aware search capabilities, high availability, and geo redundancy.