Auto-scaling configuration in DynamoDB - Time & Space Complexity

Time Complexity: Auto-scaling configuration

O(n)

Understanding Time Complexity

When using auto-scaling in DynamoDB, it is important to understand how the system adjusts capacity as demand changes.

We want to know how the time to adjust scales with the number of scaling events or workload changes.

Scenario Under Consideration

Analyze the time complexity of this auto-scaling configuration snippet.

  {
    "AutoScalingPolicy": {
      "TargetTrackingScalingPolicyConfiguration": {
        "TargetValue": 70.0,
        "PredefinedMetricSpecification": {
          "PredefinedMetricType": "DynamoDBReadCapacityUtilization"
        },
        "ScaleOutCooldown": 60,
        "ScaleInCooldown": 60
      }
    }
  }
    

This code sets up auto-scaling to keep read capacity near 70% utilization by adjusting capacity after cooldown periods.

Identify Repeating Operations

In auto-scaling, the system repeatedly checks usage and adjusts capacity.

• Primary operation: Monitoring usage metrics and adjusting capacity units.
• How many times: This happens continuously as workload changes, triggered by metric evaluations.

How Execution Grows With Input

As the number of scaling events increases, the system performs more adjustments.

Input Size (number of scaling events)	Approx. Operations
10	10 adjustments
100	100 adjustments
1000	1000 adjustments

Pattern observation: The operations grow linearly with the number of scaling events.

Final Time Complexity

Time Complexity: O(n)

This means the time to handle scaling grows directly with how many times scaling happens.

Common Mistake

[X] Wrong: "Auto-scaling adjusts capacity instantly regardless of workload changes."

[OK] Correct: Auto-scaling waits for cooldown periods and metric checks, so adjustments happen over time, not instantly.

Interview Connect

Understanding how auto-scaling time grows helps you explain system responsiveness and resource management clearly.

Self-Check

"What if the cooldown periods were removed? How would the time complexity of scaling adjustments change?"