Auto-scaling configuration in DynamoDB - Step-by-Step Execution

Concept Flow - Auto-scaling configuration

Monitor Usage Metrics

↓

Compare Usage to Thresholds

↓

Increase

↓

Capacity

↓

Update Table Capacity

↓

Repeat Monitoring

Auto-scaling watches usage and adjusts capacity up or down automatically to keep performance steady.

Execution Sample

DynamoDB

1. Monitor read/write capacity usage
2. If usage > 70%, increase capacity
3. If usage < 30%, decrease capacity
4. Update table settings
5. Repeat monitoring

This process automatically adjusts DynamoDB table capacity based on usage thresholds.

Execution Table

Step	Read Capacity Usage (%)	Write Capacity Usage (%)	Condition	Action	New Read Capacity	New Write Capacity
1	50	40	Usage within thresholds	No change	5	5
2	75	80	Usage > 70%	Increase capacity	7	7
3	65	60	Usage within thresholds	No change	7	7
4	25	20	Usage < 30%	Decrease capacity	5	5
5	55	50	Usage within thresholds	No change	5	5
6	85	90	Usage > 70%	Increase capacity	7	7
7	70	65	Usage within thresholds	No change	7	7
8	28	25	Usage < 30%	Decrease capacity	5	5
9	50	45	Usage within thresholds	No change	5	5
Exit	-	-	Monitoring stops	Manual stop or no changes needed	-	-

💡 Monitoring stops when manually stopped or no capacity changes are needed.

Variable Tracker

Variable	Start	After Step 2	After Step 4	After Step 6	After Step 8	Final
Read Capacity	5	7	5	7	5	5
Write Capacity	5	7	5	7	5	5

Key Moments - 3 Insights

Why does capacity increase when usage is above 70%?

Because high usage means the table needs more capacity to handle requests without slowing down, as shown in execution_table rows 2 and 6.

Why does capacity decrease when usage falls below 30%?

To save costs by reducing unused capacity, as seen in execution_table rows 4 and 8 where capacity is lowered.

Why are there steps where no capacity change happens even if usage is close to thresholds?

Because usage is within acceptable limits (between 30% and 70%), so no adjustment is needed, like in rows 1, 3, 5, 7, and 9.

Visual Quiz - 3 Questions

Look at the execution_table at step 2, what action is taken when read capacity usage is 75%?

A No change

B Increase capacity

C Decrease capacity

D Stop monitoring

💡 Hint

Check the 'Action' column at step 2 in the execution_table.

At which step does the capacity decrease due to low usage?

A Step 6

B Step 3

C Step 4

D Step 7

💡 Hint

Look for 'Usage < 30%' condition and 'Decrease capacity' action in the execution_table.

If the read capacity usage stays at 50% continuously, what would the capacity changes be?

A No capacity change

B Capacity increases

C Capacity decreases

D Capacity fluctuates randomly

💡 Hint

Refer to execution_table rows where usage is around 50% and see the action taken.

Concept Snapshot

Auto-scaling in DynamoDB:
- Monitors read/write usage continuously
- Increases capacity if usage > 70%
- Decreases capacity if usage < 30%
- Keeps capacity stable otherwise
- Helps balance performance and cost automatically

Full Transcript

Auto-scaling configuration in DynamoDB works by monitoring the read and write capacity usage of a table. When usage goes above 70%, the system increases capacity to handle more requests smoothly. When usage falls below 30%, it decreases capacity to save costs. If usage stays between 30% and 70%, no changes are made. This cycle repeats continuously to keep the table performing well without wasting resources. The execution table shows step-by-step how capacity changes based on usage percentages, and the variable tracker shows how capacity values update over time.