Lambda Algorithm for Cloud Data Stack Notification Automation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The determination of the creation date of electronic records and generation of notifications associated with these records in a cloud computing environment is inefficient, leading to a reduction in notifications and resource utilization within a given period.
Innovation Solution
A computer-based method and system that utilize a lambda algorithm to determine utilization duration metrics for data stacks, retrieve metadata associated with creators, and automatically generate notifications based on these metrics, with the option to delete inactive data stacks, employing creator-specific resource-specific tags and a cloud watch rule engine.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If manual determination of creation date and notification generation is used, then flexibility and customization are maintained, but productivity and efficiency are reduced
Solution Approach 1:
The system performs self-service through automated lambda algorithms that continuously execute to determine utilization duration metrics and generate notifications without human intervention. The cloud watch rule engine automatically triggers notifications based on predetermined time periods, eliminating the need for manual tracking and notification generation while maintaining systematic control.
Solution Approach 2:
The system implements preliminary action by establishing cloud watch rules and lambda algorithms in advance with predetermined notification time periods. Creator-specific resource-specific tags are generated beforehand with indicative markers including start times, enabling the system to automatically calculate utilization durations and trigger notifications at appropriate intervals without real-time manual intervention.
2Productivity
If automated lambda algorithms are implemented, then productivity and resource utilization are enhanced, but device complexity increases
Solution Approach 1:
The patent introduces cloud watch rules as an intermediary layer between resource creation and notification generation. The rules engine acts as a mediator that automatically triggers lambda algorithms based on predetermined conditions, simplifying the overall system architecture by decoupling the notification logic from direct resource management while maintaining automated functionality.
Solution Approach 2:
The system segments notification generation into discrete lambda algorithms that can be independently executed and managed. Each algorithm handles specific resource types or time periods, allowing for modular development, testing, and maintenance. This segmentation reduces complexity by breaking down the monolithic notification system into manageable, reusable components.
3Measurement precision
If continuous automated execution of lambda algorithms is performed, then measurement precision of utilization duration is improved, but use of energy increases
Solution Approach 1:
The system implements periodic action by configuring cloud watch rules to trigger lambda algorithms at predetermined time intervals rather than continuously. Notification time periods are set in advance, causing the system to evaluate utilization durations only when needed, thereby maintaining measurement precision while significantly reducing computational energy consumption compared to continuous execution.
Data Source
AI summary
A method receiving an indication of a creation of at least one data stack of a plurality of data stacks within a cloud computing environment; generating at least one creator-specific resource-specific tag, identifying at least: an identity of the creator and a start time when the at least one resource has been associated with the at least one data stack; associating the at least one creator-specific resource-specific tag with the at least one resource; continuously and automatically executing a lambda algorithm to determine each utilization duration metric of each resource of each data stack of the plurality of data stacks; dynamically determining the plurality of data stacks to retrieve metadata associated with the identity of the creator associated with the at least one data stack; and automatically generating a notification associated with the at least one data stack at a predetermined period of time.