Draft Lifecycle Management via Dynamic Lock Transition

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In stateless communication models, pessimistic locking approaches lead to stale locks and inefficient resource allocation, causing stale durable locks to consume enqueue server resources and destabilize the lock table, while optimistic locking may result in lost changes due to mismatched eTags, leading to unintended consumption of resources and potential data loss.

Innovation Solution

Implement a lifecycle service that manages draft documents by setting durable enqueue locks, monitoring inactivity, and transitioning between pessimistic and optimistic locking modes based on eTag verification and processor expiration, ensuring efficient resource allocation and minimizing data loss through notifications and timely lock releases.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If pessimistic locking is used to protect active documents from concurrent modifications, then data consistency is improved, but system resource consumption increases and productivity decreases due to stale locks

Engineering Contradiction:

Improvedata consistencyVSAvoidsystem throughput

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent implements dynamic lock management where the locking mode transitions from pessimistic to optimistic based on draft activation status. Active drafts hold pessimistic locks to ensure consistency, while inactive drafts release locks to improve throughput. This dynamic adjustment resolves the contradiction by adapting the locking strategy to the actual operational state of each draft.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system periodically checks and releases locks on inactive drafts through a lock cleanup mechanism. This periodic action prevents stale locks from accumulating, thereby maintaining high system throughput while still providing strong consistency guarantees when drafts are actively being modified.

Inventive Principle:

Principle #19Periodic action

2Reliability

If durable enqueue locks are set for active documents to prevent side effects, then data integrity is improved, but resource allocation efficiency deteriorates due to lock table consumption

Engineering Contradiction:

Improvedata integrityVSAvoidlock table resources

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The patent implements automatic lock release mechanisms that discard stale locks and recover lock table resources. When drafts are deactivated or expire, their associated locks are automatically released and removed from the lock table, preventing resource exhaustion while maintaining data integrity during active editing periods.

Inventive Principle:

Principle #34Discarding and recovering

Solution Approach 2:

The system employs feedback mechanisms through lifecycle services that monitor draft status and trigger lock release operations. This feedback loop ensures that locks are maintained only when necessary for data integrity and released promptly when no longer needed, optimizing resource allocation dynamically.

Inventive Principle:

Principle #23Feedback

3Productivity

If optimistic locking is used to allow concurrent draft modifications, then productivity is improved, but data loss risk increases due to eTag mismatches

Engineering Contradiction:

Improveconcurrent editing capabilityVSAvoidchange preservation

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent implements preliminary conflict detection by comparing eTags before committing draft changes. This preliminary action identifies potential conflicts early, allowing the system to prevent data loss by detecting when the active document has been modified since the draft was created, thus maintaining reliability while allowing concurrent editing.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system applies preliminary anti-action by preventing the commit of draft changes when eTag mismatches are detected. This preemptive measure blocks potentially conflicting updates before they can cause data loss, preserving data integrity while still enabling productive concurrent editing when no conflicts exist.

Inventive Principle:

Principle #9Preliminary anti-action

4Reliability

If exclusive drafts are used to prevent lock collisions, then data consistency is improved, but user collaboration capability deteriorates

Engineering Contradiction:

Improveconsistency during editingVSAvoidcollaborative editing support

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the editing process into exclusive draft creation phases and collaborative review phases. During active editing, exclusive locks ensure consistency, while the system architecture supports multiple users through draft sharing and review workflows. This segmentation allows the system to maintain consistency during critical editing operations while supporting collaborative capabilities overall.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS11308068B2Control systems for draft lifecycle

Publication Date: 2022.04.19 SAP SE

AI summary

A system includes identification of editing of an active document by a user, and, in response to the identified editing, setting of enqueue locks on the active document, creating a draft document corresponding to the active document and an enqueue context associated with the draft document, storing the enqueue context with the draft document and attaching the enqueue context to a request session, determining an eTag of the active document and storing the eTag with the draft document, and associating the user with the draft document as its exclusive user.