Peer-to-Peer Cloud State Management with Quorum Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional database systems for managing the state of cloud infrastructure face challenges such as disruptions leading to outages, incorrect configurations, missing data, and high load due to inefficient query optimization, especially in large distributed systems.

Innovation Solution

A peer-to-peer network is used to manage the state of cloud infrastructure, where each node maintains the complete state of the cluster, with changes verified by a consensus algorithm to ensure accuracy and security, and blocks are immutable to prevent errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a traditional centralized database system is used to manage cloud infrastructure state, then data consistency can be maintained, but the system becomes vulnerable to outages and high load issues

Engineering Contradiction:
Improvesystem resilienceVSAvoidquery performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The centralized database system is segmented into multiple distributed database nodes that operate in a peer-to-peer network. Each node maintains a portion of the cluster state and can independently serve queries, distributing the load while maintaining data consistency through consensus algorithms. This segmentation resolves the contradiction by improving both reliability (through distribution) and productivity (through load balancing).

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A consensus algorithm acts as an intermediary mechanism between distributed database nodes to coordinate state changes and maintain consistency across the network. The consensus protocol mediates between nodes during write operations, ensuring that all nodes agree on the state while allowing parallel read operations, thus maintaining both reliability and query performance.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If distributed database nodes are added to improve system resilience, then reliability increases, but device complexity and difficulty of managing state increases

Engineering Contradiction:
Improvesystem resilienceVSAvoidnetwork complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements feedback mechanisms where database nodes continuously monitor and report their state to the consensus algorithm. This feedback loop allows the network to automatically detect and respond to failures, maintaining reliability while reducing the complexity of manual state management. The consensus algorithm uses this feedback to coordinate state changes across nodes without requiring complex manual configuration.

Inventive Principle:
Principle #23Feedback

3Reliability

If complete state is replicated across all nodes in peer-to-peer network, then reliability and availability improve, but data synchronization and consistency become more difficult

Engineering Contradiction:
Improvedata availabilityVSAvoidstate consistency
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system performs preliminary actions by pre-synchronizing the complete state to all database nodes before any write operations occur. This preliminary state distribution ensures that all nodes have identical data available locally, improving availability and read performance. When state changes are needed, the consensus algorithm coordinates updates to maintain consistency, resolving the contradiction between availability and consistency.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12596586B2Managing state of distributed cloud environment in peer-to-peer network
Publication Date: 2026.04.07 SAP SE
  • US12596586B2 patent drawing
  • US12596586B2 patent drawing
  • US12596586B2 patent drawing

AI summary

In an example embodiment, rather than use a traditional database or datastore, or an ETCD database, to store the state of a cloud infrastructure management and orchestration system, a peer-to-peer network is used. The complete state of the cluster is available at every node. Nodes that are newly added to the system will fetch the current state from existing nodes. If the verification of the block is successfully performed by at least a quorum of the nodes, then the block is persisted as a new state on a node, and then distributed as a new state to every other node. The verification ensures that errors or possibly compromised nodes cannot persist incorrect changes to the system state.