SET, REMOVE, ADD, and DELETE

In this lesson you will learn set, remove, add, and delete in DynamoDB, why it matters within update operations, and how to use it correctly with clear, copy-ready examples.

SET, REMOVE, ADD, and DELETE Overview

SET, REMOVE, ADD, and DELETE lets you structure DynamoDB work so it stays readable, testable, and easy to scale. Instead of ad-hoc code, you follow a clear pattern that other developers can recognise immediately.

The key is to keep set, remove, add, and delete focused and predictable. Start from the minimal example here, then layer in only the complexity your feature actually needs.

import { DynamoDBClient } from '@aws-sdk/client-dynamodb';
import { DynamoDBDocumentClient, UpdateCommand } from '@aws-sdk/lib-dynamodb';

const client = new DynamoDBClient({});
const docClient = DynamoDBDocumentClient.from(client);

await docClient.send(new UpdateCommand({
  TableName: 'Orders',
  Key: { pk: 'ORDER#123', sk: 'META' },
  UpdateExpression: 'SET #s = :status',
  ExpressionAttributeNames: { '#s': 'status' },
  ExpressionAttributeValues: { ':status': 'SHIPPED' },
  ReturnValues: 'ALL_NEW',
}));

UpdateCommand modifies attributes in place using an update expression.

SET, REMOVE, ADD, and DELETE Example

import { DynamoDBClient } from '@aws-sdk/client-dynamodb';
import { DynamoDBDocumentClient } from '@aws-sdk/lib-dynamodb';

const docClient = DynamoDBDocumentClient.from(new DynamoDBClient({}));
// docClient.send(new PutCommand(...)) etc.

Start from a minimal SET, REMOVE, ADD, and DELETE example and grow it only as needed.
Keep configuration explicit so SET, REMOVE, ADD, and DELETE behaves the same in every environment.
Name things clearly so teammates understand your SET, REMOVE, ADD, and DELETE at a glance.
Add tests around SET, REMOVE, ADD, and DELETE early to lock in expected behaviour.

Amazon DynamoDB Cheatsheet

Handy DynamoDB (AWS SDK v3) reference related to set, remove, add, and delete.

Operation	Command	Purpose
Create/replace	`PutCommand`	Write an item
Read one	`GetCommand`	Fetch by primary key
Update	`UpdateCommand`	Modify attributes
Delete	`DeleteCommand`	Remove an item
Query	`QueryCommand`	Efficient key-based read
Scan	`ScanCommand`	Full-table read (avoid)
Transaction	`TransactWriteCommand`	Atomic multi-item writes

How SET, REMOVE, ADD, and DELETE Works in DynamoDB

SET, REMOVE, ADD, and DELETE builds on DynamoDB's key-value and document model, where every item lives in a partition chosen by its partition key and is optionally ordered by a sort key.

UpdateCommand modifies attributes in place using an update expression.

Design access patterns first, then model keys around them.
Prefer Query over Scan for predictable performance.
Use expressions to read and write only what you need.
Keep items small and avoid hot partitions.

Practical Guidance for SET, REMOVE, ADD, and DELETE

In production, set, remove, add, and delete should be cost-aware and resilient. Right-size capacity, handle throttling with retries, and lean on indexes to support your query patterns.

Concern	Recommendation
Performance	Query by key; avoid table scans
Cost	Use on-demand or right-sized provisioned capacity
Modeling	Design for known access patterns
Reliability	Retry throttled requests with backoff

Common Mistakes

Copying set, remove, add, and delete snippets without understanding what each line does.
Skipping error handling and edge cases when wiring up set, remove, add, and delete.
Leaving set, remove, add, and delete untested, so regressions slip into production.
Over-engineering set, remove, add, and delete before you actually need the extra flexibility.

Key Takeaways

SET, REMOVE, ADD, and DELETE is a core part of working effectively with DynamoDB.
Start small and keep set, remove, add, and delete focused on a single responsibility.
Apply consistent patterns so set, remove, add, and delete scales across your project.
Test and document set, remove, add, and delete to keep it maintainable over time.

Pro Tip

When you get stuck on set, remove, add, and delete, reduce it to the smallest reproducible example first — most DynamoDB issues become obvious once the noise is gone.