Ingress Router Message Persistence for Low Latency Delivery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing message delivery systems face challenges in providing assured delivery with low latency and high throughput, especially in distributed networks, as they often require persistent storage at multiple hops, leading to increased latency and resource consumption.
Innovation Solution
A method where messages are stored locally at the ingress router until acknowledgments are received from all destinations, with no persistent storage required at intermediate routers, allowing for efficient routing and minimizing latency by removing messages from storage only after successful delivery.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If messages are persisted to non-volatile storage at each messaging hop to ensure assured delivery, then message delivery reliability is improved, but message latency and processing overhead increase significantly
Solution Approach 1:
The patent segments the message delivery responsibility by distinguishing between ingress routers (which perform persistence) and intermediate routers (which perform only forwarding). This segmentation allows the reliability function to be isolated to specific nodes, preventing the latency penalty from propagating through the entire message path.
Solution Approach 2:
The patent extracts the persistent storage requirement from intermediate messaging hops and concentrates it only at ingress routers. By taking out the storage burden from the forwarding path, messages can be routed efficiently through intermediate nodes without being blocked by disk I/O operations, thus reducing overall latency while maintaining delivery guarantees.
2Reliability
If messages are stored in non-volatile storage before sending acknowledgments, then message delivery assurance is improved, but system throughput decreases due to storage bottleneck
Solution Approach 1:
The patent applies preliminary action by having ingress routers persist messages to non-volatile storage before sending acknowledgments to message producers. This ensures that messages are safely stored prior to confirming delivery, maintaining reliability while allowing the system to process multiple messages in parallel through the distributed router network, thereby preserving throughput.
Solution Approach 2:
The patent uses copying by creating distributed copies of messages across the router network. Each router maintains local copies of routing information and message state, allowing parallel processing and acknowledgment of multiple messages simultaneously, which increases throughput while the ingress router's persistence ensures reliability.
3Adaptability or versatility
If a distributed network of messaging systems is used for scalable deployment, then system scalability is improved, but message latency increases due to multiple routing hops
Solution Approach 1:
The patent introduces intermediary routers that specialize in fast message forwarding without persistence operations. These intermediaries act as mediators between ingress and egress routers, enabling scalable distributed deployment while minimizing latency by eliminating storage operations from the forwarding path.
Solution Approach 2:
The patent applies local quality by assigning different functional characteristics to different router types: ingress routers have persistent storage capability for reliability, intermediate routers have optimized forwarding for speed, and egress routers handle delivery confirmation. This localized specialization allows the distributed system to scale while maintaining low latency through appropriate functional distribution.
Data Source
AI summary
In method of providing assured message delivery across a distributed message delivery system with low delivery latency and network traffic, a set of destinations is first identified for a set of destinations for a message received at an ingress router to the network. The received message is stored in persistent storage along with meta-data about each destination for the message before the message is routed to each identified destination. The message is only removed from persistent storage when an acknowledgement has been received from each destination indicating that the message has been successfully received.