Logical Container Data Persistence via Symmetric Encoding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data persistence systems in container-based environments face challenges such as high latency, inefficiencies in data provisioning, and the need for complex storage solutions, which hinder the adoption of service-oriented storage models due to trade-offs between performance and resiliency, and result in increased costs and complexity.

Innovation Solution

The method involves creating a logical container dynamically defined to correspond to a storage device, where original or encoded data is processed, and metadata is calculated and updated to ensure data persistence across a persistence boundary, using a symmetric encoding technique for error correction and efficient data transport, allowing data to be persisted as information without relying on traditional storage containers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional storage containers are used to guarantee data persistence, then data reliability is improved, but system complexity and cost increase

Engineering Contradiction:
Improvedata persistenceVSAvoidstorage solution complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the persistence guarantee mechanism from traditional storage containers and relocates it to the data transport layer. Instead of relying on storage containers to provide persistence, the system uses encoded data streams with embedded checksums that can verify data integrity during transport, thereby separating the persistence guarantee function from the storage container.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary encoding layer that processes data before storage. This encoding layer adds checksums and verification mechanisms to data streams, acting as a mediator between the application layer and storage layer. The intermediary ensures data persistence guarantees without requiring complex storage container implementations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If traditional storage containers are used to ensure data persistence, then data reliability is improved, but performance latency increases

Engineering Contradiction:
Improvedata persistenceVSAvoiddata access latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary encoding of data with checksums before storage operations. By pre-processing data with verification mechanisms in place, the system avoids time-consuming verification operations during data access and retrieval, thereby reducing latency while maintaining persistence guarantees.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If service-oriented storage models are adopted, then adaptability is improved, but trade-offs between performance and resiliency become more complex

Engineering Contradiction:
Improvestorage model flexibilityVSAvoidperformance-resiliency trade-off complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal data transport mechanism that works across different storage backends and container environments. The encoding layer with checksums provides a single, unified approach to data persistence that adapts to various storage models without requiring complex configuration or multiple specialized solutions, thereby simplifying the performance-resiliency trade-offs.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS10248345B1Persisting data as information
Publication Date: 2019.04.02 COHESITY INC
  • US10248345B1 patent drawing
  • US10248345B1 patent drawing
  • US10248345B1 patent drawing

AI summary

Disclosed herein are methods, systems, and processes to persist data as information. A logical container is created. The logical container is dynamically defined to correspond to a storage device. Original data or encoded data written by an application container is received. If original data is received, encoded data is generated from original data. If encoded data is received, original data is generated from encoded data. Generating encoded data from original data, and original data from encoded data involves calculating original metadata for original data, and encoded metadata for encoded data. Encoded data or original data along with original metadata and encoded metadata is transported through the logical container past a persistence boundary. In response to transporting past the persistence boundary, a confirmation is received original data has been persisted.