Application Synchronization Service Delivery Guarantee

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing application synchronization services face challenges in ensuring reliable and efficient delivery of notifications about data modifications to subscribers without impacting end-to-end message delivery latency or throughput, and with minimal operational overhead, while maintaining quality of service and avoiding message failures.

Innovation Solution

A hierarchical distributed system utilizing parallelization and memory queues to manage notifications, coupled with a push notification service as a centralized failure queue, ensures level one quality of service compliance by reducing thread and memory contention and mitigating dependent service outages.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a push notification service is implemented to ensure reliable message delivery, then message delivery reliability is improved, but system complexity increases

Engineering Contradiction:
Improvemessage delivery reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a push notification service as an intermediary component between the application synchronization service and subscribers. This mediator handles the complexity of reliable message delivery (including retry logic, failure queues, and quality of service guarantees) independently, allowing the core application synchronization service to remain simple while achieving high reliability through the specialized notification service infrastructure.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If quality of service guarantees are implemented for message delivery, then message delivery success is improved, but message delivery latency increases

Engineering Contradiction:
Improvemessage delivery successVSAvoidmessage delivery latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-configuring quality of service levels and failure queue mechanisms before message delivery is needed. The push notification service is pre-established with retry logic and failure handling protocols in place, allowing messages to be delivered quickly when conditions permit while having backup mechanisms ready but not actively consuming time during successful deliveries.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If a hierarchical distributed system with parallelization is used to manage notifications, then operational overhead is reduced, but system complexity increases

Engineering Contradiction:
Improveoperational overheadVSAvoidsystem architecture complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The notification management system is segmented into a hierarchical distributed architecture with multiple independent components operating in parallel. Each node in the distributed system handles specific notification tasks independently, allowing the system to scale horizontally and reduce operational overhead through parallel processing while the modular segmentation manages complexity by isolating functions into discrete, manageable units.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12107934B1Delivery guarantee compliance for an application synchronization service
Publication Date: 2024.10.01 AMAZON TECH INC
  • US12107934B1 patent drawing
  • US12107934B1 patent drawing
  • US12107934B1 patent drawing

AI summary

Techniques for delivery guarantee compliance for an application synchronization service are described. In certain embodiments, a publishing service utilizes its memory queue to receive a request to publish a notification of a modification of a monitored data source from an application synchronization service, and then sends a success code to the application synchronization service based at least in part on the storing of the request to publish the notification in the memory queue. Embodiments herein are directed to a publishing service that delivers messages with a level one Quality of Service (QOS) that indicates that a message will be delivered one time at least.