Control-Plane Data Management Connectivity via Proxy Services

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data management systems (DMS) face high latency and single points of failure due to the use of a single additional service at the control-plane for communicating between the taskchain controller and multiple node clusters.

Innovation Solution

Implementing direct communication between the taskchain controller of the control plane and multiple node clusters through the use of proxy services and service buses, which are directly accessible by the taskchain controller and route communications between the taskchain controller and the nodes of the node cluster.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a single additional service at the control-plane is used to communicate between the taskchain controller and multiple node clusters, then device complexity is reduced, but latency increases and single points of failure are introduced

Engineering Contradiction:
Improvecontrol-plane structureVSAvoidsystem reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments the control-plane communication architecture by introducing multiple independent communication paths through service buses and proxy services. Instead of a single centralized service, the system divides communication into multiple parallel channels that can operate independently, eliminating the single point of failure while maintaining manageable complexity through modular design.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces service buses and proxy services as intermediary components between the taskchain controller and node clusters. These intermediaries enable direct communication paths while providing isolation and fault containment, allowing the system to achieve both low latency and high reliability through mediated communication channels.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If a single additional service at the control-plane is used to communicate between the taskchain controller and multiple node clusters, then device complexity is reduced, but latency increases

Engineering Contradiction:
Improvecontrol-plane structureVSAvoidcommunication latency
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The patent segments the communication path into multiple parallel channels through service buses and proxy services. This segmentation enables simultaneous communication with multiple node clusters, reducing overall latency by eliminating the sequential bottleneck of a single centralized service while maintaining architectural simplicity through modular design.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a new communication dimension by implementing service buses that operate alongside traditional control-plane services. This multi-dimensional communication architecture allows tasks to be routed through optimal paths, reducing latency by providing alternative communication routes without increasing overall system complexity.

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

Data Source

PatentUS20250175526A1Reliable and high-performance connectivity between control-planes and data-planes for a data management system
Publication Date: 2025.05.29 RUBRIK INC
  • US20250175526A1 patent drawing
  • US20250175526A1 patent drawing
  • US20250175526A1 patent drawing

AI summary

Methods, systems, and devices for data management are described. A data management system may include a control-plane common to multiple customers, where customer data for each customer is stored on a private data plane (e.g., at a remote node cluster). Each node cluster includes a controller which manages the nodes of the node cluster. A taskchain controller of the control plane may directly communicate with the nodes of the multiple node clusters, for example, via respective proxy services hosted at the node controllers or via respective service buses. The taskchain controller may communicate a command to add a new node to the node controller, and the node controller may create a new node based on the command. Future communications (e.g., commands to perform data protection tasks such as backup or restore operations) may be routed to the node via the proxy service or a service bus.