Amazon DynamoDB is a key-value and document database that delivers single-digit millisecond performance at any scale. It's a fully managed, multiregion, multimaster, durable database with built-in security, backup and restore, and in-memory caching for internet-scale applications.

1. Amazon
DynamoDB

2. OUTLINE
04
Here you could describe
the topic of the section
05
Here you could describe
the topic of the section
06
01
02
03
Timeline
Introduction
NoSQL Database
Features
Project Stages
Our Team

3. Timeline of Database Technology

4. INTRODUCTION
● Amazon DynamoDB is a fully
managed NoSQL database service
that provides fast and predictable
performance with seamless
scalability.
● DynamoDB lets you offload the
administrative burdens of operating
and scaling a distributed database.

7. WHY DO WE
NEED
DynamoDB?

8. a hotel chain with
hundreds of new guests
per day
a small app with
growing number
of users! a music player with
countless songs and
thousands of users!

9. We can use Amazon DynamoDB to create a database that can store and retrieve any
amount of data, and serve any level of request traffic.

10. Important Concepts in NoSQL!
SHARDING
PARTITIONING

11. As traffic grows to your site, your database might end up being a
bottleneck as its gets overloaded with more requests.
And scaling by upgrading the single database server
to something more powerful starts to get very
EXPENSIVE!

12. Sharding !
(or Horizontal Partitioning)
This is where sharding may help!
As breaking your big single logical database into small
databases means load is now distributed among multiple
machines and the size is more scalable as you can just add on
another node to increase the size.
Keep adding more nodes!
So, sharding can be implemented at both the application level or
the database level.

13. Vertical Partitioning!
Where we split data by columns or
features so we have a microblogging
platform like Twitter or the users will have
certain information about them in the
database such as their tweets, followers
and favorites.
If we partition this data vertically, then we store tweets in one
database, followers in the next and favorites in another.

14. Data Partitioning Criteria-Algorithmic and Dynamic

15. A basic Demonstration!
Creating our first DynamoDB table, adding items to our table,
and then query the table to find the items through the AWS
Management Console.

16. Create and Query a NoSQL table with Amazon DynamoDB
Open the AWS Management Console. Type DynamoDB in the search bar and choose to
open the DynamoDB console.

17. a. In the DynamoDB console, choose
Create table.
b. We will use a music library as our use
case In the Table name box, type Music.
Step 1 . Create a NoSQL table in DynamoDB

18. c. The partition key is used to spread data across
partitions for scalability. It’s important to choose
an attribute with a wide range of values and that
is likely to have evenly distributed access
patterns. Type Artist in the Partition key box.
d. Because each artist may write many songs,
you can enable easy sorting with a sort key.
Select the Add sort key check box. Type
songTitle in the Add sort key box.

19. e. Next, you will enable DynamoDB auto
scaling for your table.
DynamoDB auto scaling will change the read
and write capacity of your table based on
request volume.
f. Scroll down the screen past Secondary
indexes, Provisioned capacity, and Auto Scaling
to the Create button.
choose Create.
When the Music table is ready to use, it appears
in the table list with a check box .

20. a. Select the Items tab. On the Items tab, choose
Create item .
b. In the data entry window, type the following:
● For the Artist attribute, type No One
You Know.
● For the songTitle attribute, type Call
Me Today.
Choose Save to save the item.
Step 2 . Add data to the NoSQL table in DynamoDB

21. c. Repeat the process to add a few more items to
your Music table:
● Artist: No One You Know; songTitle: My
Dog Spot
● Artist: No One You Know; songTitle:
Somewhere Down The Road
● Artist: The Acme Band; songTitle: Still
in Love
● Artist: The Acme Band; songTitle: Look
Out, World

22. In DynamoDB, query operations are efficient and
use keys to find data. Scan operations traverse the
entire table.
a. In the drop-down list in the dark gray banner
above the items, change Scan to Query.
For your first query, do the following:
● In the Artist box, type No One You Know,
and choose Start search. All songs
performed by No One You Know are
displayed.
Step 3. Query the NoSQL table in DynamoDB

23. Change the Query drop-down list back to Scan.
Select the check box next to The Acme Band. In the Actions
drop-down list, choose Delete. You will be asked whether to
delete the item. Choose Delete and your item is deleted.
Step 4. Delete an existing item.
Step 5. Delete a NoSQL table.
In the console, choose the option next to Music table and
then choose delete table.
In the confirmation dialog box, choose delete.

24. Let’s understand more !
DynamoDB is a great fit for mobile, web, gaming, ad tech, and IoT
applications where scalability, throughput, and reliable performance are
key considerations.

25. How does Dynamo DB work?

26. When we create the table we specify Partition Key and an
optional Sort Key, we can’t change these later but rest of
the attributes (columns) of item (row) can change. Also
each item can have different set of attributes.
Table
Table Keys
Partition Key : authorId
Sort Key : publicationDate

27. A DynamoDB item is nothing but a row in the table. We can change any attribute of an item except its keys: partition key
or sort key, these keys are an identification for an item; if we have to change these keys, then the only option is to delete
an item and create it again.
Item
Data Types
DynamoDB supports different data types for attributes of an item, they can be mainly categorised into the following:
Scalar Types : Number, String, Binary, Boolean and Null.
Document Types : List and Map
Set Types : Number Set, String Set, and Binary Set.

28. Partition & Sort Keys
Partition Key
This key is mandatory for the
DynamoDB table and item. DynamoDB
partitions the items using this key, that’s
why this key is also called as the
partition key and sometimes is also
referred as a Hash Key.
Sort key
This key can be used in conjunction
with the Partition key but it is not
mandatory. This is useful while
querying the data relating a Partition
key. We can use several different filter
functions on the sort key such as
begins with, between etc. Some times it
is also referred to as a Range Key.

29. Batch APIs
BatchGetItem :
This can be used to fetch items from
different tables using Partition Key and
Sort Key. In a single BatchGetItem call,
we can fetch up to 16MB data or 100
items.
BatchWriteItem:
This can be used to delete or put items
on one or more tables in DynamoDB in
one call. We can write up to 16 MB
data, which can be 25 put and delete
requests.

30. Query & Scan

31. INDEXES

32. Main features of Dynamo DB
Performance and
Scalability
Automatic Data
Management
Time To Live
Storage of inconsistent
schema items
Access to control rules

33. APPLICATIONS
DUOLINGO
MAJOR
BASEBALL
LEGUE
HESS Corp.
GE
Heathcare
NTT
DoCoMo

34. ● Duolingo uses Amazon DynamoDB to store 31
billion items in support of an online learning site
that delivers lessons for 80 languages.
● The U.S. startup reaches more than 18 million
monthly users around the world who perform
more than six billion exercises using the free
Duolingo lessons.
● The company relies heavily on Amazon
DynamoDB not just for its highly scalable
database, but also for high performance that
reaches 24,000 read units per second and 3,300
write units per second.
Duolingo Example

35. ● Doppler radar system that sits behind home
plate, sampling the ball position 2,000 times a
second? Or that there are two stereoscopic
imaging devices, usually positioned above the
third-base line, that sample the positions of
players on the field 30 times a second.
● All these data transactions require a system that
is fast on both reads and writes. The MLB uses a
combination of AWS components to help
process all this data. DynamoDB plays a key role
in ensuring queries are fast and reliable.
MLB Example

36. BENEFITS
FAST, CONSISTENT
PERFORMANCE
HIGHLY
SCALABLE
FLEXIBLE
EVENT-DRIVEN
PROGRAMMING
FULLY
MANAGED
FINE
GRAINED
ACCESS
CONTROL

37. DRAWBACKS
● When multi-item or cross table transactions are
required.
● When complex queries and joins are required
● When real-time analytics on historic data is required

38. CONCLUSIÓN
● As a non-relational database, DynamoDB is a reliable system.
● It comes with options to backup, restore and secure data, and is great for both mobile
and web apps, with the exception of special services like financial transactions and
healthcare, you can redesign almost any application with DynamoDB.
● This non-relational database is extremely convenient to build event-driven
architecture and user-friendly applications. Any shortcomings with analytic workloads
are easily rectified with the use of an analytic-focused SQL layer, making DynamoDB
a great asset for users.

39. ADVANCED TOPICS IN DYNAMODB
- Data modeling
- DynamoDB Scaling
- Understanding partitions
- Design patterns and best
practices

40. THANKS!
Presented By-
TUSHALI CHETTY (16070124059)
KRITI KATYAYAN (16070124024)
AMEYA KSHIRSAGAR (16070124025)
ADITYA NAIK (16070124033)