PutItem (creating items) in DynamoDB - Time & Space Complexity

Time Complexity: PutItem (creating items)

O(1)

Understanding Time Complexity

When we add a new item to a DynamoDB table using PutItem, we want to know how the time it takes changes as the table grows.

We ask: Does adding one more item take longer if the table is bigger?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

    const params = {
      TableName: "Users",
      Item: {
        UserId: { S: "123" },
        Name: { S: "Alice" },
        Age: { N: "30" }
      }
    };
    
    await dynamodb.putItem(params).promise();
    

This code adds a new user item to the "Users" table in DynamoDB.

Identify Repeating Operations

• Primary operation: Writing a single item to the database.
• How many times: Exactly once per PutItem call.

How Execution Grows With Input

Adding one item takes about the same time no matter how many items are already in the table.

Input Size (n)	Approx. Operations
10	1 write operation
100	1 write operation
1000	1 write operation

Pattern observation: The time to add one item stays about the same regardless of table size.

Final Time Complexity

Time Complexity: O(1)

This means adding one item takes a constant amount of time, no matter how big the table is.

Common Mistake

[X] Wrong: "Adding an item takes longer as the table grows because it has to search through all existing items."

[OK] Correct: DynamoDB uses indexes and hashing to find where to put the item quickly, so it does not scan the whole table when adding.

Interview Connect

Understanding that PutItem runs in constant time helps you explain how databases handle writes efficiently, a useful skill when discussing data storage in interviews.

Self-Check

"What if we added a condition to check if the item exists before inserting? How would the time complexity change?"