RDMA Queues for Transactional Middleware Bottleneck Resolution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Transactional middleware systems face performance bottlenecks and latency issues when transferring messages between machines due to reliance on bridge processes, which can become single points of failure under heavy load and introduce long latency.
Innovation Solution
Implementing a transactional middleware system that uses Remote Direct Memory Access (RDMA) protocol for direct message transfer between local and remote machines, eliminating the need for bridge processes and enabling fast, low-latency communication through RDMA queues on high-performance networks like InfiniBand.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If bridge processes are used for message transfer between machines, then system compatibility and standard networking are maintained, but single-point bottlenecks and high latency occur under heavy load
Solution Approach 1:
The patent extracts the message transfer function from the traditional bridge process architecture and implements it directly through RDMA queues. By removing the bridge process as an intermediary, the system eliminates the single-point bottleneck while maintaining the essential message routing capability through direct queue-to-queue communication between machines.
Solution Approach 2:
The patent introduces RDMA queues as a new intermediary mechanism that replaces the traditional bridge process. These queues enable direct memory access between machines without requiring a central bridge process, thus maintaining the mediating function for message transfer while eliminating the bottleneck associated with single-point architecture.
2Ease of operation
If bridge processes handle message routing, then centralized control is achieved, but latency increases due to processing overhead
Solution Approach 1:
The patent implements self-service message transfer where each machine's RDMA queue independently handles its own message routing and transfer operations. Machines can directly send and receive messages through their queues without requiring centralized bridge process intervention, thus eliminating processing overhead and latency while maintaining operational simplicity through standardized queue interfaces.
3Stability of the object's composition
If traditional message queues are used, then system stability is maintained, but performance bottlenecks occur under heavy load
Solution Approach 1:
The patent replaces the traditional mechanical bridge process system with an RDMA-based direct memory access system. This substitution eliminates the need for complex message copying and processing through bridge processes, allowing direct memory-to-memory transfer between machines which significantly improves throughput while maintaining system stability through standardized queue interfaces.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A transactional middleware system can exchange messages between a local machine and a remote machine using Remote Direct Memory Access (RDMA) protocol to achieve short latency in a manner like a local message transfer. The transactional middleware machine environment can prevent single-point bottleneck. The transactional middleware machine environment comprises a first message queue associate with a server in a first transactional machine, wherein the server operates to be accessed using a queue address in the first message queue. The transactional middleware machine environment further comprises a second message queue associated with a client in a second transactional machine. The client operates to send a service request message to the server directly using the first message queue, and the server operates to receive the service request message from the first message queue and send a service response message directly to the client using the second message queue.