Blockchain Ledger Reconciliation for Enterprise Service Bus Failures

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing enterprise service buses face challenges in ensuring message delivery and consistency across distributed computing architectures and services, leading to potential inconsistencies and security vulnerabilities due to failures or malicious interventions.

Innovation Solution

Implementing a blockchain system with a distributed ledger that records messages, events, and actions across all nodes, allowing for reconciliation of versions and enhanced security through cryptographic hashing and node redundancy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a traditional enterprise service bus is used for message transmission, then the system structure is simple and ease of operation is maintained, but reliability deteriorates due to potential failures and lack of message delivery guarantees

Engineering Contradiction:

Improvemessage delivery reliabilityVSAvoidsystem structure complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a blockchain system as an intermediary layer between distributed services. The blockchain ledger records all message transmissions, receipts, and processing outcomes immutably. This intermediary ensures that even if the ESB fails, the message delivery status is preserved and can be reconciled, thereby improving reliability without fundamentally changing the ESB's operational simplicity

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements distributed copying of the message transmission record across multiple nodes in the blockchain network. Each node maintains a copy of the ledger, ensuring that message delivery information is replicated and preserved even if individual nodes or the ESB fail. This copying mechanism enhances reliability while keeping the system structure manageable through standardized blockchain protocols

Inventive Principle:

Principle #26Copying

2Adaptability or versatility

If message transmission is distributed across multiple computing devices, then adaptability improves, but inconsistency arises due to failures or malicious interventions

Engineering Contradiction:

Improvedistributed architecture flexibilityVSAvoidsystem state consistency

Core Design Contradiction:

Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent implements a feedback mechanism where the blockchain ledger continuously records and tracks message transmission status, receipt confirmation, and processing outcomes across distributed services. This creates a closed-loop system where any inconsistency can be detected and reconciled by comparing against the immutable ledger records, thereby maintaining system state consistency while preserving distributed architecture flexibility

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The patent performs preliminary recording of message transmission intent and expected outcomes in the blockchain ledger before actual message processing occurs. This preliminary action creates a reference state that can be used to verify and reconcile the actual system state afterward, ensuring consistency across distributed services while maintaining adaptability

Inventive Principle:

Principle #10Preliminary action

3Object-affected harmful factors

If traditional message recording is implemented, then device complexity is low, but security deteriorates due to vulnerability to manipulation and lack of audit trail

Engineering Contradiction:

Improvesecurity vulnerabilityVSAvoidsecurity infrastructure complexity

Core Design Contradiction:

Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The patent introduces a blockchain-based security intermediary that provides cryptographic verification, immutable audit trails, and tamper-evident recording of message transmissions. This intermediary layer enhances security by preventing manipulation and providing comprehensive audit capabilities without requiring fundamental changes to the ESB's core messaging functionality, thus limiting the increase in security infrastructure complexity

Inventive Principle:

Principle #24Intermediary (Mediator)

4Reliability

If blockchain reconciliation is implemented, then reliability improves, but productivity decreases due to additional verification steps

Engineering Contradiction:

Improvesystem consistencyVSAvoidmessage processing speed

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent implements partial blockchain verification where only critical message delivery milestones (transmission, receipt, processing completion) are recorded on the blockchain, rather than verifying every intermediate step. This selective approach maintains system consistency through blockchain's immutable ledger while minimizing the overhead impact on message processing speed, thus preserving productivity

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS11368416B2Reconciliation of a blockchain ledger during failures of an enterprise service bus

Publication Date: 2022.06.21 RED HAT LLC

AI summary

Enterprise messaging using a blockchain system. A method of the disclosure includes receiving, by a first node of a blockchain system of an enterprise service bus, a message transmitted by a second node of the blockchain system. The blockchain system may be to store a plurality of messages communicated via the enterprise service bus in a distributed ledger. The method also includes determining, by the first node, whether the first node should process the message. The method further includes processing, by the first node, the message in response to determining that the message should be processed by the first node. The method further includes updating the distributed ledger to indicate that the message has been processed by the first node.