Distributed Messaging Agents for ESB Reliability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Enterprise Service Bus (ESB) architectures rely on centralized message brokers, which can lead to single points of failure and bottlenecks, and are not scalable for large distributed networks, especially when handling XML messages that are large and machine-unreadable.

Innovation Solution

A fully distributed system and method for messaging that eliminates the need for centralized message brokers by using a plurality of agents to determine message addresses based on content and select transmission paths, enabling direct message transmission without relying on centralized components.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If centralized message brokers are used in ESB architecture, then message routing and delivery can be managed centrally, but single points of failure and bottlenecks occur, reducing system reliability and scalability

Engineering Contradiction:
Improvesystem reliabilityVSAvoidcentralized architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the centralized message broker functionality into multiple distributed agents that operate independently across the network. Each agent handles message routing and delivery locally, eliminating the single point of failure inherent in centralized architectures. The system divides the monolithic broker into modular, distributed components that can fail independently without compromising overall system reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts the centralization element (the centralized message broker) from the system architecture entirely. By removing this central component, the system eliminates the bottleneck and single point of failure. Message routing functionality is distributed across multiple agents rather than concentrated in a single broker, fundamentally changing the architectural paradigm from centralized to decentralized.

Inventive Principle:
Principle #2Taking out (Extraction)

2Productivity

If centralized message brokers are used, then message routing control is centralized, but bottlenecks occur that reduce messaging efficiency and throughput

Engineering Contradiction:
Improvemessaging throughputVSAvoidmessage delivery time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent segments the message routing workload across multiple distributed agents rather than concentrating it in a single broker. This distribution of workload eliminates bottlenecks and enables parallel message processing, significantly increasing overall messaging throughput. Each agent independently handles routing decisions for messages within its domain, preventing centralized bottlenecks.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces dynamic load balancing and adaptive routing capabilities where agents can dynamically adjust their behavior based on current system conditions. Messages can be dynamically routed through different paths and agents based on load, availability, and optimization criteria, enabling the system to adapt to changing conditions and maintain high throughput under varying workloads.

Inventive Principle:
Principle #15Dynamics

3Ease of manufacture

If XML messages are handled in centralized systems, then message processing can be performed, but the large size and machine-unreadable format of XML messages exacerbate the limitations of centralized architectures

Engineering Contradiction:
Improvemessage processing capabilityVSAvoidmessage size
Core Design Contradiction:
Ease of manufactureVSQuantity of substance

Solution Approach 1:

The patent segments large XML messages into smaller, manageable units that can be processed and transmitted more efficiently across the distributed network. This segmentation reduces the burden on individual agents and enables parallel processing of message components, mitigating the impact of large message sizes on system performance.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces intermediary components that facilitate efficient handling of XML messages in the distributed architecture. These intermediaries may include message brokers at the agent level, transformation services, and routing mechanisms that optimize XML message processing across the distributed system, reducing the overhead associated with handling large, complex XML structures.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9369382B2System and method for supporting messaging in a fully distributed system
Publication Date: 2016.06.14 ORACLE INT CORP
  • US9369382B2 patent drawing
  • US9369382B2 patent drawing
  • US9369382B2 patent drawing

AI summary

A system and method can support messaging in a fully distributed system. The fully distributed system includes a plurality of agents. An agent in the plurality of agents operates to determine an address for a message, wherein said address is determined at least partially according to a content of the message. Then, said agent can select a path to transmit the message according to said address, and send the message according to said path directly to said address.