Data Lake Connection Autoscaling for Load-Responsive Resource Use

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud resource usage for data lakes is often sub-optimal due to unmanaged load, leading to increased costs.

Innovation Solution

A system and method for autoscaling data lake connections based on collected metrics, automatically adjusting the number of processes connecting to the data lake to optimize resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the number of processes connecting to the data lake is increased to handle higher data loads, then productivity is improved, but resource usage efficiency deteriorates due to sub-optimal utilization of cloud resources

Engineering Contradiction:
Improvedata processing capacityVSAvoidcloud resource usage efficiency
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The system dynamically adjusts the number of processes connecting to the data lake based on real-time load metrics. The autoscaling mechanism monitors data lake load and automatically scales the number of processes up or down to match actual demand, ensuring optimal resource utilization while maintaining required productivity levels.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements a feedback loop where load metrics from the data lake are continuously collected and used to automatically adjust the number of processes. This closed-loop control ensures that resource allocation responds to actual workload conditions, preventing both over-provisioning and under-provisioning of cloud resources.

Inventive Principle:
Principle #23Feedback

2Loss of energy

If manual management of process scaling is implemented, then resource usage can be controlled, but adaptability deteriorates due to inability to respond automatically to varying data loads

Engineering Contradiction:
Improvecloud resource usage efficiencyVSAvoidresponse to varying data loads
Core Design Contradiction:
Loss of energyVSAdaptability or versatility

Solution Approach 1:

The system enables self-service autoscaling where the data lake infrastructure automatically manages its own process scaling based on monitored load metrics. The autoscaling mechanism autonomously adjusts process numbers without requiring manual intervention, combining efficient resource control with automatic adaptability to changing workload conditions.

Inventive Principle:
Principle #25Self-service

3Productivity

If cloud resources are over-provisioned to ensure adequate processing capacity, then productivity is maintained during peak loads, but resource usage efficiency deteriorates during low-utilization periods

Engineering Contradiction:
Improvedata processing capacityVSAvoidcloud resource consumption
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The system transitions from static over-provisioning to dynamic resource allocation. The autoscaling mechanism continuously monitors load metrics and adjusts the number of processes in real-time, ensuring adequate processing capacity during peak loads while reducing resource consumption during low-utilization periods.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the parameter of process quantity dynamically based on load conditions. By monitoring data lake load metrics and adjusting the number of processes accordingly, the system adapts resource consumption to actual workload requirements, avoiding both over-provisioning and under-provisioning.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12468722B1System, method, and computer program for autoscaling data lake connections
Publication Date: 2025.11.11 AMDOCS DEV LTD
  • US12468722B1 patent drawing
  • US12468722B1 patent drawing
  • US12468722B1 patent drawing

AI summary

As described herein, a system, method, and computer program are provided for autoscaling data lake connections. One or more metrics defining a load on one or more data sources included in a data lake are collected. A plurality of processes configured to connect to the data lake to retrieve data therefrom are automatically scaled, as a function of the one or more metrics.