Event Status Stream for Asynchronous Error Notification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Event recordation and distribution systems face challenges in detecting and notifying event producers of publication errors, leading to potential data loss due to network and equipment failures, as event consumers are often unaware of these failures, resulting in irretrievable data loss.

Innovation Solution

Implementing a mechanism within the event recordation and distribution system to track events using unique universal identifiers (UUIDs) and generate error notifications, allowing event producers to subscribe to a status stream for error information, enabling them to detect and correct publication failures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If event publishing is done asynchronously in a distributed system, then system throughput and scalability are improved, but event consumers become unaware of publication errors leading to data loss

Engineering Contradiction:
Improveevent publishing throughputVSAvoidevent publication reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where the event publisher subscribes to an event status stream that publishes status updates about event publication. When an event is published asynchronously, the publisher receives feedback through the status stream indicating whether the publication succeeded or failed, enabling error detection and re-publishing without blocking the asynchronous throughput

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent introduces an event status stream as an intermediary component between the event publisher and event consumers. This mediator publishes status information about event publication outcomes, allowing the publisher to monitor publication success without directly coupling with consumers or blocking the asynchronous publishing flow

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If event publication failures are not detected, then system complexity is reduced, but data loss occurs and system reliability deteriorates

Engineering Contradiction:
Improveerror detection mechanism complexityVSAvoidevent data loss
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The event publisher performs self-service error detection by subscribing to the event status stream and monitoring publication outcomes independently. The publisher autonomously detects failures and can re-publish events without requiring external intervention or complex centralized error management infrastructure

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system establishes event tracking and status publication in advance of potential failures. By pre-configuring the event status stream and subscription mechanism, the system is prepared to detect and respond to publication errors immediately when they occur, preventing data loss rather than reacting afterward

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11714694B2Error notification mechanism for streaming events
Publication Date: 2023.08.01 SALESFORCE INC
  • US11714694B2 patent drawing
  • US11714694B2 patent drawing
  • US11714694B2 patent drawing

AI summary

A method for failure event notification in an event recordation and distribution system. The method including monitoring each stage of processing of an event by an event publisher manager, detecting a failure of the event to publish in the event recordation and distribution system, and publishing an error event notification to a status stream in response to detecting the failure.