Segmented Database Architecture for Configuration Integrity

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional systems that store real-time data values and configuration data values in a single record structure face issues such as unnecessary integrity updates and performance degradation due to the lack of separation between these data types, leading to critical operations being treated with the same importance as non-critical ones.

Innovation Solution

A database architecture is segmented into separate real-time and configuration segments, allowing for transactional integrity of configuration data and providing a logical transactional unit for changes, ensuring that real-time data and configuration data are treated uniquely and updated independently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If real-time data values and configuration data values are stored in a single record structure, then data access is simplified, but transactional integrity of configuration data cannot be ensured and unnecessary integrity updates occur

Engineering Contradiction:

Improvedata access simplicityVSAvoidtransactional integrity of configuration data

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The database is segmented into separate real-time and configuration segments, each with independent versioning and locking mechanisms. This allows configuration data to maintain transactional integrity through version comparison while real-time data continues to be accessed efficiently, resolving the contradiction between data access simplicity and configuration reliability

Inventive Principle:

Principle #1Segmentation

2Device complexity

If real-time data values and configuration data values are stored in a single record structure, then storage structure is simplified, but performance degrades due to unnecessary integrity updates

Engineering Contradiction:

Improvestorage structure complexityVSAvoidsystem performance

Core Design Contradiction:

Device complexityVSProductivity

Solution Approach 1:

By segmenting the database into separate real-time and configuration segments, the system avoids unnecessary integrity updates on configuration data during real-time operations. Configuration updates only trigger integrity checks when actually modified, eliminating wasted processing cycles and improving overall system performance while maintaining manageable storage structure complexity

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system dynamically manages different segments with different update frequencies and integrity requirements. Real-time data segments allow frequent updates without integrity checks, while configuration segments perform integrity verification only when configuration changes occur, optimizing performance based on actual data modification patterns

Inventive Principle:

Principle #15Dynamics

3Device complexity

If real-time data values and configuration data values are stored in a single record structure, then data structure is simplified, but versioning cannot be properly implemented

Engineering Contradiction:

Improvedata structure complexityVSAvoidversioning capability

Core Design Contradiction:

Device complexityVSReliability

Solution Approach 1:

The database is divided into separate real-time and configuration segments, each with its own versioning mechanism. Configuration segments maintain version information to enable proper versioning and rollback capabilities, while real-time segments focus on current state storage, resolving the contradiction between data structure simplicity and versioning capability

Inventive Principle:

Principle #1Segmentation

4Ease of operation

If real-time data values and configuration data values are stored in a single record structure, then locking granularity is reduced to single record level, but critical operations cannot be prioritized

Engineering Contradiction:

Improvelocking granularityVSAvoidoperation prioritization capability

Core Design Contradiction:

Ease of operationVSProductivity

Solution Approach 1:

The database is segmented into separate real-time and configuration segments with independent locking mechanisms. This enables fine-grained locking at the segment level, allowing critical real-time operations to acquire locks on real-time segments while configuration operations lock configuration segments, enabling operation prioritization without complicating the locking model

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS11144532B2Transactional integrity in a segmented database architecture

Publication Date: 2021.10.12 AVEVA SOFTWARE LLC

AI summary

Providing separate real-time and configuration segments in a database. The real-time segment provides real-time data values to a real-time application and the configuration segment provides configuration data values to the real-time application. Utilizing two or more configuration segments enables changes to configuration data values without impacting real-time applications.