Distributed Directory Data Management via Backend Partitioning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern distributed directory systems face inefficiencies, inaccuracies, and inflexibilities in data management due to centralized management approaches, leading to increased latency and scalability issues as the system grows.

Innovation Solution

A distributed data management system is implemented, where data record management is relocated from a centralized cache to backend storage partition devices, allowing them to automatically manage metadata, resolve conflicts, and restore data in case of failures, thereby decentralizing data processing and enhancing system flexibility and reliability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a centralized directory server controls data management, then data distribution and request routing can be coordinated, but system latency increases and scalability is limited

Engineering Contradiction:
Improvedata management coordinationVSAvoidsystem latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the centralized directory server functionality into distributed directory servers, each managing its own data partitions independently. This eliminates the single point of coordination and reduces latency by allowing local decision-making at each directory server node.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a hierarchical dimension to data management, where directory servers operate at multiple levels (local and global). Local directory servers handle immediate routing decisions, while global coordination occurs asynchronously, reducing the time dimension for request processing.

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

2Reliability

If a centralized directory server manages all data routing, then request distribution can be controlled, but the system becomes inflexible and difficult to scale

Engineering Contradiction:
Improverequest routing controlVSAvoidsystem scalability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system segments routing control authority from the centralized server to individual directory servers. Each directory server can independently make routing decisions for its managed partitions, enabling the system to scale horizontally without requiring centralized reconfiguration.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic routing where directory servers can adapt their routing decisions based on current system state, load conditions, and data location. This dynamic behavior allows the system to scale flexibly while maintaining controlled request distribution.

Inventive Principle:
Principle #15Dynamics

3Productivity

If data is partitioned across multiple directory servers, then system capacity increases, but coordination overhead and management complexity increase

Engineering Contradiction:
Improvesystem capacityVSAvoidmanagement complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

Directory servers implement self-service mechanisms where each server autonomously manages its own data partitions, metadata, and routing tables. This eliminates the need for complex centralized coordination mechanisms while maintaining system capacity through independent server operations.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent merges the functions of data storage, metadata management, and routing decision-making into a single distributed directory server component. This consolidation reduces overall system complexity compared to having separate centralized controllers for each function.

Inventive Principle:
Principle #5Merging (Combining)

4Reliability

If a centralized cache manages data records, then data access can be coordinated, but the system lacks flexibility and requires additional resources for scaling

Engineering Contradiction:
Improvedata access coordinationVSAvoidadditional resources
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The centralized cache is segmented into distributed cache nodes across multiple directory servers. Each server maintains local cache data for its managed partitions, eliminating the need for a single large centralized cache and reducing resource requirements for scaling.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent transitions from a single-dimensional centralized cache architecture to a multi-dimensional distributed cache structure. Cache data is organized both locally at each directory server and globally across the system, enabling efficient data access without requiring additional centralized resources.

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

Data Source

PatentUS20240152528A1Distributing management of data management in a distributed directory system
Publication Date: 2024.05.09 MICROSOFT TECHNOLOGY LICENSING LLC
  • US20240152528A1 patent drawing
  • US20240152528A1 patent drawing
  • US20240152528A1 patent drawing

AI summary

The present disclosure relates to utilizing a distributed data management system to provide improved data management, redundancy, and reliability in distributed directory systems. To illustrate, a distributed data management system improves existing distributed directory systems by relocating and distributing the management of data records from a centralized cache device to the backend storage partition devices. In this manner, the backend storage partition devices become responsible for automatically pushing data record metadata and changes to the centralized cache device, which only passively redirects the incoming requests to the proper backend storage partition devices. Additionally, the backend storage partition devices automatically resolve conflicts and restore lost data if the centralized cache device or a backend storage partition device suffers from faults or device failures.