AWS SDK for JavaScript/Node.js in DynamoDB - Time & Space Complexity

Time Complexity: AWS SDK for JavaScript/Node.js

O(n)

Understanding Time Complexity

We want to understand how the time to complete DynamoDB operations changes as we work with more data.

Specifically, how does the number of API calls grow when using AWS SDK for JavaScript/Node.js with DynamoDB?

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

const AWS = require('aws-sdk');
const dynamodb = new AWS.DynamoDB.DocumentClient();

async function batchGetItems(keys) {
  const params = {
    RequestItems: {
      'MyTable': { Keys: keys }
    }
  };
  return dynamodb.batchGet(params).promise();
}
    

This code fetches multiple items from a DynamoDB table in one batch request using the AWS SDK for JavaScript/Node.js.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: The batchGet API call to DynamoDB.
• How many times: One call per batch, but if keys exceed 100, multiple batch calls are needed.

How Execution Grows With Input

As the number of keys increases, the number of batchGet calls grows in steps of 100 keys per call.

Input Size (n)	Approx. API Calls/Operations
10	1
100	1
1000	10

Pattern observation: The number of API calls grows roughly in proportion to the number of keys divided by 100.

Final Time Complexity

Time Complexity: O(n)

This means the time grows linearly with the number of items requested.

Common Mistake

[X] Wrong: "One batchGet call can fetch any number of items instantly."

[OK] Correct: DynamoDB limits batchGet to 100 items per call, so large requests require multiple calls, increasing time.

Interview Connect

Understanding how API calls scale with input size helps you design efficient data access patterns and shows you can think about performance in real cloud applications.

Self-Check

"What if we changed batchGet to single GetItem calls for each key? How would the time complexity change?"

Practice

1. What is the first step to interact with DynamoDB using the AWS SDK for JavaScript/Node.js?

easy

A. Create a DynamoDB client instance

B. Write a SQL query

C. Install a database driver

D. Open a database connection manually

Solution

1. Step 1: Understand AWS SDK usage

   To work with DynamoDB, you first create a client object that represents the service.

2. Step 2: Recognize the role of the client

   The client handles requests and responses to DynamoDB; no manual connection or SQL is needed.

3. Final Answer:

   Create a DynamoDB client instance -> Option A

4. Quick Check:

   Client creation = First step [OK]

Hint: Always start by creating the service client [OK]

Common Mistakes:

• Trying to write SQL queries for DynamoDB
• Assuming manual connection is needed
• Skipping client creation

2. Which of the following is the correct way to import the DynamoDB client from AWS SDK v3 in Node.js?

easy

A. const DynamoDBClient = require('@aws-sdk/client-dynamodb');

B. const { DynamoDBClient } = require('aws-sdk');

C. import { DynamoDBClient } from '@aws-sdk/client-dynamodb';

D. import DynamoDBClient from 'aws-sdk';

Solution

1. Step 1: Identify AWS SDK v3 import style

   AWS SDK v3 uses ES modules and named imports from '@aws-sdk/client-dynamodb'.

2. Step 2: Match correct syntax

   import { DynamoDBClient } from '@aws-sdk/client-dynamodb'; uses ES module import with correct package and named import syntax.

3. Final Answer:

   import { DynamoDBClient } from '@aws-sdk/client-dynamodb'; -> Option C

4. Quick Check:

   ES module named import = import { DynamoDBClient } from '@aws-sdk/client-dynamodb'; [OK]

Hint: Use ES module imports from '@aws-sdk/client-dynamodb' [OK]

Common Mistakes:

• Using old AWS SDK v2 import style
• Using default import instead of named import
• Mixing require and import syntax

3. Given the following code snippet, what will be logged if the item exists in the DynamoDB table?

import { DynamoDBClient, GetItemCommand } from '@aws-sdk/client-dynamodb';
const client = new DynamoDBClient({ region: 'us-east-1' });

async function getItem() {
  const command = new GetItemCommand({
    TableName: 'Users',
    Key: { 'UserId': { S: '123' } }
  });
  const response = await client.send(command);
  console.log(response.Item);
}
getItem();

medium

A. Undefined because no item exists

B. An empty object {}

C. An error is thrown due to missing parameters

D. The item object with attributes if found

Solution

1. Step 1: Understand GetItemCommand behavior

   GetItemCommand returns an object with an Item property if the item exists.

2. Step 2: Analyze console.log output

   Logging response.Item will show the item's attributes as an object if found.

3. Final Answer:

   The item object with attributes if found -> Option D

4. Quick Check:

   response.Item = item object [OK]

Hint: GetItemCommand returns Item if found, else undefined [OK]

Common Mistakes:

• Expecting an error when item is missing
• Assuming response itself is the item
• Confusing empty object with undefined

4. What is wrong with the following code snippet that tries to put an item into DynamoDB?

import { DynamoDBClient, PutItemCommand } from '@aws-sdk/client-dynamodb';
const client = new DynamoDBClient({ region: 'us-east-1' });

async function putItem() {
  const command = new PutItemCommand({
    TableName: 'Users',
    Item: { UserId: '123', Name: 'Alice' }
  });
  await client.send(command);
}
putItem();

medium

A. TableName should be lowercase

B. Item attributes must be wrapped with DynamoDB data types like { S: 'value' }

C. PutItemCommand does not exist in AWS SDK

D. Missing await before client.send

Solution

1. Step 1: Check Item attribute format

   DynamoDB expects attribute values wrapped in type descriptors like { S: 'string' }.

2. Step 2: Identify the error cause

   Passing plain strings without type wrappers causes validation errors.

3. Final Answer:

   Item attributes must be wrapped with DynamoDB data types like { S: 'value' } -> Option B

4. Quick Check:

   Attribute values need type wrappers [OK]

Hint: Always wrap attribute values with DynamoDB types (S, N, etc.) [OK]

Common Mistakes:

• Passing plain strings instead of typed attributes
• Assuming table names are case-insensitive
• Forgetting to await async calls

5. You want to update a user's email in DynamoDB using AWS SDK for JavaScript/Node.js. Which approach correctly updates only the email attribute without overwriting the entire item?

const command = new UpdateItemCommand({
  TableName: 'Users',
  Key: { UserId: { S: '123' } },
  UpdateExpression: 'SET Email = :email',
  ExpressionAttributeValues: { ':email': { S: '[e-mail]' } }
});
await client.send(command);

hard

A. This code correctly updates only the Email attribute

B. UpdateExpression should be 'ADD Email :email' to update

C. You must use PutItemCommand to update attributes

D. ExpressionAttributeValues keys should not start with ':'

Solution

1. Step 1: Understand UpdateItemCommand usage

   UpdateExpression with 'SET' updates specified attributes without replacing the whole item.

2. Step 2: Verify ExpressionAttributeValues syntax

   Keys start with ':' and values use DynamoDB types, matching the expression.

3. Step 3: Confirm no overwrite occurs

   Using UpdateItemCommand with SET updates only Email, preserving other attributes.

4. Final Answer:

   This code correctly updates only the Email attribute -> Option A

5. Quick Check:

   UpdateExpression SET = partial update [OK]

Hint: Use UpdateItemCommand with SET to update attributes safely [OK]

Common Mistakes:

• Using PutItemCommand which overwrites entire item
• Using ADD instead of SET for attribute update
• Removing ':' prefix in ExpressionAttributeValues keys