Request Replication and Claims Manager for High Availability Data Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

High availability data processing systems face delays in processing orphan messages due to failures in message dispatchers without high availability features, leading to increased processing overhead and costs, despite efforts to implement fast recovery features.

Innovation Solution

A method and system that replicate service requests across multiple request processing components, with a claims manager ensuring only one component processes the request, preventing duplicate updates to a high availability data store, thereby reducing the impact of failures and maintaining data integrity without excessive processing overhead.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If message dispatchers are implemented without high availability features to reduce processing overhead, then processing overhead and costs are reduced, but delays occur in processing orphan messages when a dispatcher fails

Engineering Contradiction:
Improveprocessing overheadVSAvoiddelay in processing orphan messages
Core Design Contradiction:
Loss of energyVSLoss of time

Solution Approach 1:

The system segments the message processing function by separating the message dispatcher from the high availability data store. Multiple independent message dispatchers can operate in parallel, each handling messages independently. When one dispatcher fails, other dispatchers continue processing messages, eliminating the single point of failure while keeping individual dispatcher complexity low.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by implementing high availability features selectively at the data store level rather than requiring every message dispatcher to have full high availability capabilities. This allows the system to achieve overall high availability while keeping individual dispatcher components simple and low-cost.

Inventive Principle:
Principle #3Local quality

2Reliability

If comprehensive high availability features are implemented within the HADB system to ensure reliability, then data integrity and availability are improved, but significant processing overheads are incurred during normal request processing

Engineering Contradiction:
Improvedata integrityVSAvoidprocessing throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts the message dispatcher function from the HADB system, placing it in external application servers. This separation removes the processing overhead of high availability mechanisms from the message processing path, allowing messages to be routed and initially processed externally. Only critical data integrity operations within HADB maintain full high availability monitoring, thus improving overall throughput while preserving data integrity.

Inventive Principle:
Principle #2Taking out (Extraction)

3Loss of time

If multiple request processing components are used with request replication to reduce orphan message delays, then processing availability is improved, but duplicate updates to the data store may occur without proper coordination

Engineering Contradiction:
Improvedelay in processing orphan requestsVSAvoiddata consistency
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The patent introduces a coordination mechanism as an intermediary between multiple request processing components and the HADB system. This coordinator manages request replication and ensures that duplicate requests are properly handled and coordinated, preventing duplicate updates to the data store while allowing multiple components to process requests in parallel.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary actions by implementing request replication and coordination before requests reach the HADB system. The claims manager pre-coordinates request handling among multiple processing components, establishing which component will handle each request before processing begins, thus preventing duplicate updates while enabling parallel processing.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9767135B2Data processing system and method of handling requests
Publication Date: 2017.09.19 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US9767135B2 patent drawing
  • US9767135B2 patent drawing
  • US9767135B2 patent drawing

AI summary

In a method of the invention, a plurality of distributed service requestors input service requests, and the service requests are replicated to at least two of a plurality of request processing components that are located within a communication path between the requestors and the data store. The method also includes preventing any request processing component that has not successfully claimed the service request from processing the service request A first request processing component can claim responsibility for the service request; and the first request processing component can process its replica of the claimed service request, including accessing data within the data store. The method also includes preventing any of the plurality of request processing components from entering a duplicate claim to responsibility for the service request.