Dual-Queue System for Dynamic Data Resource Scaling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Data server systems face challenges in optimizing data operations as the size and complexity of data repositories grow, with added system resources often failing to achieve desired performance improvements and incurring undesirable costs and overhead.
Innovation Solution
The implementation of a dual-queue system that dynamically instantiates nodes and migrates between multi-tenant and single-tenant configurations, utilizing ephemeral data storage and queue management to optimize resource allocation and scalability, allowing for cost-effective and performance-efficient data processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If additional system resources are added to improve data operation performance, then processing capacity increases, but cost and overhead increase
Solution Approach 1:
The patent implements dynamic queue nodes that can be instantiated and terminated based on real-time data flow conditions. When data volume increases, additional queue nodes are automatically created to handle the load; when data volume decreases, nodes are terminated to free resources. This dynamic adaptation resolves the contradiction by making system resources flexible rather than static, allowing the system to scale up only when necessary.
Solution Approach 2:
The patent creates a unified queue management system where a single queue node can serve multiple functions: handling data ingestion, performing data operations, and managing data egress. The system can dynamically allocate these functions across multiple nodes based on workload requirements. This multi-functionality allows the system to achieve high processing capacity without proportionally increasing the number of dedicated components for each function.
2Quantity of substance
If data repository size and complexity grow to handle more data, then data capacity increases, but system performance optimization becomes more difficult
Solution Approach 1:
The patent segments the data repository into multiple independent queue nodes, each handling a specific portion of the data load. Each queue node is a self-contained unit with its own data structures and processing logic. This segmentation allows the system to scale data capacity by adding more segments (nodes) rather than increasing the complexity of a single monolithic system, resolving the contradiction between data capacity and system complexity.
Solution Approach 2:
The patent introduces a queue manager as an intermediary component that coordinates between multiple queue nodes and the external system. The queue manager handles node instantiation, termination, and data routing, abstracting the complexity of managing multiple nodes from the rest of the system. This intermediary layer allows the system to handle large data volumes while maintaining manageable complexity through centralized coordination.
3Reliability
If permanent data storage is used to maintain data availability, then data accessibility improves, but resource consumption increases
Solution Approach 1:
The patent implements ephemeral queue nodes that are created when needed and terminated when not needed, rather than maintaining permanent storage for all data. Data is retained only as long as it is actively being processed or needs to be accessed. Once data has been processed and is no longer needed, it is discarded rather than permanently stored. This approach maintains data availability during the active processing period while significantly reducing resource consumption compared to permanent storage.
Solution Approach 2:
The patent employs periodic monitoring of data queue conditions and dynamic adjustment of node lifecycle. The system periodically evaluates whether queue nodes should be instantiated or terminated based on current data flow patterns and storage requirements. This periodic action allows the system to maintain data availability when needed while minimizing resource consumption during low-activity periods, resolving the contradiction between reliability and resource usage.
Data Source
AI summary
A computer-implemented method, system, and computer-readable media are disclosed herein. In embodiments, the computer-implemented method may entail receiving, by a data service, live data associated with an entity. The entity may be, for example, a customer of the data service. The method may then route the live data to a dual-queue system. The live data may then be loaded into a live data queue for processing of the live data. In addition, the live data may be stored as a persistent backup of the live data in a stale data queue. A remote data store may periodically establish a connection with the dual-queue system, after which, at least a portion of the stale data may be transmitted to the remote data store. Additional embodiments are described and/or claimed.


