1
00:00:00,390 --> 00:00:05,220
Are going to come back let's talk about dining with be retried capacity and it's which is the throughput

2
00:00:05,370 --> 00:00:08,780
parameters for your table and the associated pricing.

3
00:00:10,490 --> 00:00:12,670
So what's the read capacity units.

4
00:00:12,800 --> 00:00:16,770
So when you configure the table with the table you will be asked.

5
00:00:16,770 --> 00:00:21,960
You have to enter the primary key you have to enter the read capacity units and the right capacity units.

6
00:00:22,040 --> 00:00:22,960
There are three things.

7
00:00:22,970 --> 00:00:28,820
And of course the name if you want to add any one read capacity and it represents what does a heat capacity

8
00:00:28,820 --> 00:00:36,430
and to present one strongly consistent 3 per second or two if eventually consistent reads per second

9
00:00:36,440 --> 00:00:39,940
for an item up to four key kilobyte in size.

10
00:00:39,950 --> 00:00:43,070
So if you have one item that is up to.

11
00:00:43,070 --> 00:00:46,620
So one two three or four kilobyte insights.

12
00:00:46,790 --> 00:00:54,680
Then one read per second for this item is what we call eat or eat capacity unit if you need to read

13
00:00:54,710 --> 00:00:57,670
an item that is larger than 4 kilobyte.

14
00:00:57,920 --> 00:01:04,820
Then what do we need one great capacity unit can give you up to one read per second for an item for

15
00:01:04,820 --> 00:01:05,630
kilobytes.

16
00:01:05,630 --> 00:01:06,880
Now if I need to do 8.

17
00:01:06,920 --> 00:01:09,220
So that means you need to reach capacity.

18
00:01:09,380 --> 00:01:12,900
If I need to do 12 three read capacity and so on and so forth.

19
00:01:12,950 --> 00:01:16,150
So are going to be will need to consume additional capacity units.

20
00:01:16,430 --> 00:01:22,730
The total number of free capacity units required depends on the item size and whether you want eventually

21
00:01:22,730 --> 00:01:26,350
consistent or strongly consistent with.

22
00:01:26,540 --> 00:01:32,600
So here when we said that one capacity and it represents one read for an item that is for kilobyte in

23
00:01:32,600 --> 00:01:33,620
size.

24
00:01:33,740 --> 00:01:35,780
So that is a strong consistency.

25
00:01:35,780 --> 00:01:40,060
If we're talking about revenger consistency then you have to read per second.

26
00:01:40,160 --> 00:01:46,670
So you can have two items of full color bite or one item up to 8 kilobyte that can be read by one recovery

27
00:01:46,760 --> 00:01:47,090
unit.

28
00:01:47,120 --> 00:01:57,100
So to simplify this even further let's say your target is to get to 1000 kilobyte per second rate.

29
00:01:57,200 --> 00:02:03,890
Now the question becomes what do you want do you want to do eventually consistency or strong consistency.

30
00:02:03,890 --> 00:02:13,260
Why is it different because one need capacity that is enough to read for kilobyte per second of the

31
00:02:13,260 --> 00:02:22,860
range of consistency or wondred capacity it is enough to do it kilobyte per second.

32
00:02:24,030 --> 00:02:30,650
So if you want to get to 1000 kilobyte per second of fried performance and you are talking about strong

33
00:02:30,740 --> 00:02:35,020
consistency then you need how many capacity capacity you need.

34
00:02:35,030 --> 00:02:36,500
I need 1000.

35
00:02:36,620 --> 00:02:41,220
Divide by 4 which is that kilobytes per unit.

36
00:02:41,330 --> 00:02:49,540
And this is four kilobytes this is per second for one and this is per second for the desiré two I need

37
00:02:49,640 --> 00:02:52,570
250 read capacity units.

38
00:02:52,600 --> 00:02:57,230
If I wanted to do eventually consistency it would be half of that because we are talking about 4 and

39
00:02:57,230 --> 00:02:57,520
8.

40
00:02:57,520 --> 00:03:00,550
So it will be hundred and twenty five for the capacity unit.

41
00:03:00,550 --> 00:03:03,940
Very easy to think about it from that perspective.

42
00:03:04,000 --> 00:03:11,740
Now what if my item size is two and a half kilobytes its not for do I divide by two and a half here.

43
00:03:11,740 --> 00:03:18,190
No because the definition of that it is an item up to 4 kilobytes in size.

44
00:03:18,190 --> 00:03:26,160
What if my item is 5 kilobyte in size that means each item will require to read capacity and so basically

45
00:03:26,160 --> 00:03:28,040
we are not doing fractions here.

46
00:03:28,120 --> 00:03:35,390
It's either up to four if the item sells up to four one week capacity or if the item size is less than

47
00:03:35,410 --> 00:03:35,800
eight.

48
00:03:35,790 --> 00:03:41,650
So multiples of four then you need to reach capacity and if the item size is up to 12 then you need

49
00:03:41,650 --> 00:03:43,580
three capacity units per item.

50
00:03:43,580 --> 00:03:46,270
So that's how it works and that's how the math works.

51
00:03:46,270 --> 00:03:50,150
Hopefully it's easier now to understand what's the right capacity it.

52
00:03:50,170 --> 00:03:56,410
On the other hand one road capacity and it represents one right per second for an item up to 1 kilobyte

53
00:03:56,430 --> 00:03:56,880
in size.

54
00:03:56,890 --> 00:04:02,890
Why did we not talk about eventually and strong because this is a right action and right action has

55
00:04:02,890 --> 00:04:10,690
nothing to do with eventual consistency and strong consistency that only for Read actions if you need

56
00:04:10,690 --> 00:04:16,900
to write an item larger than one kilobyte then will you be will need to consume additional capacity

57
00:04:16,900 --> 00:04:17,470
units.

58
00:04:17,490 --> 00:04:25,330
So now if I have if I want to write an item that is for kilobyte size then what do I need then I need

59
00:04:25,330 --> 00:04:26,170
for.

60
00:04:26,380 --> 00:04:29,420
Exactly four right capacity units.

61
00:04:30,100 --> 00:04:40,000
So as you can see here for capacity units to write an item of one of four kilobyte where as one read

62
00:04:40,000 --> 00:04:45,610
capacity on it we're talking about strong consistency can read can I use it can I use it I can use it

63
00:04:45,610 --> 00:04:53,590
to read for kilobyte if it is strong consistency and one read capacity on it was enough to read eight

64
00:04:53,590 --> 00:04:58,350
kilobytes if it was eventual consistency.

65
00:04:58,360 --> 00:05:08,170
So what does that tell me that tells you that using dynamo be for read intensive applications for gaming

66
00:05:08,170 --> 00:05:14,980
and apps and all that is going to be less costly compared to exactly the right operations.

67
00:05:14,980 --> 00:05:20,590
So if you have less rights and a lot of Freed's they're going to be is going to be a cost effective

68
00:05:20,590 --> 00:05:20,970
solution.

69
00:05:20,980 --> 00:05:28,510
If you have more rights than Greed's then that is going to be exactly that going to be more expensive.

70
00:05:28,510 --> 00:05:33,670
When we talk about it because there isn't right capacity on it are more or less the same cost.

71
00:05:33,730 --> 00:05:34,890
I'm talking about the unit.

72
00:05:38,460 --> 00:05:43,680
And with the heat capacity units that the total number of freight capacity units it depends on the item

73
00:05:43,680 --> 00:05:47,490
size that you would like to write pricing.

74
00:05:47,810 --> 00:05:51,660
As a rule of thumb reeds are cheaper than rights when using the animal.

75
00:05:51,800 --> 00:05:52,440
As we just.

76
00:05:52,490 --> 00:05:59,480
So with the one kilobyte and four kilobytes What do you pay for when using that MTV you pay for that

77
00:05:59,480 --> 00:06:05,270
provision throughput the read and write throughput for the table in hourly rates.

78
00:06:05,270 --> 00:06:11,330
So this is how much it costs per hour for the throughput that you have.

79
00:06:11,550 --> 00:06:16,410
You are charged for the provision throughput regardless whether used or not if you created a table and

80
00:06:16,410 --> 00:06:23,720
then you specified and it Fyffe read capacity on it and 5 right capacity on it or 25 and 25 then you're

81
00:06:23,730 --> 00:06:24,860
going to be charged for that.

82
00:06:24,870 --> 00:06:26,850
And usually you have a three tier.

83
00:06:26,850 --> 00:06:33,820
I believe the first 25 read and write the best units are free indexed data storage.

84
00:06:34,620 --> 00:06:40,980
So if you have any data in its history that you have saved and you're indexing through here then that

85
00:06:40,980 --> 00:06:45,140
is also going to be chargeable Internet data transfer.

86
00:06:45,150 --> 00:06:50,640
If you are querying the database from outside the region but if it is within the region you don't do

87
00:06:50,640 --> 00:06:51,020
that.

88
00:06:51,240 --> 00:06:58,590
You don't pick and there is a free account across all tables 25 free capacity units and 25 right capacity

89
00:06:58,590 --> 00:07:00,070
units per month.

90
00:07:00,120 --> 00:07:07,160
So you have these free but what if you have defined three tables and the three tables are getting 203

91
00:07:07,170 --> 00:07:13,110
capacity units and 150 drive capacity on units for instance then 25 will be free.

92
00:07:13,650 --> 00:07:15,450
And you would pay for that.

93
00:07:16,050 --> 00:07:16,640
All right.

94
00:07:16,830 --> 00:07:21,540
So let's take a break and talk in the next lecture about a very important feature of denim would be

95
00:07:21,540 --> 00:07:23,430
which is scalability.

96
00:07:23,460 --> 00:07:24,120
I'll see you then.