Cloud Transaction Failover With Message Reconciliation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Modern high-throughput transaction computing systems face significant resiliency and reliability challenges due to instability or outages in cloud-based environments, which can lead to transaction loss and poor customer experience.

Innovation Solution

A system and method for automatic transaction processing failover and reconciliation in a cloud-based environment, utilizing region affinity, event sourcing, traceability, and health monitoring to detect errors and initiate seamless failover with robust transaction reconciliation and error remediation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If cloud-based environment is used for high-throughput transaction processing, then processing speed and scalability are improved, but system reliability and transaction safety deteriorate due to instability and outages

Engineering Contradiction:

Improvetransaction processing throughputVSAvoidsystem availability

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The system divides the cloud environment into multiple independent regions, each capable of autonomous operation. This segmentation allows the system to isolate failures to specific regions while maintaining operational capacity in other regions, thereby preserving both high throughput and reliability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system establishes health monitoring mechanisms and failover protocols in advance, creating a cushion against potential failures. By proactively detecting region instability and automatically initiating failover before complete system failure occurs, the system maintains continuous transaction processing capability.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

2Reliability

If automatic failover switching is implemented, then system availability is improved, but transaction loss risk worsens due to potential message duplication or loss during region switching

Engineering Contradiction:

Improvesystem availabilityVSAvoidtransaction message loss

Core Design Contradiction:

ReliabilityVSLoss of information

Solution Approach 1:

The system implements comprehensive health monitoring that continuously feeds back region status information to the failover management mechanism. This feedback loop enables real-time detection of region instability and triggers appropriate failover actions only when necessary, preventing unnecessary switching that could cause message loss while ensuring timely failover when needed.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system maintains copies of transaction messages and state information across multiple regions. During failover, this copying mechanism ensures that no transaction data is lost, as the target region already possesses the necessary message copies to continue processing without interruption or duplication.

Inventive Principle:

Principle #26Copying

3Reliability

If health monitoring and automatic failover are implemented, then system resiliency is improved, but system complexity worsens due to additional monitoring and state management components

Engineering Contradiction:

Improvesystem resiliencyVSAvoidsystem architecture complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system implements self-service mechanisms where regions automatically monitor their own health status and autonomously initiate failover actions when instability is detected. This self-service approach eliminates the need for complex centralized monitoring and control mechanisms, reducing overall system complexity while maintaining high resiliency.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The health monitoring and failover management components are designed to be universal and multi-functional, serving multiple purposes including transaction routing, state synchronization, and error detection. This multi-functionality reduces the need for separate dedicated components, thereby reducing system complexity while achieving comprehensive reliability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Loss of information

If region affinity and event sourcing are used for failover, then transaction traceability is improved, but processing latency worsens due to additional monitoring and reconciliation steps

Engineering Contradiction:

Improvetransaction traceabilityVSAvoidprocessing latency

Core Design Contradiction:

Loss of informationVSLoss of time

Solution Approach 1:

The system performs preliminary actions by maintaining event sources and traceability information in advance during normal operation. When failover is needed, this pre-prepared information allows for immediate switching without requiring time-consuming data collection or analysis, thus preserving traceability while minimizing latency.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS12566681B2Automatic transaction processing failover and reconciliation

Publication Date: 2026.03.03 FMR CORP

AI summary

Automatic transaction processing failover and reconciliation in a cloud-based environment includes monitoring the processing of transaction messages to identify exception events and determining whether to initiate a failover switch based upon the identified exception events. When a failover switch is initiated, the system identifies a target cloud-based system instance for the failover switch, changes a state of the affected cloud-based system instance to prevent the affected instance from receiving transaction messages, changes a state of the target instance to receive transaction messages intended for the affected instance, and performs a replication check between databases. The system reconciles transaction messages stored in the database of the cloud-based system instance to identify anomalies.