Virtualized Append-Only Storage Interface

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

User interfaces for append-only storage services are not well-suited for users, requiring them to select inefficient locations and offsets, and existing file systems do not abstract underlying hardware details, leading to inefficient resource management and operational inefficiencies.

Innovation Solution

A virtualized append-only storage system that abstracts underlying storage devices, allowing users to access append-only services regardless of the hardware type, with features like arbitrary data growth, trimming, and optimized storage allocation, enabling efficient resource utilization and cost savings.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a traditional file system interface is used for append-only storage, then users can access storage services, but users must manually select inefficient locations and offsets, leading to poor ease of operation

Engineering Contradiction:
Improveuser interface usabilityVSAvoidstorage operation efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

A virtualization layer is introduced as an intermediary between the user interface and the underlying storage devices. This layer translates high-level user requests into optimized storage operations, automatically managing locations and offsets without requiring user input. The virtualization layer acts as a mediator that both simplifies the user interface and optimizes storage efficiency simultaneously.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If physical storage device details are exposed to users, then storage operations can be performed, but resource management becomes inefficient and operational overhead increases

Engineering Contradiction:
Improveresource management efficiencyVSAvoidsystem operational complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The complex details of physical storage device management are extracted from the user interface and consolidated into a dedicated virtualization layer. This separation allows the system to hide intricate device-specific operations while maintaining efficient resource management capabilities. The virtualization layer absorbs the complexity of device interaction, presenting a simplified interface to users while optimizing storage operations internally.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If append-only storage is implemented without virtualization, then storage operations are straightforward, but the system cannot adapt to different hardware types and loses versatility

Engineering Contradiction:
Improvehardware compatibilityVSAvoidstorage system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The virtualization layer is designed to provide universal support for multiple storage device types including append-only devices, random-access devices, and storage class memory. A single virtualized interface can adapt to various underlying hardware configurations, allowing the system to maintain simplicity while gaining hardware versatility. The virtualization layer handles device-specific complexities internally, presenting a unified interface to users regardless of the underlying hardware.

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

Data Source

PatentUS11500822B2Virtualized append-only interface
Publication Date: 2022.11.15 MICROSOFT TECHNOLOGY LICENSING LLC
  • US11500822B2 patent drawing
  • US11500822B2 patent drawing
  • US11500822B2 patent drawing

AI summary

An interface is instantiated for receiving storage requests for storing data in a software-defined storage network using an append-only storage scheme. The interface receives requests that are agnostic of interfaces and hardware-specific details of the storage devices of the software-defined storage network. A request comprises an identifier of a data object to be stored in the software-defined storage network using the append-only storage scheme. Metadata is generated for the data object indicating that the data object is an append-only object; and the request is translated to instructions for storing the data object in the storage devices using the append-only storage scheme. The data object is stored at one of the plurality of storage devices based on the instructions. The metadata is updated to indicate a mapping between the data object and a stored location of the data object.