Predicting Fail-Over in Message-Oriented Middleware

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional message management approaches in message-oriented middleware systems fail to maintain data continuity during fail-over operations, leading to data duplicity and scalability issues when clients switch between clusters.

Innovation Solution

The implementation of a machine learning-based anomaly detection system that predicts fail-over events in message-oriented middleware systems, allowing for automatic data migration between clusters to prevent duplicity and ensure seamless message processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional message management approaches are used during fail-over operations, then system simplicity is maintained, but data duplicity occurs and message processing must be reprocessed from the beginning

Engineering Contradiction:
Improvedata continuityVSAvoidmessage reprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by detecting anomalies that precede fail-over events using machine learning techniques. By identifying patterns in MOM parameter values before the actual fail-over occurs, the system proactively migrates data and metadata to backup clusters in advance, ensuring continuity of message processing without reprocessing from the beginning.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates copies of data and metadata from the primary MOM system to backup clusters before fail-over occurs. This copying mechanism ensures that when fail-over happens, the backup cluster already possesses the necessary transaction state information and message offsets, eliminating the need for clients to reprocess messages from the beginning.

Inventive Principle:
Principle #26Copying

2Reliability

If data is migrated between clusters during fail-over, then data duplicity is prevented, but system complexity increases

Engineering Contradiction:
Improvemessage delivery consistencyVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system introduces an intermediary anomaly detection component that acts as a mediator between the MOM systems and the fail-over mechanism. This component processes MOM parameter values, detects anomalies using machine learning, and triggers automated data migration. By placing this intermediary layer, the system manages the complexity of inter-cluster data migration while maintaining message delivery consistency, as the intermediary handles the complex coordination of data copying and cluster communication.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If anomaly detection using machine learning is implemented, then fail-over prediction accuracy is improved, but processing complexity increases

Engineering Contradiction:
Improveanomaly detection accuracyVSAvoidprocessing complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The anomaly detection component performs self-service by automatically processing MOM parameter values and detecting anomalies without requiring external intervention. The machine learning model is trained on historical data and autonomously identifies patterns indicating impending fail-over events. This self-service approach improves anomaly detection accuracy while managing processing complexity through automation, reducing the need for manual monitoring and intervention.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11940886B2Automatically predicting fail-over of message-oriented middleware systems
Publication Date: 2024.03.26 DELL PROD LP
  • US11940886B2 patent drawing
  • US11940886B2 patent drawing
  • US11940886B2 patent drawing

AI summary

Methods, apparatus, and processor-readable storage media for automatically predicting fail-over of message-oriented middleware systems are provided herein. An example computer-implemented method includes obtaining one or more message-oriented middleware parameter values for at least a portion of multiple message-oriented middleware systems; detecting one or more fail-over-related anomalies associated with at least one of the multiple message-oriented middleware systems by processing at least a portion of the one or more message-oriented middleware parameter values using one or more machine learning techniques; and automatically migrating, based at least in part on the one or more detected fail-over-related anomalies, at least a portion of data associated with the at least one message-oriented middleware system associated with the one or more detected fail-over-related anomalies to at least one of the other of the multiple message-oriented middleware systems.