Platform Usage Triggering via Event Subscription
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Developers in the application platform field face challenges in detecting specific events due to the lack of exposure through APIs, leading to inefficiencies and difficulties in maintaining polling systems.
Innovation Solution
A system and method for triggering on platform usage, which includes a transaction system, usage trigger database, trigger monitoring system, and trigger action processor, allowing for the creation of usage triggers and counter-based actions within a closed platform.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If polling systems are used to detect events, then developers can detect when events occur, but the system becomes time consuming and difficult to maintain
Solution Approach 1:
The patent introduces an event subscription mechanism where developers subscribe to specific events through a standardized interface, and the platform's event system acts as an intermediary to deliver events directly to subscribers. This eliminates the need for developers to implement complex polling systems while maintaining reliable event detection.
Solution Approach 2:
The patent replaces the mechanical polling approach (repeatedly checking for events at intervals) with an event-driven notification system where the platform proactively pushes events to developers. This substitution eliminates the inherent inefficiencies of polling while preserving event detection reliability.
2Adaptability or versatility
If all internal events are exposed through API, then developers can detect all events, but security and business reasons prevent full exposure
Solution Approach 1:
The patent implements selective event exposure where different events are made available to developers based on their permissions and the platform's security policies. Each event type can have different visibility and access controls, allowing the platform to expose only appropriate events to each developer while maintaining security.
Solution Approach 2:
The patent segments the event space into different categories with different access levels. Public events are available to all developers, private events require authentication, and sensitive events are restricted to platform operators. This segmentation allows comprehensive event detection coverage while maintaining security boundaries.
3Reliability
If polling systems are implemented by developers, then event detection is possible, but it is difficult to maintain
Solution Approach 1:
The patent implements a self-service event subscription model where developers automatically register their event interests through configuration files or code annotations. The platform's event system automatically manages the subscription lifecycle, including adding new event sources and removing obsolete ones, without requiring manual intervention for maintenance.
Data Source
AI summary
A system and method for triggering on platform usage can include at a platform, receiving and storing a trigger configuration of an account; operating a platform comprising internally executing a process on behalf of an account and publishing at least one event when executing the process; at the platform, incrementing a counter in response to the at least one event and if the stored trigger configuration species a usage key associated with a category of counted events of the at least one event; monitoring counters in a context of an associated trigger; and processing the trigger upon the counter satisfying condition of an associated trigger.