Message Handling via Non-Persistent Storage Delay

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Message-oriented middleware systems face inefficiencies in handling guaranteed messages, as they often require persistent storage for reliability, which increases resource usage and reduces performance, especially when dealing with a large number of clients and messages.

Innovation Solution

Implementing a method where guaranteed messages are initially stored in non-persistent storage, with periodic removal as they are delivered, and then transferred to persistent storage after a dynamically determined delay interval, allowing for faster message handling and reduced resource usage by minimizing the need for persistent storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If guaranteed messages are stored in persistent storage to ensure reliability, then message integrity is improved, but resource consumption and processing speed deteriorate

Engineering Contradiction:
Improvemessage integrityVSAvoidmessage handling speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system dynamically switches between non-persistent and persistent storage based on message delivery status. Messages are initially stored in non-persistent storage for fast access, and only transferred to persistent storage if delivery fails or timing requires it. This dynamic storage strategy resolves the contradiction by providing fast message handling when possible while ensuring reliability only when necessary.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the storage parameter (from persistent to non-persistent) based on the delivery timing and system state. By adjusting the persistence parameter dynamically rather than using a fixed storage mode, the system achieves both high-speed message handling and guaranteed delivery reliability, resolving the trade-off between speed and reliability.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If guaranteed messages are immediately stored in persistent storage, then reliability is improved, but resource usage increases

Engineering Contradiction:
Improvemessage delivery guaranteeVSAvoidstorage resource usage
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

Instead of immediately persisting all guaranteed messages, the system applies partial persistence only when necessary. Messages are held in non-persistent storage first, and only transferred to persistent storage if the delay interval expires or delivery conditions require it. This partial action approach reduces unnecessary storage resource consumption while maintaining delivery guarantees.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system uses non-persistent storage (a cheaper, temporary storage medium) for guaranteed messages initially, replacing the need for immediate persistent storage. This allows the system to handle messages with minimal resource usage, only invoking expensive persistent storage when absolutely necessary to maintain reliability.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

3Productivity

If messages are held in non-persistent storage without delay, then processing speed is improved, but reliability deteriorates

Engineering Contradiction:
Improvemessage processing speedVSAvoidmessage delivery assurance
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system implements periodic checks and delayed persistence for messages in non-persistent storage. Instead of immediately persisting or immediately discarding messages, the system holds them temporarily and periodically evaluates whether to transfer to persistent storage based on timing intervals and delivery status. This periodic action maintains processing speed while periodically ensuring reliability.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system performs preliminary storage in non-persistent storage before final persistent storage. This preliminary action allows fast processing initially, with the option to perform a second persistence action if needed. The preliminary non-persistent storage phase maintains speed, while the potential follow-up persistent storage phase ensures reliability.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8516054B2Message handling
Publication Date: 2013.08.20 AUREA SOFTWARE
  • US8516054B2 patent drawing
  • US8516054B2 patent drawing
  • US8516054B2 patent drawing

AI summary

The disclosure includes a description of a method of handling messages received at a messaging system server. The method includes storing, in non-persistent storage, messages received from at least one client, removing delivered messages from the non-persistent storage, and saving messages stored in the non-persistent storage to persistent storage after a delay interval.