Distributed Transaction State Reconciliation Across Microservices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional distributed architectures face challenges in maintaining synchronization among systems with multiple child workflows, leading to increased costs and delayed reconciliation that fails to prevent losses during transactions.

Innovation Solution

A reconciliation manager is introduced to monitor and manage transaction states across microservices, utilizing a rule engine state machine to detect and rectify state mismatches or violations by rolling back or restarting transactions based on business rules, ensuring immediate reconciliation and adherence to SLAs/SLOs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional end-of-day reconciliations are performed after assumed completion of all transaction steps, then system complexity is reduced, but losses that had already occurred during the workflow cannot be saved

Engineering Contradiction:
Improvetransaction consistencyVSAvoidreconciliation delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements continuous reconciliation that monitors and validates transaction states throughout the workflow execution, rather than waiting until end-of-day. This preliminary action detects state inconsistencies early in the process, allowing immediate correction before losses occur, thus resolving the contradiction between reliability and time loss.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system establishes continuous feedback loops where transaction states are constantly monitored and compared against expected states. When discrepancies are detected, the system immediately triggers reconciliation processes, creating a real-time feedback mechanism that prevents losses while maintaining system reliability without end-of-day delays.

Inventive Principle:
Principle #23Feedback

2Adaptability or versatility

If multiple child workflows are managed within a super workflow in distributed architecture, then system functionality is enhanced, but maintaining synchronization among systems becomes challenging and costly

Engineering Contradiction:
Improveworkflow functionalityVSAvoidsynchronization complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a central reconciliation service that acts as an intermediary between multiple child workflows and the super workflow. This mediator continuously monitors transaction states across all workflows, compares them against a rule engine state machine, and coordinates synchronization actions, thereby managing the complexity of maintaining synchronization across distributed systems while preserving workflow versatility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system dynamically adjusts reconciliation parameters and monitoring frequency based on transaction states and workflow progress. By changing parameters such as reconciliation intensity and state validation thresholds, the system manages synchronization complexity adaptively while maintaining the functionality of multiple child workflows within the super workflow structure.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20260003665A1Reconciliation method for transaction state machine in distributed environment
Publication Date: 2026.01.01 JPMORGAN CHASE BANK NA
  • US20260003665A1 patent drawing
  • US20260003665A1 patent drawing
  • US20260003665A1 patent drawing

AI summary

Aspects of the subject disclosure may include, for example, obtaining a first state associated with a first microservice that performs a first step in a distributed process comprising a plurality of steps, wherein the first step is one of the plurality of steps; obtaining a second state associated with a second microservice that performs a second step in the distributed process, wherein the second microservice is distinct from the first microservice, and wherein the second step follows the first step; reconciling the first state with first known action data to determine whether a first action indicated by the first state is verified as completed, resulting in a first determination; and reconciling the second state with second known action data to determine whether a second action indicated by the second state is verified as completed, resulting in a second determination. Other embodiments are disclosed.