Boto3 (Python) client vs resource in DynamoDB - Visual Side-by-Side Comparison

Concept Flow - Boto3 (Python) client vs resource

Start

↓

Choose Boto3 Interface

↓

Client: Low-level API

↓

Call service methods

↓

Receive raw response

↓

Resource: High-level API

↓

Use Python objects

↓

Call methods on objects

↓

Simplified interaction

↓

End

You start by choosing between client or resource interface. Client calls low-level service methods and returns raw data. Resource provides Python objects with easy methods for simpler use.

Execution Sample

DynamoDB

import boto3
client = boto3.client('dynamodb')
resource = boto3.resource('dynamodb')
table_client = client.get_item(TableName='MyTable', Key={'Id': {'S': '123'}})
table_resource = resource.Table('MyTable')
item = table_resource.get_item(Key={'Id': '123'})

This code shows how to get an item from DynamoDB using both client and resource interfaces.

Execution Table

Step	Action	Interface	Input	Output
1	Create client	client	service='dynamodb'	client object created
2	Create resource	resource	service='dynamodb'	resource object created
3	Call get_item	client	TableName='MyTable', Key={'Id': {'S': '123'}}	Raw response dict with item data
4	Access Table object	resource	Table('MyTable')	Table resource object
5	Call get_item	resource	Key={'Id': '123'}	Response dict with item data
6	Extract item	resource	response['Item']	Python dict with item attributes
7	End	-	-	-

💡 All steps complete, showing difference in method calls and outputs between client and resource.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6	Final
client	None	client object	client object	client object	client object	client object	client object	client object
resource	None	None	resource object	resource object	resource object	resource object	resource object	resource object
table_client	None	None	None	raw response dict	raw response dict	raw response dict	raw response dict	raw response dict
table_resource	None	None	None	None	Table resource object	Table resource object	Table resource object	Table resource object
item	None	None	None	None	None	response dict	Python dict	Python dict

Key Moments - 2 Insights

Why does the client get_item require the key value wrapped in {'S': '123'} but resource does not?

The client interface uses low-level API requiring explicit data types like {'S': '123'} for strings, as shown in step 3. The resource interface abstracts this, letting you pass plain Python types, as in step 5.

Why is the output from client get_item called 'raw response'?

Because client returns the full low-level response dictionary directly from AWS, including metadata and typed attributes (step 3). Resource simplifies this to Python dicts with attribute values (step 6).

Visual Quiz - 3 Questions

Look at the execution table, what type of object is 'resource' after step 2?

A A low-level client object

B A high-level resource object

C A raw response dictionary

D A Python dict with item data

💡 Hint

Check the output column at step 2 in the execution_table.

At which step does the client interface return the raw response dict?

A Step 3

B Step 1

C Step 5

D Step 6

💡 Hint

Look at the output column for step 3 in the execution_table.

If you want simpler Python objects to work with DynamoDB items, which interface should you use?

A Client interface

B Both are equally simple

C Resource interface

D Neither, use raw HTTP calls

💡 Hint

Refer to the concept_flow and the difference in outputs in execution_table steps 5 and 6.

Concept Snapshot

Boto3 client is low-level, needs explicit data types and returns raw AWS responses.
Boto3 resource is high-level, uses Python objects and simplifies data handling.
Use client for full control, resource for easier coding.
Client methods require detailed parameters; resource methods accept Python types.
Resource wraps tables and items as objects with methods.
Choose based on your comfort and needs.

Full Transcript

This visual execution compares Boto3 client and resource interfaces for DynamoDB in Python. First, we create both client and resource objects. The client calls get_item with explicit typed keys and returns a raw response dictionary. The resource accesses a Table object and calls get_item with plain Python keys, returning a simplified Python dictionary. Variables track these objects and responses step-by-step. Key moments clarify why client needs typed keys and why resource is easier to use. The quiz tests understanding of object types, response steps, and interface choice. The snapshot summarizes the main differences and usage tips.