DynamoDB is a fully managed NoSQL database service from Amazon that provides unlimited storage and throughput scaling without downtime. The document discusses getting started with DynamoDB, including defining primary keys like hash and hash-range, provisioning throughput, and using secondary indexes. Best practices include uploading big data to S3 and having DynamoDB only store pointers, as well as designing uniform workloads that avoid limited hash keys and use distinct values.

1. @agatestudio
DynamoDB
Aswin
Knight
Agate Studio

2. Amazon DynamoDB
(Introduction)
Aswin Juari

3. Overview
• Amazon DynamoDB
• Getting Started
• Best Practice

4. Amazon DynamoDB
• Fully Managed NoSQL Database Service
• Unlimited traffic & storage :D.
• Scaling without downtime.

5. Getting Started with DynamoDB
• Define Primary Keys
– Hash
– Hash and Range
• Provisioned throughput:
– Read Operation :
Read Operation Per Second * Read Operation Data/ 4KB
– Write Operation:
Write Operation Per Second * size of item/1KB
• Note: You will be charged priced per hour of
provisioned throughput

6. Example

7. Getting Started with DynamoDB
• Optional Element
– Secondary Index
• Local Secondary Index
• Global Secondary Index
• Transaction
Item Level Transaction only. Puts, updates,
deletes, are ACID.

8. Local Secondary Index
• Hash key is the same with primary index
• Consume Read & Write from table

9. Global Secondary Index
• Hash Key can be different from hash Index
• Every read & write has its own provisioned
throughput setting
• Notes: Global Secondary Index is like create a
new table that has the same content, but
different index. Meanwhile, local secondary
index is the same table with the different
range key.

10. Minus
• Cannot Modify Table Index
• You cannot query for not indexed attribute.

11. Best Practice
• Big Data Upload to S3
– DynamoDB only for Pointer
• Design Uniform Workload
– Avoid limited hash key values,
– Use distinct hash key values.

12. Further Research
• Development API
– How to Do Query