Stream-Cut Event Annulment in Ordered Event Stream Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional ordered event stream (OES) systems face inefficiencies in removing inappropriate events, as traditional methods either require significant computing resources for copying events or result in unnecessary complexity by adding mitigating events, leading to suboptimal resource usage and stream complexity.

Innovation Solution

The system employs stream-cut events to reposition the write cursor, allowing for the annulment of events by overwriting inappropriate ones, either lossily or losslessly, using stream-cut events to update the write cursor position and manage event storage across segments, thereby reducing computational burden and stream complexity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional methods are used to remove inappropriate events by copying events, then data integrity is maintained, but computing resources are significantly consumed

Engineering Contradiction:
Improvedata integrityVSAvoidcomputing resources
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent extracts and removes inappropriate events from the event stream using stream-cut events that directly delete problematic events rather than copying the entire stream. This extraction approach eliminates the need for resource-intensive copying operations while maintaining data integrity through selective removal based on event identifiers and stream-cut boundaries.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system discards inappropriate events by using stream-cut events to annul them, and recovers storage resources by overwriting the space occupied by removed events with new events. This discarding and recovering mechanism reduces computing resources by avoiding the need to preserve and manage large volumes of inappropriate event data.

Inventive Principle:
Principle #34Discarding and recovering

2Reliability

If mitigating events are added to compensate for inappropriate events, then data integrity is maintained, but stream complexity increases

Engineering Contradiction:
Improvedata integrityVSAvoidstream complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Instead of adding mitigating events to compensate for inappropriate ones, the patent directly extracts and removes the inappropriate events using stream-cut events. This extraction approach maintains data integrity by eliminating the root cause rather than adding compensatory elements, thereby avoiding increased stream complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent inverts the traditional approach by removing inappropriate events directly rather than adding mitigating events to compensate for them. This inversion simplifies the stream structure by reducing the number of events that need to be tracked and managed, thereby decreasing stream complexity while maintaining data integrity.

Inventive Principle:
Principle #13The other way round (Inversion)

3Productivity

If the write cursor is repositioned using stream-cut events, then event annulment is achieved, but storage structure must be updated

Engineering Contradiction:
Improveevent annulment efficiencyVSAvoidstorage structure
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent uses stream-cut events that are prepared in advance with event identifiers and position information. When annulment is needed, the pre-prepared stream-cut events are applied to reposition the write cursor directly, achieving efficient event annulment without requiring complex real-time storage structure updates. The preliminary preparation of stream-cut events simplifies the annulment operation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The stream-cut event acts as an intermediary that mediates between the write cursor and the storage structure. Instead of directly updating the storage structure when repositioning the write cursor, the stream-cut event serves as a mediator that encapsulates the position information and annulment logic, simplifying the interaction and reducing the complexity of storage structure updates.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Use of energy by moving object

If lossy overwriting is used for event annulment, then computational overhead is reduced, but data integrity is compromised

Engineering Contradiction:
Improvecomputational overheadVSAvoiddata integrity
Core Design Contradiction:
Use of energy by moving objectVSReliability

Solution Approach 1:

The patent applies different annulment strategies to different events based on their local characteristics. Stream-cut events can specify whether to perform lossless or lossy overwriting for particular events, allowing the system to maintain data integrity for critical events while reducing computational overhead for less critical ones. This local quality approach enables selective application of annulment methods.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system changes the parameter of overwriting behavior from fixed to variable by using stream-cut events that can specify different annulment modes. This parameter change allows the system to dynamically adjust between lossless and lossy overwriting based on data integrity requirements, enabling flexible control over the trade-off between computational overhead and data integrity.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12099513B2Ordered event stream event annulment in an ordered event stream storage system
Publication Date: 2024.09.24 EMC IP HLDG CO LLC
  • US12099513B2 patent drawing
  • US12099513B2 patent drawing
  • US12099513B2 patent drawing

AI summary

Annulment of events written into an ordered event stream (OES) storage system is disclosed. Events can be written to one or more segments of an OES. An event can be invalid and overwriting the event can be desirable. A stream-cut event can be employed to facilitate annulment of the event via altering a portion of a segment of an OES. The stream-cut event can be durable. Annulment can avoid rewriting an entire stream and/or complicating a stream by adding mitigating events without overwriting invalid events. In an aspect, annulment can comprise moving a write cursor according to a stream-cut event. The annulment can be lossy or lossless. In an embodiment, annulment can be performed in single tier OES storage system. In another embodiment, multi-tier OES storage systems can facilitate annulment.