Database Virtual Node State Machine for Protocol Bridging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database architectures with different protocols are not interoperable, making it costly and difficult to scale or reconfigure existing database systems to improve throughput and storage capacity without migrating data, as direct scaling or replacement requires significant infrastructure changes and expertise.

Innovation Solution

A method is introduced to bridge two databases with different architectures by maintaining a state machine representing a virtual node in the first database, allowing it to communicate according to its native protocol while accessing and updating data in a second database, thereby extending the capabilities of the first database without altering its infrastructure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a database system uses a specific database architecture with a native protocol, then it achieves reliable access to geospatially replicated data, but it becomes costly and difficult to scale or reconfigure to improve throughput and storage capacity

Engineering Contradiction:
Improvethroughput and storage capacityVSAvoidinfrastructure reconfiguration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a mediator component that translates between the first native protocol of the existing database architecture and the second native protocol of the scalable database architecture. This intermediary enables communication and data exchange between the two incompatible systems, allowing the existing database to leverage the scalability benefits of the second architecture without requiring complete reconfiguration or migration of the underlying infrastructure.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If the database architecture is reconfigured to use a different database system with better scalability, then throughput and storage capacity improve, but the cost and difficulty of reconfiguration increase

Engineering Contradiction:
ImprovescalabilityVSAvoidreconfiguration cost
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent segments the database system into distinct protocol layers, separating the existing database architecture from the scalable database architecture. By dividing the system into protocol translation components and data storage components, it enables selective adoption of scalable features without requiring complete system reconfiguration, thereby reducing reconfiguration costs while maintaining adaptability.

Inventive Principle:
Principle #1Segmentation

3Quantity of substance

If the existing database infrastructure is replaced with a new database architecture, then storage capacity and throughput increase, but data migration and infrastructure changes become necessary

Engineering Contradiction:
Improvestorage capacityVSAvoiddata migration time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The patent establishes a protocol translation layer in advance that enables the existing database to communicate with the scalable database architecture before complete migration. This preliminary action allows data to be progressively transferred and accessed across architectures without requiring complete data migration at once, significantly reducing the time loss associated with data migration while still achieving increased storage capacity.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11474846B2Controller for bridging database architectures
Publication Date: 2022.10.18 MICROSOFT TECHNOLOGY LICENSING LLC
  • US11474846B2 patent drawing
  • US11474846B2 patent drawing
  • US11474846B2 patent drawing

AI summary

A method of bridging a first database and a second database. The method includes maintaining a state machine representing a state of a virtual node in the first database, wherein the state of the virtual node conforms to a native protocol for native nodes of the first database, said native protocol of the first database differing from a foreign protocol of the second database. The method further includes receiving an incoming message for the virtual node from one of the native nodes according to the native protocol, and based on the incoming message, accessing the second database. The method further includes updating the state of the virtual node based on the incoming message according to the native protocol, and based on the state of the virtual node as updated, sending an outgoing message to one or more of the native nodes according to the native protocol.