1
00:00:00,000 --> 00:00:04,969
>> [Music kucheza]

2
00:00:04,969 --> 00:00:06,010
RICK Houlihan: zote haki.

3
00:00:06,010 --> 00:00:06,600
Hi, kila mtu.

4
00:00:06,600 --> 00:00:07,670
Jina langu ni Rick Houlihan.

5
00:00:07,670 --> 00:00:10,330
Nina mkuu mwandamizi
ufumbuzi mbunifu katika AWS.

6
00:00:10,330 --> 00:00:14,070
Mimi kuzingatia NoSQL na
DynamoDB teknolojia.

7
00:00:14,070 --> 00:00:16,930
Mimi niko hapa leo kuzungumza na
wewe kidogo kuhusu hayo.

8
00:00:16,930 --> 00:00:18,970
>> Historia yangu ni
hasa katika safu data.

9
00:00:18,970 --> 00:00:21,390
Mimi alitumia maendeleo yangu nusu
kazi ya kuandika Mbegu,

10
00:00:21,390 --> 00:00:25,930
upatikanaji data, ufumbuzi
ajili ya matumizi mbalimbali.

11
00:00:25,930 --> 00:00:30,000
Nimekuwa katika wingu virtualization
kwa miaka 20 hivi.

12
00:00:30,000 --> 00:00:33,460
Hivyo kabla ya wingu ilikuwa wingu,
tulikuwa kuiita shirika kompyuta.

13
00:00:33,460 --> 00:00:37,170
Na wazo hilo, ni kama
PG & E, wewe kulipa kwa nini wewe kutumia.

14
00:00:37,170 --> 00:00:38,800
Leo sisi kuiita wingu.

15
00:00:38,800 --> 00:00:41,239
>> Lakini zaidi ya miaka, Nimepata kazi
kwa wanandoa wa makampuni

16
00:00:41,239 --> 00:00:42,530
umefanya pengine sijawahi kusikia.

17
00:00:42,530 --> 00:00:47,470
Lakini nimepata kukusanya orodha ya ufundi
mafanikio, mimi nadhani wewe d kusema.

18
00:00:47,470 --> 00:00:51,620
Nina ruhusu nane katika mifumo wingu
virtualization, microprocessor kubuni,

19
00:00:51,620 --> 00:00:54,440
tata tukio usindikaji,
na maeneo mengine pia.

20
00:00:54,440 --> 00:00:58,290
>> Hivyo siku hizi, mimi kuzingatia zaidi juu ya NoSQL
teknolojia na kizazi kijacho

21
00:00:58,290 --> 00:00:59,450
database.

22
00:00:59,450 --> 00:01:03,370
Na hiyo ndiyo ujumla nini mimi kwenda
kuwa hapa kuzungumza na wewe leo kuhusu.

23
00:01:03,370 --> 00:01:06,030
Hivyo nini unaweza kutarajia
kutoka kikao hiki,

24
00:01:06,030 --> 00:01:08,254
tutaweza kwenda kupitia kwa kifupi
historia ya usindikaji data.

25
00:01:08,254 --> 00:01:10,420
Ni siku zote na manufaa kwa
kuelewa tulikotoka

26
00:01:10,420 --> 00:01:12,400
na kwa nini tuko hapa tulipo.

27
00:01:12,400 --> 00:01:15,600
Na tutaweza kuongea kidogo
kidogo kuhusu NoSQL teknolojia

28
00:01:15,600 --> 00:01:17,500
kutoka kwa upande wa kimsingi.

29
00:01:17,500 --> 00:01:19,870
>> Sisi kupata katika baadhi ya
DynamoDB internals.

30
00:01:19,870 --> 00:01:24,350
DynamoDB ni AWS hakuna ladha.

31
00:01:24,350 --> 00:01:27,340
Ni kusimamiwa kikamilifu na
mwenyeji NoSQL ufumbuzi.

32
00:01:27,340 --> 00:01:32,420
Na tutaweza kuzungumza kidogo kuhusu meza
muundo, APIs, aina ya data, bahati,

33
00:01:32,420 --> 00:01:35,177
na baadhi ya internals
ya kwamba teknolojia DynamoDB.

34
00:01:35,177 --> 00:01:37,760
Tutaweza kupata katika baadhi ya kubuni
mwelekeo na mbinu bora.

35
00:01:37,760 --> 00:01:39,968
Tutaweza majadiliano juu ya jinsi
kutumia teknolojia hii kwa baadhi

36
00:01:39,968 --> 00:01:41,430
ya maombi ya leo.

37
00:01:41,430 --> 00:01:44,820
Na kisha tutaweza kuzungumza kidogo
kuhusu mageuzi au kuibuka

38
00:01:44,820 --> 00:01:48,980
ya dhana mpya katika programu
aitwaye maombi tukio inayotokana

39
00:01:48,980 --> 00:01:51,580
na jinsi DynamoDB anacheza katika kuwa vilevile.

40
00:01:51,580 --> 00:01:54,690
Na tutaweza kuondoka kidogo kidogo ya
kumbukumbu usanifu majadiliano

41
00:01:54,690 --> 00:01:59,540
ili tuweze kuzungumza kuhusu baadhi ya
njia unaweza kutumia DynamoDB.

42
00:01:59,540 --> 00:02:04,116
>> Hivyo kwanza off-- hili ni swali
Mimi kusikia mengi ni, nini database.

43
00:02:04,116 --> 00:02:06,240
Mengi ya watu wanadhani wao
kujua nini orodha ni.

44
00:02:06,240 --> 00:02:08,360
Kama Google, utaona huu.

45
00:02:08,360 --> 00:02:11,675
Ni kuweka muundo wa data uliofanyika
katika kompyuta, hasa moja ambayo

46
00:02:11,675 --> 00:02:13,600
ni kupatikana kwa njia mbalimbali.

47
00:02:13,600 --> 00:02:16,992
Nadhani hiyo ni nzuri
ufafanuzi wa database kisasa.

48
00:02:16,992 --> 00:02:19,450
Lakini mimi si kama hayo, kwa sababu
ina maana michache ya mambo.

49
00:02:19,450 --> 00:02:20,935
Ni ina maana muundo.

50
00:02:20,935 --> 00:02:23,120
Na inaonyesha kuwa ni juu ya kompyuta.

51
00:02:23,120 --> 00:02:25,750
Na database hakuwa
daima zipo kwenye kompyuta.

52
00:02:25,750 --> 00:02:28,020
Databaser kweli ulikuwepo kwa njia nyingi.

53
00:02:28,020 --> 00:02:32,000
>> Hivyo ufafanuzi mzuri wa
Mbegu ni kitu kama hiki.

54
00:02:32,000 --> 00:02:34,786
Mbegu ni kupangwa
utaratibu kwa ajili ya kuhifadhi, kusimamia,

55
00:02:34,786 --> 00:02:35,910
na kurejesha habari.

56
00:02:35,910 --> 00:02:36,868
Hii ni kutokana na About.com.

57
00:02:36,868 --> 00:02:42,080
Hivyo mimi kama hii kwa sababu ni kweli mazungumzo
kuhusu orodha akiwa there,

58
00:02:42,080 --> 00:02:44,800
uwepo wa
Maelezo, si lazima

59
00:02:44,800 --> 00:02:46,780
kitu kwamba yapo kwenye kompyuta.

60
00:02:46,780 --> 00:02:49,290
Na katika historia, sisi
si daima alikuwa kompyuta.

61
00:02:49,290 --> 00:02:52,110
>> Sasa, kama mimi kuuliza wastani
developer leo nini

62
00:02:52,110 --> 00:02:54,770
Mbegu, hiyo ni jibu mimi kupata.

63
00:02:54,770 --> 00:02:56,070
Mahali fulani siwezi fimbo mambo ya ajabu.

64
00:02:56,070 --> 00:02:56,670
Sawa?

65
00:02:56,670 --> 00:02:58,725
Na ni kweli.

66
00:02:58,725 --> 00:02:59,600
Lakini ni bahati mbaya.

67
00:02:59,600 --> 00:03:02,700
Kwa sababu database ni kweli
msingi wa programu ya kisasa.

68
00:03:02,700 --> 00:03:04,810
Ni msingi
ya kila maombi.

69
00:03:04,810 --> 00:03:07,240
Na jinsi wewe kujenga kwamba
Mbegu, jinsi muundo

70
00:03:07,240 --> 00:03:11,750
takwimu ambazo ni kwenda kulazimisha jinsi kwamba
maombi hufanya kama wewe kuongeza.

71
00:03:11,750 --> 00:03:14,640
>> Hivyo mengi ya kazi yangu leo
ni kushughulika na kile

72
00:03:14,640 --> 00:03:17,180
hutokea wakati watengenezaji
kuchukua mbinu hii

73
00:03:17,180 --> 00:03:19,510
na kushughulika na Aftermath
ya maombi ambayo

74
00:03:19,510 --> 00:03:24,966
sasa kuongeza zaidi ya awali
dhamira na mateso kutoka kwa kubuni mbaya.

75
00:03:24,966 --> 00:03:26,840
Hivyo hopefully wakati
kutembea mbali leo, utasikia

76
00:03:26,840 --> 00:03:29,010
kuwa wanandoa wa zana katika
ukanda yako kwamba itabidi kuweka wewe

77
00:03:29,010 --> 00:03:32,566
kutokana na kufanya makosa hizo hizo.

78
00:03:32,566 --> 00:03:33,066
Sawa.

79
00:03:33,066 --> 00:03:36,360
Basi hebu majadiliano juu kidogo ya
ratiba ya teknolojia database.

80
00:03:36,360 --> 00:03:38,830
Nadhani kusoma
Makala si kwamba zamani

81
00:03:38,830 --> 00:03:43,020
na ni alisema kitu juu ya lines--
ni kauli mashairi sana.

82
00:03:43,020 --> 00:03:46,590
Ilisema historia
ya data usindikaji ni

83
00:03:46,590 --> 00:03:49,350
kamili ya watermarks juu
wa takwimu wingi.

84
00:03:49,350 --> 00:03:49,920
SAWA.

85
00:03:49,920 --> 00:03:52,532
Sasa, mimi nadhani hiyo ni aina ya kweli.

86
00:03:52,532 --> 00:03:54,990
Lakini mimi kwa kweli kuangalia kama ipo
historia ni kweli kujazwa

87
00:03:54,990 --> 00:03:56,820
na watermark juu cha data shinikizo.

88
00:03:56,820 --> 00:04:00,040
Kwa sababu kiwango cha data ya
kumeza kamwe inakwenda chini.

89
00:04:00,040 --> 00:04:01,360
Ni tu huenda juu.

90
00:04:01,360 --> 00:04:03,670
>> Na uvumbuzi hutokea wakati
tunaona data shinikizo, ambayo

91
00:04:03,670 --> 00:04:07,825
ni kiasi cha data kwamba ni
sasa katika kuja katika mfumo.

92
00:04:07,825 --> 00:04:12,027
Na haiwezi kusindika
ufanisi ama katika wakati au katika gharama.

93
00:04:12,027 --> 00:04:14,110
Na kwamba wakati sisi kuanza
kuangalia data shinikizo.

94
00:04:14,110 --> 00:04:15,920
>> Hivyo wakati sisi kuangalia
Mbegu kwanza, hii

95
00:04:15,920 --> 00:04:17,180
ni moja kwamba alikuwa kati ya masikio yetu.

96
00:04:17,180 --> 00:04:18,310
Tuko wote waliozaliwa na hayo.

97
00:04:18,310 --> 00:04:19,194
Ni orodha nzuri.

98
00:04:19,194 --> 00:04:21,110
Ina upatikanaji juu.

99
00:04:21,110 --> 00:04:21,959
Ni siku zote juu ya.

100
00:04:21,959 --> 00:04:23,930
Daima unaweza kupata hiyo.

101
00:04:23,930 --> 00:04:24,890
>> Lakini ni mtumiaji moja.

102
00:04:24,890 --> 00:04:26,348
Siwezi kubadilishana mawazo yangu na wewe.

103
00:04:26,348 --> 00:04:28,370
Huwezi kupata mawazo yangu
wakati unataka yao.

104
00:04:28,370 --> 00:04:30,320
Na abilitiy zao si nzuri.

105
00:04:30,320 --> 00:04:32,510
Sisi kusahau mambo.

106
00:04:32,510 --> 00:04:36,540
Kila sasa na kisha, mmoja wetu majani
na hatua juu ya kuwepo kwa mwingine

107
00:04:36,540 --> 00:04:39,110
na sisi kupoteza kila kitu
aliyokuwa nayo kwamba database.

108
00:04:39,110 --> 00:04:40,640
Hivyo si kwamba wote kuwa nzuri.

109
00:04:40,640 --> 00:04:43,189
>> Na hii kazi vizuri baada ya muda
tulipokuwa nyuma katika siku

110
00:04:43,189 --> 00:04:46,230
wakati wote sisi kweli zinahitajika ili kujua ni
ambapo ni sisi kwenda juu ya kesho

111
00:04:46,230 --> 00:04:49,630
au ambapo sisi kukusanya chakula bora.

112
00:04:49,630 --> 00:04:52,820
Lakini kama sisi tulianza kukua kama
ustaarabu na serikali kuanza

113
00:04:52,820 --> 00:04:55,152
kuja katika kuwa, na
wafanyabiashara kuanza kuenea,

114
00:04:55,152 --> 00:04:57,360
sisi kuanza kutambua sisi
haja kidogo zaidi kuliko yale

115
00:04:57,360 --> 00:04:58,210
tunaweza kuweka katika kichwa chetu.

116
00:04:58,210 --> 00:04:58,870
Sawa?

117
00:04:58,870 --> 00:05:00,410
>> Sisi zinahitajika mifumo ya kumbukumbu.

118
00:05:00,410 --> 00:05:02,220
Sisi zinahitajika maeneo kuwa na uwezo data kuhifadhi.

119
00:05:02,220 --> 00:05:05,450
Hivyo sisi kuanza kuandika nyaraka,
kujenga maktaba na nyaraka.

120
00:05:05,450 --> 00:05:08,000
Tulianza kuendeleza
mfumo kitabu uhasibu.

121
00:05:08,000 --> 00:05:12,200
Na kwamba mfumo wa kitabu kuhesabu
mbio kote kwa karne nyingi,

122
00:05:12,200 --> 00:05:15,580
na labda hata milenia kama
sisi aina ya ilikua kwa uhakika

123
00:05:15,580 --> 00:05:18,420
ambapo kwamba mzigo data kuzidi
uwezo wa mifumo ya wale

124
00:05:18,420 --> 00:05:19,870
kuweza kuudhibiti.

125
00:05:19,870 --> 00:05:22,070
>> Na hii hasa kilichotokea katika miaka ya 1880.

126
00:05:22,070 --> 00:05:22,570
Sawa?

127
00:05:22,570 --> 00:05:24,390
Mwaka 1880 Sensa ya Marekani.

128
00:05:24,390 --> 00:05:26,976
Hii ni kweli ambapo kugeuka
uhakika data ya kisasa ya usindikaji.

129
00:05:26,976 --> 00:05:28,850
Hii ni hatua
ambayo kiasi cha data

130
00:05:28,850 --> 00:05:32,060
kwamba mara kuwa zilizokusanywa na
Serikali ya Marekani got kwa uhakika

131
00:05:32,060 --> 00:05:34,005
ambako ilichukua miaka minane mchakato.

132
00:05:34,005 --> 00:05:36,350
>> Sasa, years-- nane kama
unajua, Sensa

133
00:05:36,350 --> 00:05:39,180
anaendesha kila years-- 10 hivyo ni
pretty wazi kwamba kwa muda sisi

134
00:05:39,180 --> 00:05:41,419
got sensa 1890,
kiasi cha data kwamba

135
00:05:41,419 --> 00:05:43,210
alikuwa anaenda kuwa kusindika
na serikali ilikuwa ni

136
00:05:43,210 --> 00:05:46,335
kwenda kisichozidi miaka 10 kuwa ni
itachukua ilizindua sensa mpya.

137
00:05:46,335 --> 00:05:47,250
Hii ilikuwa ni tatizo.

138
00:05:47,250 --> 00:05:49,000
>> Hivyo guy aitwaye Herman
Hollerith alikuja pamoja

139
00:05:49,000 --> 00:05:52,640
na yeye zuliwa kitengo rekodi ngumi
kadi, Punch kadi msomaji, Punch kadi

140
00:05:52,640 --> 00:05:58,420
tabulator, na kulinganishwa ya
mifumo ya teknolojia hii.

141
00:05:58,420 --> 00:06:01,860
Na kwamba kampuni hiyo yeye sumu katika
muda, pamoja na michache ya watu wengine,

142
00:06:01,860 --> 00:06:05,450
kweli akawa moja ya nguzo za
kampuni ndogo tunajua leo inaitwa IBM.

143
00:06:05,450 --> 00:06:08,417
>> Hivyo IBM awali ilikuwa katika
biashara database.

144
00:06:08,417 --> 00:06:09,750
Na kwamba ni kweli walichofanya.

145
00:06:09,750 --> 00:06:11,110
Walivyofanya usindikaji data.

146
00:06:11,110 --> 00:06:15,400
>> Kama hivyo kuenea kwa ngumi
kadi, utaratibu wa ingenious

147
00:06:15,400 --> 00:06:18,560
wa kuwa na uwezo wa kujiinua kwamba
teknolojia ya uchaguzi yamepangwa matokeo seti.

148
00:06:18,560 --> 00:06:20,726
Unaweza kuona katika picha hii
kuna tuna little--

149
00:06:20,726 --> 00:06:23,970
ni kidogo small-- lakini unaweza kuona
ingenious sana mitambo utaratibu

150
00:06:23,970 --> 00:06:26,970
ambapo tuna Punch kadi ya staha.

151
00:06:26,970 --> 00:06:28,720
Na kuchukua mtu wa
bisibisi kidogo

152
00:06:28,720 --> 00:06:31,400
na kujikita kupitia
inafaa na kuondoa it up

153
00:06:31,400 --> 00:06:34,820
kupata kwamba mechi, kwamba
matokeo yamepangwa kuweka.

154
00:06:34,820 --> 00:06:36,270
>> Hii ni kuwakusanya.

155
00:06:36,270 --> 00:06:38,690
Sisi kufanya hivyo wakati wote
leo katika kompyuta,

156
00:06:38,690 --> 00:06:40,100
ambapo kufanya hivyo katika orodha.

157
00:06:40,100 --> 00:06:41,620
Tulikuwa kufanya hivyo manually, sawa?

158
00:06:41,620 --> 00:06:42,994
Watu kuweka mambo haya kwa pamoja.

159
00:06:42,994 --> 00:06:45,440
Na ilikuwa kuenea
wa kadi hizo ngumi

160
00:06:45,440 --> 00:06:50,070
katika kile sisi kuitwa ngoma data
na data reels, karatasi mkanda.

161
00:06:50,070 --> 00:06:55,980
>> Sekta ya usindikaji wa data alichukua
somo kutoka pianos mchezaji.

162
00:06:55,980 --> 00:06:57,855
Mchezaji pianos nyuma katika
upande wa karne

163
00:06:57,855 --> 00:07:02,100
kutumika kwa kutumia reels karatasi na inafaa
juu ya kupeleka habari ambayo funguo kucheza.

164
00:07:02,100 --> 00:07:05,380
Hivyo teknolojia ambayo ilichukuliwa
hatimaye kuhifadhi data digital,

165
00:07:05,380 --> 00:07:08,070
kwa sababu wangeweza kuweka takwimu ambazo
kwenye wale reels karatasi mkanda.

166
00:07:08,070 --> 00:07:10,870
>> Sasa, matokeo yake, data
ilikuwa actually-- jinsi

167
00:07:10,870 --> 00:07:14,960
wewe kupata data huyu alikuwa moja kwa moja
tegemezi kwa jinsi gani kuhifadhiwa yake.

168
00:07:14,960 --> 00:07:17,825
Hivyo kama mimi kuweka data juu ya mkanda,
Mimi nilikuwa kupata data kwa mstari.

169
00:07:17,825 --> 00:07:20,475
Mimi nilikuwa unaendelea nzima
mkanda kupata data zote.

170
00:07:20,475 --> 00:07:22,600
Kama mimi kuweka data katika ngumi
kadi, sikuweza kupata huduma hiyo

171
00:07:22,600 --> 00:07:26,270
katika kidogo zaidi random
mtindo, labda si kwa haraka.

172
00:07:26,270 --> 00:07:30,770
>> Lakini kulikuwa na mapungufu katika jinsi sisi
upatikanaji wa data kulingana na jinsi ilikuwa kuhifadhiwa.

173
00:07:30,770 --> 00:07:32,890
Na hivyo hii ilikuwa ni tatizo
kwenda katika '50s.

174
00:07:32,890 --> 00:07:37,890
Tena, tunaweza kuanza kuona kwamba kama sisi
kuendeleza teknolojia mpya na mchakato

175
00:07:37,890 --> 00:07:41,670
data, kulia, ni kufungua
mlango kwa ufumbuzi mpya,

176
00:07:41,670 --> 00:07:45,852
kwa ajili ya programu mpya, mpya
maombi kwa ajili ya data hizo.

177
00:07:45,852 --> 00:07:47,810
Na kwa kweli, utawala bora
inaweza kuwa ni sababu

178
00:07:47,810 --> 00:07:49,435
kwa nini sisi maendeleo ya baadhi ya mifumo hii.

179
00:07:49,435 --> 00:07:52,290
Lakini biashara kwa haraka akawa
dereva nyuma ya mageuzi

180
00:07:52,290 --> 00:07:54,720
ya Mbegu ya kisasa na
kisasa mfumo wa faili.

181
00:07:54,720 --> 00:07:56,870
>> Hivyo jambo la pili kwamba
walifika mara katika '50s

182
00:07:56,870 --> 00:08:00,780
Ilikuwa mfumo wa faili na
maendeleo ya random upatikanaji wa kuhifadhi.

183
00:08:00,780 --> 00:08:02,050
Hii ilikuwa nzuri.

184
00:08:02,050 --> 00:08:06,230
Sasa, kwa ghafla, tunaweza kuweka yetu
faili popote kwenye anatoa ngumu hizi

185
00:08:06,230 --> 00:08:09,760
na tuweze kupata taarifa hii nasibu.

186
00:08:09,760 --> 00:08:11,950
Tunaweza Hazrat kwamba
Maelezo nje ya mafaili.

187
00:08:11,950 --> 00:08:14,920
Na sisi kutatuliwa zote duniani
matatizo na usindikaji data.

188
00:08:14,920 --> 00:08:17,550
>> Na ambayo ilidumu kuhusu 20 au
Miaka 30 hadi mageuzi

189
00:08:17,550 --> 00:08:22,100
ya database kimahusiano, ambayo
ni wakati dunia aliamua sisi sasa

190
00:08:22,100 --> 00:08:27,940
haja ya kuwa na there kwamba kushindwa
oplanerad ya data katika faili

191
00:08:27,940 --> 00:08:29,540
mifumo ya kwamba tumekuwa kujengwa. Sawa?

192
00:08:29,540 --> 00:08:34,270
Data sana kusambazwa katika mengi mno
maeneo, de-kurudia ya data,

193
00:08:34,270 --> 00:08:37,120
na gharama za kuhifadhi ilikuwa kubwa sana.

194
00:08:37,120 --> 00:08:43,760
>> Katika '70s, rasilimali ghali zaidi
kwamba kompyuta alikuwa alikuwa hifadhi.

195
00:08:43,760 --> 00:08:46,200
Processor alikuwa
kutazamwa kama gharama za kudumu.

196
00:08:46,200 --> 00:08:49,030
Wakati mimi kununua sanduku,
CPU anafanya baadhi ya kazi.

197
00:08:49,030 --> 00:08:51,960
Ni kwenda kuwa inazunguka kama
ni kweli kazi au la.

198
00:08:51,960 --> 00:08:53,350
Hiyo ni kweli gharama kuzamishwa.

199
00:08:53,350 --> 00:08:56,030
>> Lakini nini gharama mimi kama
biashara ni hifadhi.

200
00:08:56,030 --> 00:09:00,020
Kama mimi na kununua disks zaidi ijayo
mwezi, hiyo ni gharama halisi kwamba mimi kulipa.

201
00:09:00,020 --> 00:09:01,620
Na kuhifadhi kwamba ni ghali.

202
00:09:01,620 --> 00:09:05,020
>> Sasa sisi kufunga mbele ya miaka 40
na tuna tatizo tofauti.

203
00:09:05,020 --> 00:09:10,020
Compute ni sasa
ghali zaidi rasilimali.

204
00:09:10,020 --> 00:09:11,470
Kuhifadhi ni nafuu.

205
00:09:11,470 --> 00:09:14,570
I mean, tunaweza kwenda mahali popote kwenye
wingu na tunaweza kupata kuhifadhi nafuu.

206
00:09:14,570 --> 00:09:17,190
Lakini nini siwezi kupata nafuu compute.

207
00:09:17,190 --> 00:09:20,700
>> Hivyo mageuzi ya leo
teknolojia, teknolojia ya Mbegu,

208
00:09:20,700 --> 00:09:23,050
ni kweli ililenga kuzunguka
databaser kusambazwa

209
00:09:23,050 --> 00:09:26,960
kwamba hawana wanakabiliwa na
aina moja ya wadogo

210
00:09:26,960 --> 00:09:29,240
mapungufu ya database kimahusiano.

211
00:09:29,240 --> 00:09:32,080
Tutaweza kuzungumza kidogo kuhusu
nini kwamba kweli ina maana.

212
00:09:32,080 --> 00:09:34,760
>> Lakini moja ya sababu na
dereva nyuma ya Haya sisi

213
00:09:34,760 --> 00:09:38,290
kuongelea shinikizo data.

214
00:09:38,290 --> 00:09:41,920
Takwimu shinikizo ni jambo ambalo
kwamba anatoa ubunifu.

215
00:09:41,920 --> 00:09:44,610
Na kama ukiangalia juu
miaka mitano iliyopita,

216
00:09:44,610 --> 00:09:48,180
hii ni chati ya nini data
mzigo katika biashara kwa ujumla

217
00:09:48,180 --> 00:09:49,640
Inaonekana kama katika miaka mitano iliyopita.

218
00:09:49,640 --> 00:09:52,570
>> Na utawala mkuu wa thumb
days-- hizi ukienda Google--

219
00:09:52,570 --> 00:09:55,290
ni 90% ya takwimu ambazo
sisi kuhifadhi leo, na ilikuwa

220
00:09:55,290 --> 00:09:57,330
yanayotokana ndani ya miaka miwili iliyopita.

221
00:09:57,330 --> 00:09:57,911
SAWA.

222
00:09:57,911 --> 00:09:59,410
Sasa, hii si mwenendo hiyo ni mpya.

223
00:09:59,410 --> 00:10:01,230
Hii ni hali ambayo imekuwa ni
kwenda nje kwa muda wa miaka 100.

224
00:10:01,230 --> 00:10:03,438
Tangu Herman Hollerith
maendeleo kadi Punch,

225
00:10:03,438 --> 00:10:08,040
tumekuwa kujenga hifadhi za seli data
na kukusanya data kwa viwango phenomenal.

226
00:10:08,040 --> 00:10:10,570
>> Hivyo katika kipindi cha miaka 100 iliyopita,
tumeona hali hii.

227
00:10:10,570 --> 00:10:11,940
Hiyo si kwenda na mabadiliko.

228
00:10:11,940 --> 00:10:14,789
Kwenda mbele, sisi ni kwenda kuona
hivyo, kama si kuharakisha mwenendo.

229
00:10:14,789 --> 00:10:16,330
Na unaweza kuona nini kwamba inaonekana kama.

230
00:10:16,330 --> 00:10:23,510
>> Kama biashara mwaka 2010 alikuwa mmoja
terabyte ya data chini ya usimamizi,

231
00:10:23,510 --> 00:10:27,080
leo kwamba maana wao uko
kusimamia 6.5 petabytes ya data.

232
00:10:27,080 --> 00:10:30,380
Hiyo ni 6,500 data zaidi ya mara.

233
00:10:30,380 --> 00:10:31,200
Na najua hii.

234
00:10:31,200 --> 00:10:33,292
Mimi kazi na wafanyabiashara hawa kila siku.

235
00:10:33,292 --> 00:10:35,000
Miaka mitano iliyopita, mimi
bila kuzungumza na makampuni

236
00:10:35,000 --> 00:10:38,260
ambao kuzungumza na mimi kuhusu kile maumivu
ni kusimamia terabytes wa data.

237
00:10:38,260 --> 00:10:39,700
Na wangeweza kuzungumza
na mimi kuhusu jinsi tunaona

238
00:10:39,700 --> 00:10:41,825
kwamba hii pengine ni kwenda
kuwa petabyte moja au mbili

239
00:10:41,825 --> 00:10:43,030
ndani ya miaka michache.

240
00:10:43,030 --> 00:10:45,170
>> Makampuni haya huo
leo mimi nina mkutano na,

241
00:10:45,170 --> 00:10:48,100
na wao ni kuzungumza na mimi kuhusu
Tatizo ni pale baada ya kusimamia

242
00:10:48,100 --> 00:10:51,440
mamia, 20 petabytes ya data.

243
00:10:51,440 --> 00:10:53,590
Hivyo mlipuko wa
data katika sekta ya

244
00:10:53,590 --> 00:10:56,670
ni kuendesha gari kubwa
haja kwa ajili ya ufumbuzi bora.

245
00:10:56,670 --> 00:11:00,980
Na database kimahusiano ni
sio tu kuishi hadi mahitaji.

246
00:11:00,980 --> 00:11:03,490
>> Na hivyo kuna linear
uwiano kati ya data shinikizo

247
00:11:03,490 --> 00:11:05,210
na ubunifu wa kiufundi.

248
00:11:05,210 --> 00:11:07,780
Historia imeonyesha sisi
hii, kwamba baada ya muda,

249
00:11:07,780 --> 00:11:11,090
wakati wowote kiasi cha data
kwamba mahitaji ya kuwa kusindika

250
00:11:11,090 --> 00:11:15,490
unazidi uwezo wa mfumo
kwa mchakato yake katika muda muafaka

251
00:11:15,490 --> 00:11:18,870
au kwa gharama nafuu,
teknolojia mpya kisha

252
00:11:18,870 --> 00:11:21,080
ni zuliwa ili kutatua matatizo hayo.

253
00:11:21,080 --> 00:11:24,090
Wale teknolojia mpya,
kwa upande wake, kufungua mlango

254
00:11:24,090 --> 00:11:27,840
hadi nyingine seti ya matatizo, ambayo
linakutana data hata zaidi.

255
00:11:27,840 --> 00:11:29,520
>> Sasa, sisi siyo kwenda kukomesha hali hii.

256
00:11:29,520 --> 00:11:30,020
Sawa?

257
00:11:30,020 --> 00:11:31,228
Sisi siyo kwenda kukomesha hali hii.

258
00:11:31,228 --> 00:11:31,830
Kwa nini?

259
00:11:31,830 --> 00:11:35,520
Kwa sababu huwezi kujua kila kitu
hapo ni kujua katika ulimwengu.

260
00:11:35,520 --> 00:11:40,510
Na kwa muda mrefu kama tumekuwa hai,
kipindi chote cha historia ya mwanadamu,

261
00:11:40,510 --> 00:11:43,440
sisi daima inaendeshwa kujua zaidi.

262
00:11:43,440 --> 00:11:49,840
>> Hivyo inaonekana kama kila inchi sisi hoja
chini njia ya ugunduzi wa kisayansi,

263
00:11:49,840 --> 00:11:54,620
sisi ni kuzidisha kiasi cha data
kuwa tunahitaji mchakato exponentially

264
00:11:54,620 --> 00:11:59,920
kama sisi kubaini zaidi na zaidi na zaidi
kuhusu utendaji kazi ndani ya maisha,

265
00:11:59,920 --> 00:12:04,530
kuhusu jinsi ulimwengu kazi, kuhusu
kuendesha gari ugunduzi wa kisayansi,

266
00:12:04,530 --> 00:12:06,440
na uvumbuzi kwamba
sisi ni kufanya leo.

267
00:12:06,440 --> 00:12:09,570
Kiasi cha data tu
daima huongezeka.

268
00:12:09,570 --> 00:12:12,120
Hivyo kuwa na uwezo wa kukabiliana na
tatizo hili ni kubwa sana.

269
00:12:12,120 --> 00:12:14,790

270
00:12:14,790 --> 00:12:17,410
>> Hivyo moja ya mambo
sisi kuangalia kama nini NoSQL?

271
00:12:17,410 --> 00:12:19,200
Ni kwa jinsi gani NoSQL kutatua tatizo hili?

272
00:12:19,200 --> 00:12:24,980
Naam, databaser kimahusiano,
Uliza muundo lugha,

273
00:12:24,980 --> 00:12:28,600
SQL-- hiyo kwa kweli kujenga ya
kimahusiano database-- mambo haya ni

274
00:12:28,600 --> 00:12:30,770
optimized kwa ajili ya kuhifadhi.

275
00:12:30,770 --> 00:12:33,180
>> Nyuma katika '70s, tena,
disk ni ghali.

276
00:12:33,180 --> 00:12:36,990
Utoaji zoezi la kuhifadhi
katika biashara ni kamwe-kuishia.

277
00:12:36,990 --> 00:12:37,490
Najua.

278
00:12:37,490 --> 00:12:38,020
Mimi aliishi yake.

279
00:12:38,020 --> 00:12:41,250
Niliandika madereva kuhifadhi kwa
Enterprised superserver kampuni

280
00:12:41,250 --> 00:12:42,470
nyuma katika miaka ya 90.

281
00:12:42,470 --> 00:12:45,920
Na line ya chini ni racking nyingine
kuhifadhi safu mara tu kitu ambacho

282
00:12:45,920 --> 00:12:47,600
kilichotokea kila siku katika biashara.

283
00:12:47,600 --> 00:12:49,030
Na kamwe kusimamishwa.

284
00:12:49,030 --> 00:12:52,690
Juu wiani kuhifadhi, mahitaji
kwa msongamano kuhifadhi,

285
00:12:52,690 --> 00:12:56,340
na kwa ajili ya kuhifadhi ufanisi zaidi
devices-- ni kamwe kusimamishwa.

286
00:12:56,340 --> 00:13:00,160
>> Na NoSQL ni teknolojia kubwa
kwa sababu normalizes data.

287
00:13:00,160 --> 00:13:02,210
Ni de-marudio data.

288
00:13:02,210 --> 00:13:07,180
Ni unaweka data katika muundo kwamba
ni agnostic kwa kila mfano upatikanaji.

289
00:13:07,180 --> 00:13:11,600
Maombi mbalimbali wanaweza kugonga kwamba
Database SQL, kukimbia dharula maswali,

290
00:13:11,600 --> 00:13:15,950
na kupata data katika sura kwamba wao
haja ya mchakato kwa mzigo wao.

291
00:13:15,950 --> 00:13:17,570
Kwamba inaonekana ajabu.

292
00:13:17,570 --> 00:13:21,350
Lakini line ya chini ni kwa yoyote
mfumo, ikiwa ni agnostic kwa kila kitu,

293
00:13:21,350 --> 00:13:23,500
ni optimized kwa ajili ya kitu chochote.

294
00:13:23,500 --> 00:13:24,050
SAWA?

295
00:13:24,050 --> 00:13:26,386
>> Na kwamba ni nini tunapata kwa
kimahusiano database.

296
00:13:26,386 --> 00:13:27,510
Ni optimized kwa ajili ya kuhifadhi.

297
00:13:27,510 --> 00:13:28,280
Ni kawaida.

298
00:13:28,280 --> 00:13:29,370
Ni kimahusiano.

299
00:13:29,370 --> 00:13:31,660
Ni inasaidia dharula maswali.

300
00:13:31,660 --> 00:13:34,000
Na yake na mizani wima.

301
00:13:34,000 --> 00:13:39,030
>> Kama mimi haja ya kupata kubwa SQL database
au nguvu zaidi SQL database,

302
00:13:39,030 --> 00:13:41,090
Mimi kwenda kununua kipande kubwa ya chuma.

303
00:13:41,090 --> 00:13:41,600
SAWA?

304
00:13:41,600 --> 00:13:44,940
Nimepata kazi na mengi ya wateja
kwamba wamekuwa kupitia upgrades kuu

305
00:13:44,940 --> 00:13:48,340
katika SQL miundombinu yao tu
ili kujua miezi sita baadaye,

306
00:13:48,340 --> 00:13:49,750
wao ni kupiga ukuta tena.

307
00:13:49,750 --> 00:13:55,457
Na jibu kutoka Oracle au MSSQL
au mtu yeyote mwingine ni kupata sanduku kubwa.

308
00:13:55,457 --> 00:13:58,540
Vizuri mapema au baadaye, huwezi kununua
kubwa sanduku, na kwamba tatizo halisi.

309
00:13:58,540 --> 00:14:00,080
Tunahitaji kweli kubadilisha mambo.

310
00:14:00,080 --> 00:14:01,080
Hivyo ambapo gani kazi hii?

311
00:14:01,080 --> 00:14:06,560
Ni kazi vizuri kwa nje ya mkondo
analytics, mzigo OLAP-aina.

312
00:14:06,560 --> 00:14:08,670
Na kwamba ni kweli ambapo SQL ni mwanachama.

313
00:14:08,670 --> 00:14:12,540
Sasa, ni kutumika leo katika wengi online
Mapatano usindikaji aina

314
00:14:12,540 --> 00:14:13,330
matumizi.

315
00:14:13,330 --> 00:14:16,460
Na ni kazi nzuri tu katika
baadhi ya kiwango cha matumizi,

316
00:14:16,460 --> 00:14:18,670
lakini ni tu haina wadogo
njia hiyo NoSQL gani.

317
00:14:18,670 --> 00:14:20,660
Na tutaweza kuongea kidogo
kidogo kuhusu nini kuwa ni.

318
00:14:20,660 --> 00:14:23,590
>> Sasa, NoSQL, kwa upande mwingine,
ni zaidi optimized kwa compute.

319
00:14:23,590 --> 00:14:24,540
SAWA?

320
00:14:24,540 --> 00:14:26,830
Sio agnostic kwa
upatikanaji mfano.

321
00:14:26,830 --> 00:14:31,620
Ni nini sisi kuwaita de-normalized
muundo au muundo wa kihierarkia.

322
00:14:31,620 --> 00:14:35,000
Data katika database kimahusiano ni
alijiunga pamoja na meza nyingi

323
00:14:35,000 --> 00:14:36,850
kuzalisha mtazamo kwamba unahitaji.

324
00:14:36,850 --> 00:14:40,090
Data database NoSQL katika
ni kuhifadhiwa katika hati kwamba

325
00:14:40,090 --> 00:14:42,100
ina muundo wa kihierarkia.

326
00:14:42,100 --> 00:14:45,670
Wote wa takwimu ambazo kwa kawaida kuwa
alijiunga pamoja na kuzalisha mtazamo kwamba

327
00:14:45,670 --> 00:14:47,160
ni kuhifadhiwa katika hati moja.

328
00:14:47,160 --> 00:14:50,990
Na tutaweza kuzungumza kidogo kuhusu
jinsi kazi katika michache ya chati.

329
00:14:50,990 --> 00:14:55,320
>> Lakini Wazo hapa ni kwamba kuhifadhi
data yako kama maoni haya instantiated.

330
00:14:55,320 --> 00:14:56,410
SAWA?

331
00:14:56,410 --> 00:14:58,610
Wewe kuongeza usawa.

332
00:14:58,610 --> 00:14:59,556
Sawa?

333
00:14:59,556 --> 00:15:02,100
Kama mimi haja ya kuongeza
ukubwa wa wangu NoSQL nguzo,

334
00:15:02,100 --> 00:15:03,700
Sina haja ya kupata sanduku kubwa.

335
00:15:03,700 --> 00:15:05,200
Mimi kupata sanduku mwingine.

336
00:15:05,200 --> 00:15:07,700
Na mimi nguzo wale pamoja,
na siwezi Shard data hizo.

337
00:15:07,700 --> 00:15:10,780
Tutaweza kuzungumza kidogo kuhusu
nini sharding ni, kuwa

338
00:15:10,780 --> 00:15:14,270
uwezo wa kuongeza kwamba orodha
katika vifaa vingi kimwili

339
00:15:14,270 --> 00:15:18,370
na kuondoa kikwazo kwamba
inahitaji kwangu wadogo wima.

340
00:15:18,370 --> 00:15:22,080
>> Hivyo ni kweli kujengwa kwa online
usindikaji shughuli na wadogo.

341
00:15:22,080 --> 00:15:25,480
Kuna tofauti kubwa
hapa kati ya kuripoti, sawa?

342
00:15:25,480 --> 00:15:27,810
Kuripoti, sijui
maswali mimi nina kwenda kuuliza.

343
00:15:27,810 --> 00:15:28,310
Sawa?

344
00:15:28,310 --> 00:15:30,570
Reporting-- kama mtu kutoka
idara ya masoko yangu

345
00:15:30,570 --> 00:15:34,520
anataka just-- wangapi wa wateja wangu
kuwa na tabia hii hasa ambao

346
00:15:34,520 --> 00:15:37,850
kununua juu ya day-- hii sijui
nini swala wao wanaenda kuomba.

347
00:15:37,850 --> 00:15:39,160
Hivyo mimi haja ya kuwa agnostic.

348
00:15:39,160 --> 00:15:41,810
>> Sasa, katika online
Mapatano maombi,

349
00:15:41,810 --> 00:15:43,820
Najua ni maswali gani mimi nina kuuliza.

350
00:15:43,820 --> 00:15:46,581
Mimi kujengwa maombi kwa
workflow maalum sana.

351
00:15:46,581 --> 00:15:47,080
SAWA?

352
00:15:47,080 --> 00:15:50,540
Hivyo kama mimi kuongeza data
kuhifadhi kusaidia kwamba workflow,

353
00:15:50,540 --> 00:15:52,020
ni kwenda kuwa kasi zaidi.

354
00:15:52,020 --> 00:15:55,190
Na hii ndiyo maana NoSQL Unaweza
kweli kuharakisha utoaji

355
00:15:55,190 --> 00:15:57,710
ya wale aina ya huduma.

356
00:15:57,710 --> 00:15:58,210
Sawa.

357
00:15:58,210 --> 00:16:00,501
>> Hivyo sisi ni kwenda kupata katika
kidogo ya nadharia hapa.

358
00:16:00,501 --> 00:16:03,330
Na baadhi yenu, macho yenu
Huenda unaendelea nyuma kidogo.

359
00:16:03,330 --> 00:16:06,936
Lakini mimi itabidi kujaribu kuweka
kiwango cha juu sana kama naweza.

360
00:16:06,936 --> 00:16:08,880
Hivyo kama wewe ni katika mradi
usimamizi, kuna

361
00:16:08,880 --> 00:16:12,280
kujenga aitwaye
pembe tatu ya vikwazo.

362
00:16:12,280 --> 00:16:12,936
SAWA.

363
00:16:12,936 --> 00:16:16,060
Pembe tatu ya constrains dictates
huwezi kuwa na kila kitu wakati wote.

364
00:16:16,060 --> 00:16:17,750
Huwezi kuwa na pie yako na kula sana.

365
00:16:17,750 --> 00:16:22,310
Hivyo katika usimamizi wa mradi, kwamba pembe tatu
vikwazo ni unaweza kuwa ni nafuu,

366
00:16:22,310 --> 00:16:24,710
unaweza kuwa ni haraka,
au unaweza kuwa ni mzuri.

367
00:16:24,710 --> 00:16:25,716
Pick mbili.

368
00:16:25,716 --> 00:16:27,090
Kwa sababu huwezi kuwa wote watatu.

369
00:16:27,090 --> 00:16:27,460
Sawa?

370
00:16:27,460 --> 00:16:27,820
SAWA.

371
00:16:27,820 --> 00:16:28,920
>> Hivyo wewe kusikia kuhusu hili sana.

372
00:16:28,920 --> 00:16:31,253
Ni kikwazo tatu,
pembe tatu ya mara tatu kulazimika,

373
00:16:31,253 --> 00:16:34,420
au chuma pembe tatu ni oftentimes--
wakati majadiliano kwa mradi mameneja,

374
00:16:34,420 --> 00:16:35,420
wao itabidi kuzungumza kuhusu suala hili.

375
00:16:35,420 --> 00:16:37,640
Sasa, databaser na
chuma yao wenyewe pembe tatu.

376
00:16:37,640 --> 00:16:40,350
Na chuma pembe tatu ya data
ni nini sisi kuwaita CAP theorem.

377
00:16:40,350 --> 00:16:41,580
SAWA?

378
00:16:41,580 --> 00:16:43,770
>> CAP theorem dictates
jinsi database kazi

379
00:16:43,770 --> 00:16:45,627
chini ya hali maalum sana.

380
00:16:45,627 --> 00:16:47,460
Na tutaweza majadiliano juu ya
nini hali hiyo ni.

381
00:16:47,460 --> 00:16:52,221
Lakini pointi tatu ya pembe tatu,
hivyo kusema, ni C, msimamo.

382
00:16:52,221 --> 00:16:52,720
SAWA?

383
00:16:52,720 --> 00:16:56,760
Hivyo katika CAP, na msimamo ina maana kwamba wote
wateja ambao wanaweza kupata orodha

384
00:16:56,760 --> 00:16:59,084
siku zote kuwa sana
Mtazamo thabiti ya data.

385
00:16:59,084 --> 00:17:00,750
Hakuna mtu wa gonna kuona mambo mawili tofauti.

386
00:17:00,750 --> 00:17:01,480
SAWA?

387
00:17:01,480 --> 00:17:04,020
Kama mimi kuona Mbegu,
Mimi nina kuona mtazamo huo

388
00:17:04,020 --> 00:17:06,130
kama mpenzi wangu ambaye anaona
Mbegu huo.

389
00:17:06,130 --> 00:17:07,470
Hiyo ni msimamo.

390
00:17:07,470 --> 00:17:12,099
>> Upatikanaji ina maana kwamba kama
Mbegu online, kama inaweza kufikiwa,

391
00:17:12,099 --> 00:17:14,760
kwamba wateja wote daima
kuwa na uwezo wa kusoma na kuandika.

392
00:17:14,760 --> 00:17:15,260
SAWA?

393
00:17:15,260 --> 00:17:17,010
Hivyo kila mteja kwamba
Unaweza kusoma orodha

394
00:17:17,010 --> 00:17:18,955
daima kuwa na uwezo wa kusoma
data na kuandika data.

395
00:17:18,955 --> 00:17:21,819
Na kama hiyo kesi,
ni mfumo inapatikana.

396
00:17:21,819 --> 00:17:24,230
>> Na hatua ya tatu ni nini
tunatoa wito kuhesabu uvumilivu.

397
00:17:24,230 --> 00:17:24,730
SAWA?

398
00:17:24,730 --> 00:17:28,160
Kuhesabu uvumilivu njia
kuwa mfumo wa kazi vizuri

399
00:17:28,160 --> 00:17:32,000
licha ya mtandao kimwili
partitions kati ya nodes.

400
00:17:32,000 --> 00:17:32,760
SAWA?

401
00:17:32,760 --> 00:17:36,270
Hivyo nodes katika nguzo hawawezi
kuzungumza na kila mmoja, nini kitatokea?

402
00:17:36,270 --> 00:17:36,880
Sawa.

403
00:17:36,880 --> 00:17:39,545
>> Databaser hivyo kimahusiano choose--
unaweza kuchukua wawili hawa.

404
00:17:39,545 --> 00:17:40,045
SAWA.

405
00:17:40,045 --> 00:17:43,680
Databaser hivyo kimahusiano kuchagua
kuwa thabiti na za kutosha.

406
00:17:43,680 --> 00:17:47,510
Kama kuhesabu hutokea kati ya
DataNodes katika kuhifadhi data,

407
00:17:47,510 --> 00:17:48,831
Mbegu shambulio.

408
00:17:48,831 --> 00:17:49,330
Sawa?

409
00:17:49,330 --> 00:17:50,900
Ni tu inakwenda chini.

410
00:17:50,900 --> 00:17:51,450
SAWA.

411
00:17:51,450 --> 00:17:54,230
>> Na hii ni kwa nini wana
kukua na masanduku kubwa.

412
00:17:54,230 --> 00:17:54,730
Sawa?

413
00:17:54,730 --> 00:17:58,021
Kwa sababu kuna no-- kawaida, nguzo
Mbegu, kuna si mengi sana miongoni mwao

414
00:17:58,021 --> 00:17:59,590
ambayo yanafanya kazi kwa njia hiyo.

415
00:17:59,590 --> 00:18:03,019
Lakini databaser zaidi wadogo
wima ndani ya sanduku moja.

416
00:18:03,019 --> 00:18:05,060
Kwa sababu wanahitaji kuwa
thabiti na za kutosha.

417
00:18:05,060 --> 00:18:10,320
Kama kuhesabu zilipaswa sindano,
basi ingekuwa kufanya uchaguzi.

418
00:18:10,320 --> 00:18:13,720
Una kufanya uchaguzi kati
kuwa thabiti na za kutosha.

419
00:18:13,720 --> 00:18:16,080
>> Na kwamba ni nini NoSQL databaser kufanya.

420
00:18:16,080 --> 00:18:16,580
Sawa.

421
00:18:16,580 --> 00:18:20,950
Hivyo orodha NoSQL, ni
huja katika ladha mbili.

422
00:18:20,950 --> 00:18:22,990
Sisi have-- vizuri,
huja katika ladha nyingi,

423
00:18:22,990 --> 00:18:26,140
lakini inakuja na mawili ya msingi
characteristics-- nini

424
00:18:26,140 --> 00:18:30,050
tunataka kuwaita CP Mbegu, au a
thabiti na kuhesabu uvumilivu

425
00:18:30,050 --> 00:18:31,040
mfumo.

426
00:18:31,040 --> 00:18:34,930
Haya guys kufanya uchaguzi kwamba wakati
nodes kupoteza kuwasiliana na kila mmoja,

427
00:18:34,930 --> 00:18:37,091
sisi siyo kwenda kuruhusu
watu kuandika tena.

428
00:18:37,091 --> 00:18:37,590
SAWA?

429
00:18:37,590 --> 00:18:41,855
>> Mpaka kwamba kuhesabu ni kuondolewa,
upatikanaji kuandika ni imefungwa.

430
00:18:41,855 --> 00:18:43,230
Hiyo ina maana wao ni haipatikani.

431
00:18:43,230 --> 00:18:44,510
Wao ni thabiti.

432
00:18:44,510 --> 00:18:46,554
Wakati tunaona kwamba
kuhesabu kuingiza yenyewe,

433
00:18:46,554 --> 00:18:48,470
sasa tuko thabiti,
kwa sababu sisi siyo kwenda

434
00:18:48,470 --> 00:18:51,517
kuruhusu mabadiliko data kwenye miwili
pande mbili za kuhesabu kujitegemea

435
00:18:51,517 --> 00:18:52,100
ya kila mmoja.

436
00:18:52,100 --> 00:18:54,130
Tutakuwa na
upya mawasiliano

437
00:18:54,130 --> 00:18:56,930
kabla ya update yoyote kwa
data ni kuruhusiwa.

438
00:18:56,930 --> 00:18:58,120
SAWA?

439
00:18:58,120 --> 00:19:02,650
>> Ladha ya pili itakuwa mfumo AP,
au inapatikana na partitioned

440
00:19:02,650 --> 00:19:03,640
kuvumiliana mfumo.

441
00:19:03,640 --> 00:19:05,320
Haya guys hawajali.

442
00:19:05,320 --> 00:19:06,020
Sawa?

443
00:19:06,020 --> 00:19:08,960
Node yoyote ambayo anapata
kuandika, tutaweza kuchukua hiyo.

444
00:19:08,960 --> 00:19:11,480
Hivyo mimi nina kujinakilisha data zangu
hela nodes nyingi.

445
00:19:11,480 --> 00:19:14,730
Nodi hiyo kupata mteja, mteja anakuja
katika, anasema, mimi nina kwenda kuandika baadhi ya data.

446
00:19:14,730 --> 00:19:16,300
Node anasema, hakuna tatizo.

447
00:19:16,300 --> 00:19:18,580
Nodi karibu naye anapata
kuandika kwenye rekodi sawa,

448
00:19:18,580 --> 00:19:20,405
yeye kwenda kusema hakuna tatizo.

449
00:19:20,405 --> 00:19:23,030
Mahali fulani nyuma mgongoni mwisho,
data ambayo inaenda kuiga.

450
00:19:23,030 --> 00:19:27,360
Na kisha mtu kwenda kutambua,
uh-oh, mfumo watakubali, uh-oh,

451
00:19:27,360 --> 00:19:28,870
kumekuwa na update kwa pande hizo mbili.

452
00:19:28,870 --> 00:19:30,370
Tufanye nini?

453
00:19:30,370 --> 00:19:33,210
Na wanachokifanya basi ni
wanafanya kitu ambacho

454
00:19:33,210 --> 00:19:36,080
inaruhusu yao ya kutatua kwamba hali data.

455
00:19:36,080 --> 00:19:39,000
Na tutaweza majadiliano juu ya
kwamba katika chati ijayo.

456
00:19:39,000 --> 00:19:40,000
>> Jambo kwa kumweka nje hapa.

457
00:19:40,000 --> 00:19:42,374
Na mimi si kwenda kupata pia
mengi katika hili, kwa sababu hii

458
00:19:42,374 --> 00:19:43,510
anapata katika nadharia kina data.

459
00:19:43,510 --> 00:19:46,670
Lakini kuna Mapatano
mfumo kuwa

460
00:19:46,670 --> 00:19:50,680
anaendesha katika mfumo kimahusiano kwamba
inaruhusu mimi kwa usalama kufanya updates

461
00:19:50,680 --> 00:19:53,760
kwa nyingi vyombo katika database.

462
00:19:53,760 --> 00:19:58,320
Na updates wale kutokea
wote kwa mara moja au si wakati wote.

463
00:19:58,320 --> 00:20:00,500
Na hii inaitwa shughuli ACID.

464
00:20:00,500 --> 00:20:01,000
SAWA?

465
00:20:01,000 --> 00:20:06,570
>> ACID inatupa atomicity, msimamo,
kutengwa, na kudumu.

466
00:20:06,570 --> 00:20:07,070
SAWA?

467
00:20:07,070 --> 00:20:13,550
Hiyo ina maana atomic, shughuli, kila
updates yangu ama kutokea au wao hawana.

468
00:20:13,550 --> 00:20:16,570
Msimamo maana yake ni kwamba
Mbegu daima

469
00:20:16,570 --> 00:20:19,780
kuletwa thabiti
hali baada ya update.

470
00:20:19,780 --> 00:20:23,900
Sitakuacha kamwe orodha katika
hali mbaya baada ya kutumia update.

471
00:20:23,900 --> 00:20:24,400
SAWA?

472
00:20:24,400 --> 00:20:26,720
>> Hivyo ni tofauti kidogo
kuliko CAP msimamo.

473
00:20:26,720 --> 00:20:29,760
CAP msimamo ina maana wote yangu
wateja wanaweza daima kuona data.

474
00:20:29,760 --> 00:20:34,450
ACID msimamo ina maana kwamba wakati
shughuli kosa, takwimu nzuri.

475
00:20:34,450 --> 00:20:35,709
Mahusiano yangu wote ni nzuri.

476
00:20:35,709 --> 00:20:38,750
Sitakuja kufuta mstari mzazi
na kuondoka rundo la watoto yatima

477
00:20:38,750 --> 00:20:40,970
katika baadhi meza mengine.

478
00:20:40,970 --> 00:20:44,320
Ni haiwezi kutokea kama mimi nina thabiti
katika shughuli asidi.

479
00:20:44,320 --> 00:20:49,120
>> Kutengwa ina maana kwamba shughuli
daima kutokea mmoja baada ya mwingine.

480
00:20:49,120 --> 00:20:51,920
Matokeo ya mwisho ya data
itakuwa hali hiyo

481
00:20:51,920 --> 00:20:54,770
kana kwamba shughuli hizo
kwamba zilitolewa Sanjari

482
00:20:54,770 --> 00:20:57,340
waliuawa serially.

483
00:20:57,340 --> 00:21:00,030
Hivyo ni concurrency
udhibiti katika database.

484
00:21:00,030 --> 00:21:04,130
Hivyo kimsingi, siwezi increment
thamani huo mara mbili kwa shughuli mbili.

485
00:21:04,130 --> 00:21:08,580
>> Lakini kama mimi kusema kuongeza 1 kwa thamani hii,
na shughuli mbili kuja katika

486
00:21:08,580 --> 00:21:10,665
na kujaribu kufanya hivyo, moja ni
kwenda kupata huko kwanza

487
00:21:10,665 --> 00:21:12,540
na wengine mtu
kwenda kupata huko baada.

488
00:21:12,540 --> 00:21:15,210
Hivyo katika mwisho, mimi aliongeza mbili.

489
00:21:15,210 --> 00:21:16,170
Unaweza kuona nini namaanisha?

490
00:21:16,170 --> 00:21:16,670
SAWA.

491
00:21:16,670 --> 00:21:19,220

492
00:21:19,220 --> 00:21:21,250
>> Uimara ni pretty moja kwa moja.

493
00:21:21,250 --> 00:21:23,460
Wakati shughuli
ni alikubali, ni

494
00:21:23,460 --> 00:21:26,100
kwenda kuwa kuna hata
kama mfumo shambulio.

495
00:21:26,100 --> 00:21:29,230
Wakati mfumo kuwa recovers, kwamba
shughuli ambayo ilikuwa nia

496
00:21:29,230 --> 00:21:30,480
ni kweli kwenda huko.

497
00:21:30,480 --> 00:21:33,130
Hivyo hiyo ni dhamana
ya mashirikiano ACID.

498
00:21:33,130 --> 00:21:35,470
Hayo ni dhamana pretty nzuri
kuwa juu ya orodha,

499
00:21:35,470 --> 00:21:36,870
lakini wao kuja kwa gharama hiyo.

500
00:21:36,870 --> 00:21:37,640
Sawa?

501
00:21:37,640 --> 00:21:40,520
>> Kwa sababu tatizo
kwa mfumo huu ni

502
00:21:40,520 --> 00:21:44,540
kama kuna kuhesabu katika data
kuweka, I have kufanya uamuzi.

503
00:21:44,540 --> 00:21:48,000
Mimi naenda kuwa kuruhusu
taarifa juu ya upande mmoja au mwingine.

504
00:21:48,000 --> 00:21:50,310
Na kama hiyo itatokea,
basi mimi nina hakuna kwenda tena

505
00:21:50,310 --> 00:21:52,630
kuwa na uwezo wa kudumisha
wale sifa.

506
00:21:52,630 --> 00:21:53,960
Hawawezi kuwa thabiti.

507
00:21:53,960 --> 00:21:55,841
Wao si kutengwa.

508
00:21:55,841 --> 00:21:58,090
Hii ni pale ambapo umekwisha
kwa database kimahusiano.

509
00:21:58,090 --> 00:22:01,360
Hii ni sababu kimahusiano
databaser wadogo wima.

510
00:22:01,360 --> 00:22:05,530
>> Kwa upande mwingine, tuna
kile kinachoitwa BASE teknolojia.

511
00:22:05,530 --> 00:22:07,291
Na haya ndiyo NoSQL Databases yako.

512
00:22:07,291 --> 00:22:07,790
Sawa.

513
00:22:07,790 --> 00:22:10,180
Hivyo tuna CP yetu, AP database.

514
00:22:10,180 --> 00:22:14,720
Na haya ndiyo nini wito kimsingi
inapatikana, hali laini, hatimaye

515
00:22:14,720 --> 00:22:15,740
thabiti.

516
00:22:15,740 --> 00:22:16,420
SAWA?

517
00:22:16,420 --> 00:22:19,690
>> Kimsingi inapatikana, kwa sababu
wao uko kuhesabu kuhimili.

518
00:22:19,690 --> 00:22:21,470
Wao siku zote kuwa
pale, hata kama kuna

519
00:22:21,470 --> 00:22:23,053
kuhesabu mtandao kati ya nodes.

520
00:22:23,053 --> 00:22:25,900
Kama naweza kuzungumza na node, mimi nina
kwenda kuwa na uwezo wa kusoma data.

521
00:22:25,900 --> 00:22:26,460
SAWA?

522
00:22:26,460 --> 00:22:30,810
Nipate si mara zote na uwezo wa kuandika
data kama mimi nina jukwaa thabiti.

523
00:22:30,810 --> 00:22:32,130
Lakini mimi utakuwa na uwezo wa kusoma data.

524
00:22:32,130 --> 00:22:34,960

525
00:22:34,960 --> 00:22:38,010
>> Hali laini inaonyesha
kwamba wakati mimi kusoma data kwamba,

526
00:22:38,010 --> 00:22:40,790
wanaweza kuwa sawa na nodes nyingine.

527
00:22:40,790 --> 00:22:43,390
Kama haki ilitolewa juu ya nodi
mahali pengine katika nguzo

528
00:22:43,390 --> 00:22:46,650
na hivyo siyo kuigwa katika
nguzo lakini wakati mimi kusoma kwamba data,

529
00:22:46,650 --> 00:22:48,680
hali ambayo inaweza kuwa thabiti.

530
00:22:48,680 --> 00:22:51,650
Hata hivyo, itakuwa ni
Hatimaye thabiti,

531
00:22:51,650 --> 00:22:53,870
kwa maana ya kuwa wakati kuandika
ni kufanywa na mfumo,

532
00:22:53,870 --> 00:22:56,480
itakuwa kuiga hela nodes.

533
00:22:56,480 --> 00:22:59,095
Na hatimaye, kwamba hali
atapelekwa katika utaratibu,

534
00:22:59,095 --> 00:23:00,890
na itakuwa hali thabiti.

535
00:23:00,890 --> 00:23:05,000
>> Sasa, CAP theorem kweli
ina tu katika hali moja.

536
00:23:05,000 --> 00:23:08,700
Masharti kwamba ni wakati hii hutokea.

537
00:23:08,700 --> 00:23:13,710
Kwa sababu wakati wowote ni kufanya kazi katika
hali ya kawaida, hakuna kuhesabu,

538
00:23:13,710 --> 00:23:16,370
kila kitu ni thabiti na za kutosha.

539
00:23:16,370 --> 00:23:19,990
Wewe tu na wasiwasi juu ya CAP
wakati tuna kuwa kuhesabu.

540
00:23:19,990 --> 00:23:21,260
Hivyo wale ni nadra.

541
00:23:21,260 --> 00:23:25,360
Lakini jinsi mfumo humenyuka wakati wale
kutokea kulazimisha aina gani ya mfumo

542
00:23:25,360 --> 00:23:26,750
sisi ni kushughulika na.

543
00:23:26,750 --> 00:23:31,110
>> Basi hebu tuangalie nini
kwamba inaonekana kama kwa mifumo AP.

544
00:23:31,110 --> 00:23:32,621
SAWA?

545
00:23:32,621 --> 00:23:34,830
Mifumo AP kuja katika ladha mbili.

546
00:23:34,830 --> 00:23:38,514
Wao kuja katika ladha kwamba ni
bwana bwana, 100%, daima inapatikana.

547
00:23:38,514 --> 00:23:40,430
Na wao kuja katika
ladha nyingine, ambayo inasema,

548
00:23:40,430 --> 00:23:43,330
unajua nini, mimi nina kwenda kuwa na wasiwasi
kuhusu hili jambo partitioning

549
00:23:43,330 --> 00:23:44,724
wakati kuhesabu halisi hutokea.

550
00:23:44,724 --> 00:23:47,890
Vinginevyo, kuna kwenda kuwa msingi
nodes ambao kwenda kuchukua haki.

551
00:23:47,890 --> 00:23:48,500
SAWA?

552
00:23:48,500 --> 00:23:50,040
>> Hivyo kama sisi kitu kama Cassandra.

553
00:23:50,040 --> 00:23:54,440
Cassandra itakuwa bwana
bwana, basi ni mimi kuandika kwa node yoyote.

554
00:23:54,440 --> 00:23:55,540
Hivyo kile kinachotokea?

555
00:23:55,540 --> 00:23:58,270
Hivyo nina kitu katika
Mbegu ambayo ipo juu ya nodes mbili.

556
00:23:58,270 --> 00:24:01,705
Hebu simu kwamba kitu S.
Hivyo tuna hali ya S.

557
00:24:01,705 --> 00:24:04,312
Tuna baadhi ya shughuli
juu ya S kwamba zinaendelea.

558
00:24:04,312 --> 00:24:06,270
Cassandra inaruhusu mimi
kuandika kwa nodes nyingi.

559
00:24:06,270 --> 00:24:08,550
Basi hebu kusema mimi kupata
kuandika kwa s kwa nodes mbili.

560
00:24:08,550 --> 00:24:12,274
Naam, ni nini kuishia kinachotokea ni
tunatoa wito kwamba tukio partitioning.

561
00:24:12,274 --> 00:24:14,190
Kuna inaweza kuwa
kimwili kuhesabu mtandao.

562
00:24:14,190 --> 00:24:15,950
Lakini kwa sababu ya muundo
mfumo, ni

563
00:24:15,950 --> 00:24:18,449
kweli partitioning haraka
kama mimi kupata kuandika juu ya nodes mbili.

564
00:24:18,449 --> 00:24:20,830
Siyo kulazimisha kwangu
kuandika wote kwa njia ya nodi moja.

565
00:24:20,830 --> 00:24:22,340
Mimi nina kuandika juu ya nodes mbili.

566
00:24:22,340 --> 00:24:23,330
SAWA?

567
00:24:23,330 --> 00:24:25,740
>> Hivyo sasa nina majimbo mawili.

568
00:24:25,740 --> 00:24:26,360
SAWA?

569
00:24:26,360 --> 00:24:28,110
Nini kitatokea
ni mapema au baadaye,

570
00:24:28,110 --> 00:24:29,960
kuna kwenda kuwa tukio replication.

571
00:24:29,960 --> 00:24:33,300
Kuna kwenda kuwa nini sisi
aitwaye kuhesabu ahueni, ambayo

572
00:24:33,300 --> 00:24:35,200
Hapa ndipo hizi mbili
mataifa kurudi pamoja

573
00:24:35,200 --> 00:24:37,310
na kuna kwenda kuwa algorithm
kwamba anaendesha ndani ya Mbegu,

574
00:24:37,310 --> 00:24:38,540
anaamua nini cha kufanya.

575
00:24:38,540 --> 00:24:39,110
SAWA?

576
00:24:39,110 --> 00:24:43,057
By default, mwisho update
mafanikio katika maeneo mengi ya mifumo AP.

577
00:24:43,057 --> 00:24:44,890
Hivyo kuna kawaida
chaguo-msingi algorithm, nini

578
00:24:44,890 --> 00:24:47,400
watataka callback
kazi, jambo ambalo

579
00:24:47,400 --> 00:24:51,000
wataitwa wakati hali hii
ni wanaona kutekeleza baadhi ya mantiki

580
00:24:51,000 --> 00:24:52,900
kutatua mgogoro huo.

581
00:24:52,900 --> 00:24:53,850
SAWA?

582
00:24:53,850 --> 00:24:58,770
Callback chaguo-msingi na chaguo-msingi
resolver katika zaidi databaser AP

583
00:24:58,770 --> 00:25:01,130
ni, nadhani nini, timestamp mafanikio.

584
00:25:01,130 --> 00:25:02,380
Hii ilikuwa ni update ya mwisho.

585
00:25:02,380 --> 00:25:04,320
Mimi nina kwenda kuweka kwamba update huko.

586
00:25:04,320 --> 00:25:08,440
Nipate dampo rekodi hii kwamba mimi
kutupwa mbali katika gogo ahueni

587
00:25:08,440 --> 00:25:11,670
hivyo kwamba mtumiaji anaweza kurudi baadaye
na kusema, hey, kulikuwa na mgongano.

588
00:25:11,670 --> 00:25:12,320
Ni nini kilichotokea?

589
00:25:12,320 --> 00:25:16,370
Na unaweza kweli dampo rekodi ya
zote migongano na rollbacks

590
00:25:16,370 --> 00:25:17,550
na kuona nini kinatokea.

591
00:25:17,550 --> 00:25:21,580
>> Sasa, kama user, unaweza pia
pamoja na mantiki katika kwamba callback.

592
00:25:21,580 --> 00:25:24,290
Hivyo unaweza mabadiliko hayo
callback operesheni.

593
00:25:24,290 --> 00:25:26,730
Unaweza kusema, hey, nataka
kwa remediate taarifa hii.

594
00:25:26,730 --> 00:25:28,880
Na mimi nataka kujaribu na
kuunganisha kumbukumbu hizo mbili.

595
00:25:28,880 --> 00:25:30,050
Lakini hiyo ni juu yako.

596
00:25:30,050 --> 00:25:32,880
Mbegu hajui jinsi ya
kufanya hivyo kwa chaguo-msingi. Wengi wakati,

597
00:25:32,880 --> 00:25:34,850
Kitu pekee orodha
anajua jinsi ya kufanya ni kusema,

598
00:25:34,850 --> 00:25:36,100
hii moja ilikuwa ni rekodi iliyopita.

599
00:25:36,100 --> 00:25:39,183
Hiyo ni moja ambayo inaenda kushinda,
na kwamba thamani mimi nina kwenda kuweka.

600
00:25:39,183 --> 00:25:41,490
Mara baada ya kuwa kuhesabu ahueni
na replication hutokea,

601
00:25:41,490 --> 00:25:43,930
tuna hali yetu, ambayo
sasa S mkuu, ambayo ni

602
00:25:43,930 --> 00:25:46,890
kuunganisha hali ya wale vitu vyote.

603
00:25:46,890 --> 00:25:49,700
Hivyo mifumo AP na hii.

604
00:25:49,700 --> 00:25:51,615
Mifumo CP hawana haja
na wasiwasi juu ya hili.

605
00:25:51,615 --> 00:25:54,490
Kwa sababu kwa haraka kama kuhesabu linatokana
katika kucheza, wao tu kuacha kutumia

606
00:25:54,490 --> 00:25:55,530
anaandika.

607
00:25:55,530 --> 00:25:56,180
SAWA?

608
00:25:56,180 --> 00:25:58,670
Hivyo hiyo ni rahisi sana
kukabiliana na kuwa thabiti

609
00:25:58,670 --> 00:26:01,330
wakati huna kukubali updates yoyote.

610
00:26:01,330 --> 00:26:04,620
Hiyo ni pamoja na mifumo CP kufanya.

611
00:26:04,620 --> 00:26:05,120
Sawa.

612
00:26:05,120 --> 00:26:07,590
>> Hivyo hebu majadiliano kidogo
kidogo kuhusu upatikanaji mwelekeo.

613
00:26:07,590 --> 00:26:11,580
Tunapozungumzia kuhusu NoSQL, ni
wote kuhusu upatikanaji mfano.

614
00:26:11,580 --> 00:26:13,550
Sasa, SQL ni dharula, maswali.

615
00:26:13,550 --> 00:26:14,481
Ni kimahusiano kuhifadhi.

616
00:26:14,481 --> 00:26:16,480
Hatuna wasiwasi
kuhusu upatikanaji mfano.

617
00:26:16,480 --> 00:26:17,688
Mimi kuandika swala ngumu sana.

618
00:26:17,688 --> 00:26:19,250
Ni inakwenda na anapata data.

619
00:26:19,250 --> 00:26:21,210
Hiyo ni nini inaonekana huu
kama, kuhalalisha.

620
00:26:21,210 --> 00:26:24,890
>> Hivyo katika muundo fulani,
sisi ni kuangalia bidhaa catalog.

621
00:26:24,890 --> 00:26:26,640
Nina aina mbalimbali za bidhaa.

622
00:26:26,640 --> 00:26:27,217
Nina vitabu.

623
00:26:27,217 --> 00:26:27,800
Nina albamu.

624
00:26:27,800 --> 00:26:30,090
Nina video.

625
00:26:30,090 --> 00:26:33,370
Uhusiano kati ya bidhaa
na yeyote mmoja wa haya vitabu, albamu,

626
00:26:33,370 --> 00:26:34,860
na video meza ni 1: 1.

627
00:26:34,860 --> 00:26:35,800
Sawa?

628
00:26:35,800 --> 00:26:38,860
Mimi nimepata bidhaa kitambulisho,
na kwamba ID sambamba

629
00:26:38,860 --> 00:26:41,080
kwa kitabu, albamu, au video.

630
00:26:41,080 --> 00:26:41,580
SAWA?

631
00:26:41,580 --> 00:26:44,350
Hiyo ni 1: 1 mahusiano
hela meza hizo.

632
00:26:44,350 --> 00:26:46,970
>> Sasa, books-- wote
kuwa ni mzizi mali.

633
00:26:46,970 --> 00:26:47,550
Hakuna shida.

634
00:26:47,550 --> 00:26:48,230
Hiyo ni kubwa.

635
00:26:48,230 --> 00:26:52,130
Uhusiano wa moja kwa moja, mimi kupata yote
data nahitaji kuelezea kitabu hicho.

636
00:26:52,130 --> 00:26:54,770
Albamu Albums-- na nyimbo.

637
00:26:54,770 --> 00:26:56,470
Hii ni nini sisi kuwaita moja kwa watu wengi.

638
00:26:56,470 --> 00:26:58,905
Kila albamu ya nyimbo inaweza kuwa mingi.

639
00:26:58,905 --> 00:27:00,780
Hivyo kwa kila wimbo kwenye
albamu, mimi naweza kuwa

640
00:27:00,780 --> 00:27:02,570
rekodi nyingine katika hii meza mtoto.

641
00:27:02,570 --> 00:27:04,680
Hivyo mimi kujenga rekodi moja
katika albamu yangu ya meza.

642
00:27:04,680 --> 00:27:06,700
Mimi kujenga rekodi nyingi
katika nyimbo meza.

643
00:27:06,700 --> 00:27:08,850
Uhusiano wa moja kwa wengi.

644
00:27:08,850 --> 00:27:11,220
>> Uhusiano huu ni nini
tunatoa wito wengi kwa wengi.

645
00:27:11,220 --> 00:27:11,750
SAWA?

646
00:27:11,750 --> 00:27:17,000
Unaweza kuona kwamba watendaji inaweza kuwa
katika sinema nyingi, video wengi.

647
00:27:17,000 --> 00:27:21,450
Hivyo kile sisi kufanya ni sisi kuweka ramani hii
meza kati ya hizo, ambayo ni tu

648
00:27:21,450 --> 00:27:24,040
ramani muigizaji ID kwa video ID.

649
00:27:24,040 --> 00:27:28,464
Sasa naweza kujenga swala the anaungana
video kupitia muigizaji video kwa watendaji,

650
00:27:28,464 --> 00:27:31,130
na inanipa nzuri orodha ya
sinema zote na watendaji wote

651
00:27:31,130 --> 00:27:32,420
waliokuwa katika kwamba movie.

652
00:27:32,420 --> 00:27:33,290
>> SAWA.

653
00:27:33,290 --> 00:27:33,880
Hivyo hapa sisi kwenda.

654
00:27:33,880 --> 00:27:38,040
Moja kwa moja ni wa ngazi za juu
Uhusiano; moja kwa watu wengi,

655
00:27:38,040 --> 00:27:40,240
albamu na nyimbo; wengi kwa wengi.

656
00:27:40,240 --> 00:27:44,990
Hayo ni tatu wa ngazi za juu
mahusiano katika orodha yoyote.

657
00:27:44,990 --> 00:27:48,050
Kama unajua jinsi wale
mahusiano kazi pamoja,

658
00:27:48,050 --> 00:27:51,490
basi, unajua mengi
kuhusu orodha tayari.

659
00:27:51,490 --> 00:27:55,660
Hivyo NoSQL kazi tofauti kidogo.

660
00:27:55,660 --> 00:27:58,930
Hebu fikiria kuhusu kwa nini pili
inaonekana kama kwenda kupata bidhaa yangu yote.

661
00:27:58,930 --> 00:28:01,096
>> Katika kuhifadhi kimahusiano, mimi
wanataka kupata bidhaa yangu yote

662
00:28:01,096 --> 00:28:02,970
juu ya orodha ya bidhaa wangu wote.

663
00:28:02,970 --> 00:28:04,910
Kwamba mengi ya maswali.

664
00:28:04,910 --> 00:28:07,030
I got swala kwa vitabu yangu yote.

665
00:28:07,030 --> 00:28:08,470
I got swala kutoka albamu yangu.

666
00:28:08,470 --> 00:28:09,970
Na mimi got swala kwa ajili ya video yangu yote.

667
00:28:09,970 --> 00:28:11,719
Na mimi got kuiweka
wote kwa pamoja katika orodha

668
00:28:11,719 --> 00:28:15,250
na kutumika nyuma hadi
maombi hiyo kuomba hiyo.

669
00:28:15,250 --> 00:28:18,000
>> Kupata vitabu yangu, mimi kujiunga
Bidhaa na Vitabu.

670
00:28:18,000 --> 00:28:21,680
Kupata albamu yangu, I got kujiunga
Bidhaa, Albamu, na Tracks.

671
00:28:21,680 --> 00:28:25,330
Na kupata video yangu, nina
kujiunga Bidhaa kwa Video,

672
00:28:25,330 --> 00:28:28,890
kujiunga kupitia Muigizaji Video,
na kuleta katika Watendaji.

673
00:28:28,890 --> 00:28:31,020
Hivyo hiyo ni maswali matatu.

674
00:28:31,020 --> 00:28:34,560
Maswali magumu sana kwa
kukusanyika moja matokeo ya kuweka.

675
00:28:34,560 --> 00:28:36,540
>> Hiyo ni chini zaidi kuliko kawaida.

676
00:28:36,540 --> 00:28:39,200
Hii ni kwa nini wakati sisi majadiliano
kuhusu muundo data kwamba

677
00:28:39,200 --> 00:28:42,900
kujengwa kwa kuwa agnostic kwa upatikanaji
pattern-- vizuri kwamba ni kubwa.

678
00:28:42,900 --> 00:28:45,730
Na unaweza kuona hii ni kweli
nzuri jinsi tumekuwa kupangwa data.

679
00:28:45,730 --> 00:28:46,550
Na unajua nini?

680
00:28:46,550 --> 00:28:49,750
Mimi tu kuwa na rekodi moja kwa muigizaji.

681
00:28:49,750 --> 00:28:50,440
>> Hiyo ni poa.

682
00:28:50,440 --> 00:28:53,750
Nimekuwa deduplicated watendaji wangu wote,
na mimi iimarishwe vyama yangu

683
00:28:53,750 --> 00:28:55,200
katika hii meza ramani.

684
00:28:55,200 --> 00:29:00,620
Hata hivyo, kupata data
nje inakuwa ghali.

685
00:29:00,620 --> 00:29:04,500
Mimi kutuma CPU duniani mfumo
kujiunga na miundo haya data pamoja

686
00:29:04,500 --> 00:29:05,950
kuwa na uwezo wa kuvuta data kwamba nyuma.

687
00:29:05,950 --> 00:29:07,310
>> Hivyo ni jinsi gani mimi kupata kote kwamba?

688
00:29:07,310 --> 00:29:11,200
Katika NoSQL ni kuhusu
kuwakusanya, si kuhalalisha.

689
00:29:11,200 --> 00:29:13,534
Hivyo tunataka kusema tunataka
kusaidia upatikanaji mfano.

690
00:29:13,534 --> 00:29:15,283
Kama upatikanaji mfano
kwa maombi,

691
00:29:15,283 --> 00:29:16,770
Mimi haja ya kupata bidhaa yangu yote.

692
00:29:16,770 --> 00:29:19,027
Hebu kuweka bidhaa zote katika meza moja.

693
00:29:19,027 --> 00:29:22,110
Kama mimi kuweka bidhaa zote katika meza moja,
Siwezi kuchagua tu mazao yote

694
00:29:22,110 --> 00:29:23,850
kutoka meza hiyo na mimi kupata yote.

695
00:29:23,850 --> 00:29:25,240
Vizuri jinsi gani mimi kufanya hivyo?

696
00:29:25,240 --> 00:29:28,124
Vizuri katika NoSQL hakuna
muundo wa meza.

697
00:29:28,124 --> 00:29:30,540
Tutaweza kuzungumza kidogo kuhusu
jinsi hii matendo katika Dynamo DB.

698
00:29:30,540 --> 00:29:33,570
Lakini huna huo
sifa na tabia ile ile

699
00:29:33,570 --> 00:29:37,751
katika kila safu moja, katika kila moja
bidhaa, kama wewe kufanya katika meza SQL.

700
00:29:37,751 --> 00:29:39,750
Na nini hii inaruhusu mimi
kufanya ni mambo mengi

701
00:29:39,750 --> 00:29:41,124
na kunipa mengi ya kubadilika.

702
00:29:41,124 --> 00:29:45,360
Katika kesi hii, mimi
kuwa na bidhaa nyaraka zangu.

703
00:29:45,360 --> 00:29:49,090
Na katika hili hasa
mfano, kila kitu

704
00:29:49,090 --> 00:29:51,930
ni hati katika Bidhaa meza.

705
00:29:51,930 --> 00:29:56,510
Na bidhaa kwa ajili ya kitabu nguvu
kuwa na aina ID kwamba unasema kitabu.

706
00:29:56,510 --> 00:29:59,180
Na maombi
ingekuwa kubadili juu kwamba ID.

707
00:29:59,180 --> 00:30:02,570
>> Wakati maombi tier, mimi nina kwenda
kusema oh, nini rekodi ya aina hii?

708
00:30:02,570 --> 00:30:04,100
Oh, ni rekodi ya kitabu.

709
00:30:04,100 --> 00:30:05,990
Rekodi kitabu na mali hizi.

710
00:30:05,990 --> 00:30:08,100
Napenda kuunda kitabu kitu.

711
00:30:08,100 --> 00:30:11,289
Hivyo nina kwenda kujaza
kitabu kitu kwa bidhaa hii.

712
00:30:11,289 --> 00:30:13,080
Bidhaa ijayo anakuja na
anasema, nini bidhaa hii?

713
00:30:13,080 --> 00:30:14,560
Naam bidhaa hii ni albamu.

714
00:30:14,560 --> 00:30:17,340
Oh, I got mbalimbali nzima
usindikaji wa mara kwa mara kwa kuwa,

715
00:30:17,340 --> 00:30:18,487
kwa sababu ni albamu.

716
00:30:18,487 --> 00:30:19,320
Unaweza kuona nini namaanisha?

717
00:30:19,320 --> 00:30:21,950
>> Hivyo maombi tier-- mimi
tu kuchagua rekodi zote hizi.

718
00:30:21,950 --> 00:30:23,200
Wote kuanza kuja katika.

719
00:30:23,200 --> 00:30:24,680
Wao wanaweza kuwa aina zote mbalimbali.

720
00:30:24,680 --> 00:30:27,590
Na ni mantiki ya maombi ya
kwamba swichi katika wale aina

721
00:30:27,590 --> 00:30:29,530
na anaamua jinsi mchakato yao.

722
00:30:29,530 --> 00:30:33,640
>> Tena, hivyo sisi ni optimizing
schema kwa ajili ya kupata mfano.

723
00:30:33,640 --> 00:30:36,390
Sisi ni kufanya hivyo kwa
kuanguka meza hizo.

724
00:30:36,390 --> 00:30:39,670
Sisi ni kimsingi kuchukua
miundo haya kurejesha,

725
00:30:39,670 --> 00:30:42,000
na sisi ni kujenga
kihierarkia miundo.

726
00:30:42,000 --> 00:30:45,130
Ndani ya kila mmoja kumbukumbu hizi
Mimi nina kwenda kuona mali safu.

727
00:30:45,130 --> 00:30:49,400
>> Ndani ya waraka huu kwa Albamu,
Mimi nina kuona arrays ya nyimbo.

728
00:30:49,400 --> 00:30:53,900
Nyimbo hizo sasa become-- ni
kimsingi hii meza mtoto kwamba

729
00:30:53,900 --> 00:30:56,520
lipo hapa hapa katika muundo huu.

730
00:30:56,520 --> 00:30:57,975
Hivyo unaweza kufanya hivyo katika DynamoDB.

731
00:30:57,975 --> 00:30:59,810
Unaweza kufanya hivyo katika MongoDB.

732
00:30:59,810 --> 00:31:01,437
Unaweza kufanya hivyo katika database yoyote NoSQL.

733
00:31:01,437 --> 00:31:03,520
Kujenga aina hii ya
kihierarkia miundo data

734
00:31:03,520 --> 00:31:07,120
kwamba kuruhusu retrieve data
haraka sana kwa sababu sasa mimi

735
00:31:07,120 --> 00:31:08,537
Si lazima kuendana.

736
00:31:08,537 --> 00:31:11,620
Wakati mimi kuingiza mstari katika Tracks
meza, au mstari katika Albamu meza,

737
00:31:11,620 --> 00:31:13,110
Nina kuendana na kwamba schema.

738
00:31:13,110 --> 00:31:18,060
Mimi kuwa na sifa au
mali ambayo inaelezwa kwenye meza hiyo.

739
00:31:18,060 --> 00:31:20,480
Kila mmoja wao,
wakati mimi kuingiza mstari huo.

740
00:31:20,480 --> 00:31:21,910
Si kwamba kesi katika NoSQL.

741
00:31:21,910 --> 00:31:24,440
>> Siwezi kuwa tofauti kabisa
mali katika kila hati

742
00:31:24,440 --> 00:31:26,100
kwamba mimi kuingiza ndani ya ukusanyaji.

743
00:31:26,100 --> 00:31:30,480
Hivyo sana nguvu utaratibu.

744
00:31:30,480 --> 00:31:32,852
Na kwa kweli ni jinsi gani
kuongeza mfumo.

745
00:31:32,852 --> 00:31:35,310
Kwa sababu sasa kwamba swala, badala
ya kujiunga na mbao hizo zote

746
00:31:35,310 --> 00:31:39,160
na utekelezaji maswali kadhaa nusu
kuvuta nyuma data nahitaji,

747
00:31:39,160 --> 00:31:40,890
Mimi utekelezaji swala moja.

748
00:31:40,890 --> 00:31:43,010
Na mimi nina iterating
hela matokeo kuweka.

749
00:31:43,010 --> 00:31:46,512
inakupa wazo
nguvu za NoSQL.

750
00:31:46,512 --> 00:31:49,470
Mimi nina kwenda aina ya kwenda sideways hapa
na kuzungumza kidogo kuhusu hili.

751
00:31:49,470 --> 00:31:53,240
Hii ni aina zaidi ya
masoko au technology--

752
00:31:53,240 --> 00:31:55,660
masoko ya teknolojia
aina ya majadiliano.

753
00:31:55,660 --> 00:31:58,672
Lakini ni muhimu kuelewa
kwa sababu kama sisi kuangalia juu

754
00:31:58,672 --> 00:32:00,380
hapa katika chati hii,
nini sisi ni kuangalia

755
00:32:00,380 --> 00:32:04,030
ni kile tunachokiita
teknolojia Hype Curve.

756
00:32:04,030 --> 00:32:06,121
Na nini maana ya hii ni
mambo mapya linachukua nafasi.

757
00:32:06,121 --> 00:32:07,120
Watu wanadhani ni kubwa.

758
00:32:07,120 --> 00:32:09,200
Nimekuwa kutatuliwa matatizo yangu yote.

759
00:32:09,200 --> 00:32:11,630
>> Hii inaweza kuwa mwisho
wote, kuwa wote kwa kila kitu.

760
00:32:11,630 --> 00:32:12,790
Nao kuanza kutumia.

761
00:32:12,790 --> 00:32:14,720
Na wanasema, mambo haya haifanyi kazi.

762
00:32:14,720 --> 00:32:17,600
Hii si haki.

763
00:32:17,600 --> 00:32:19,105
Mambo ya zamani ilikuwa bora zaidi.

764
00:32:19,105 --> 00:32:21,230
Nao kurudi nyuma na kufanya
mambo kwa njia hao.

765
00:32:21,230 --> 00:32:22,730
Na kisha hatimaye
wao kwenda, unajua nini?

766
00:32:22,730 --> 00:32:24,040
Mambo haya si mbaya.

767
00:32:24,040 --> 00:32:26,192
Oh, hiyo ni jinsi kazi.

768
00:32:26,192 --> 00:32:28,900
Na mara moja wao kufikiri ni jinsi gani
matendo, wao kuanza kupata bora.

769
00:32:28,900 --> 00:32:32,050
>> Na jambo funny kuhusu hilo
ni, aina ya yanaendana na kile

770
00:32:32,050 --> 00:32:34,300
tunatoa wito Teknolojia Adoption Curve.

771
00:32:34,300 --> 00:32:36,910
Hivyo kile kinachotokea ni tuna
aina fulani ya teknolojia trigger.

772
00:32:36,910 --> 00:32:39,100
Katika kesi ya database,
ni data shinikizo.

773
00:32:39,100 --> 00:32:42,200
Kuongelea pointi juu ya maji
wa takwimu shinikizo katika wakati.

774
00:32:42,200 --> 00:32:46,310
Wakati kwamba shinikizo data hits fulani
hatua, hiyo ni teknolojia trigger.

775
00:32:46,310 --> 00:32:47,830
>> Ni kupata gharama kubwa mno.

776
00:32:47,830 --> 00:32:49,790
Inachukua muda mrefu sana kwa mchakato wa data.

777
00:32:49,790 --> 00:32:50,890
Tunahitaji kitu kizuri zaidi.

778
00:32:50,890 --> 00:32:52,890
Kupata wabunifu
huko nje mbio kuzunguka,

779
00:32:52,890 --> 00:32:55,050
kujaribu kujua nini ufumbuzi.

780
00:32:55,050 --> 00:32:56,050
Nini wazo jipya?

781
00:32:56,050 --> 00:32:58,170
>> Nini ijayo bora
njia ya kufanya jambo hili?

782
00:32:58,170 --> 00:32:59,530
Nao kuja na kitu.

783
00:32:59,530 --> 00:33:03,140
Na watu wenye maumivu ya kweli,
guys katika makali kutokwa na damu,

784
00:33:03,140 --> 00:33:06,390
wao itabidi kuruka yote juu yake,
kwa sababu wanahitaji jibu.

785
00:33:06,390 --> 00:33:09,690
Sasa nini inevitably happens-- na
ni kinatokea sasa hivi katika NoSQL.

786
00:33:09,690 --> 00:33:11,090
Mimi naona ni wakati wote.

787
00:33:11,090 --> 00:33:13,610
>> Nini kinatokea ni inevitably
watu kuanza kutumia zana mpya

788
00:33:13,610 --> 00:33:15,490
njia ile ile waliyo na umri wa chombo.

789
00:33:15,490 --> 00:33:17,854
Nao kujua ni
haifanyi kazi vizuri.

790
00:33:17,854 --> 00:33:20,020
Siwezi kukumbuka mimi ni nani
kuzungumza na mapema leo.

791
00:33:20,020 --> 00:33:22,080
Lakini ni kama, wakati
jackhammer ilizuliwa,

792
00:33:22,080 --> 00:33:24,621
watu hawakuwa kuuzungusha juu ya
vichwa vyao Smash halisi.

793
00:33:24,621 --> 00:33:27,360

794
00:33:27,360 --> 00:33:30,610
>> Lakini hiyo ni nini
kinachotokea na NoSQL leo.

795
00:33:30,610 --> 00:33:33,900
Kama kutembea katika maduka zaidi,
wao ni kujaribu kuwa maduka NoSQL.

796
00:33:33,900 --> 00:33:36,510
Nini re kufanya ni
wao ni kutumia NoSQL,

797
00:33:36,510 --> 00:33:39,900
na wao ni wa kupakia ni
kamili ya kimahusiano schema.

798
00:33:39,900 --> 00:33:41,630
Kwa sababu hiyo ni jinsi
wao kubuni database.

799
00:33:41,630 --> 00:33:44,046
Na wao ni wanashangaa, kwa nini ni
kuwa si kufanya vizuri sana?

800
00:33:44,046 --> 00:33:45,230
Boy, jambo hili stinks.

801
00:33:45,230 --> 00:33:49,900
Mimi nilikuwa na kudumisha wote yangu
anaungana in-- ni kama, hapana, hapana.

802
00:33:49,900 --> 00:33:50,800
Kudumisha anaungana?

803
00:33:50,800 --> 00:33:52,430
Mbona kujiunga na data?

804
00:33:52,430 --> 00:33:54,350
Huwezi kujiunga data katika NoSQL.

805
00:33:54,350 --> 00:33:55,850
Wewe jumla ya mabao hayo.

806
00:33:55,850 --> 00:34:00,690
>> Hivyo kama unataka kuepuka hili, kujifunza
jinsi chombo kazi kabla ya kweli

807
00:34:00,690 --> 00:34:02,010
kuanza kutumia.

808
00:34:02,010 --> 00:34:04,860
Je, si kujaribu na matumizi ya zana mpya
njia hiyo hiyo kutumika zana za zamani.

809
00:34:04,860 --> 00:34:06,500
Wewe ni kwenda kuwa na uzoefu mbaya.

810
00:34:06,500 --> 00:34:08,848
Na kila wakati
kwamba ni nini hii ni kuhusu.

811
00:34:08,848 --> 00:34:11,389
Wakati sisi kuanza kuja juu hapa,
ni kwa sababu watu figured nje

812
00:34:11,389 --> 00:34:13,449
jinsi ya kutumia zana.

813
00:34:13,449 --> 00:34:16,250
>> Wao kitu kimoja lini
databaser kimahusiano walikuwa zuliwa,

814
00:34:16,250 --> 00:34:17,969
na walikuwa kuchukua nafasi ya mifumo ya faili.

815
00:34:17,969 --> 00:34:20,420
Walijaribu kujenga mifumo ya faili
na database kimahusiano

816
00:34:20,420 --> 00:34:22,159
kwa sababu hiyo ndiyo watu kueleweka.

817
00:34:22,159 --> 00:34:23,049
Haikuwa kazi.

818
00:34:23,049 --> 00:34:26,090
Hivyo kuelewa mbinu bora
ya teknolojia wewe ni kufanya kazi kwa

819
00:34:26,090 --> 00:34:26,730
ni kubwa.

820
00:34:26,730 --> 00:34:29,870
Muhimu sana.

821
00:34:29,870 --> 00:34:32,440
>> Hivyo sisi ni kwenda kupata katika DynamoDB.

822
00:34:32,440 --> 00:34:36,480
DynamoDB ni AWS ya
kikamilifu kusimamiwa NoSQL jukwaa.

823
00:34:36,480 --> 00:34:37,719
Je kikamilifu kusimamiwa maana gani?

824
00:34:37,719 --> 00:34:40,010
Ina maana wewe huna haja ya
kweli wasiwasi kuhusu lolote.

825
00:34:40,010 --> 00:34:42,060
>> Wewe kuja katika, kumweleza
sisi, mimi haja ya meza.

826
00:34:42,060 --> 00:34:43,409
Inahitaji uwezo kiasi hiki.

827
00:34:43,409 --> 00:34:47,300
Kugonga kifungo, na sisi utoaji
miundombinu yote nyuma ya eneo.

828
00:34:47,300 --> 00:34:48,310
Sasa kwa kuwa ni kubwa sana.

829
00:34:48,310 --> 00:34:51,310
>> Kwa sababu wakati majadiliano
kuhusu kuongeza database,

830
00:34:51,310 --> 00:34:53,917
NoSQL data nguzo katika
wadogo, uendeshaji petabytes,

831
00:34:53,917 --> 00:34:55,750
mbio mamilioni ya
shughuli kwa pili,

832
00:34:55,750 --> 00:34:58,180
mambo haya si makundi madogo.

833
00:34:58,180 --> 00:35:00,830
Tunazungumzia maelfu ya matukio.

834
00:35:00,830 --> 00:35:04,480
Kusimamia maelfu ya matukio,
hata matukio virtual,

835
00:35:04,480 --> 00:35:06,350
ni maumivu ya kweli katika kitako.

836
00:35:06,350 --> 00:35:09,110
I mean, kufikiri juu ya kila an wakati
mfumo wa uendeshaji kiraka hutoka nje

837
00:35:09,110 --> 00:35:11,552
au toleo jipya la orodha.

838
00:35:11,552 --> 00:35:13,260
Hiyo ina maana gani
na wewe operationally?

839
00:35:13,260 --> 00:35:16,330
Hiyo ina maana wewe got 1,200
watumishi ambayo yanahitaji updated.

840
00:35:16,330 --> 00:35:18,960
Sasa hata kwa automatisering,
ambayo inaweza kuchukua muda mrefu.

841
00:35:18,960 --> 00:35:21,480
Hiyo inaweza kusababisha mengi ya
uendeshaji kuumwa kichwa,

842
00:35:21,480 --> 00:35:23,090
kwa sababu nipate kuwa huduma chini.

843
00:35:23,090 --> 00:35:26,070
>> Kama mimi update database haya, mimi
anaweza kufanya bluu deployments kijani

844
00:35:26,070 --> 00:35:29,420
ambapo mimi kupeleka na kuboresha nusu yangu
nodes, na kisha kuboresha nusu nyingine.

845
00:35:29,420 --> 00:35:30,490
Kuchukua wale chini.

846
00:35:30,490 --> 00:35:33,410
Hivyo kusimamia miundombinu
wadogo ni mkubwa sana chungu.

847
00:35:33,410 --> 00:35:36,210
Na AWS kuchukua kwamba maumivu nje ya hiyo.

848
00:35:36,210 --> 00:35:39,210
Na NoSQL databaser Unaweza
kuwa extraordinarily chungu

849
00:35:39,210 --> 00:35:41,780
kwa sababu ya njia ya wao wadogo.

850
00:35:41,780 --> 00:35:42,926
>> Kuongeza usawa.

851
00:35:42,926 --> 00:35:45,550
Kama unataka kupata NoSQL kubwa
Mbegu, kununua nodes zaidi.

852
00:35:45,550 --> 00:35:48,660
Kila nodi kununua ni
mwingine uendeshaji maumivu ya kichwa.

853
00:35:48,660 --> 00:35:50,830
Hivyo basi mtu mwingine kufanya hivyo kwa ajili yenu.

854
00:35:50,830 --> 00:35:52,000
AWS anaweza kufanya hivyo.

855
00:35:52,000 --> 00:35:54,587
>> Tunaunga mkono maadili hati muhimu.

856
00:35:54,587 --> 00:35:56,670
Sasa sisi hakwenda sana
ndani ya juu ya chati wengine.

857
00:35:56,670 --> 00:35:58,750
Kuna mengi ya tofauti
ladha ya NoSQL.

858
00:35:58,750 --> 00:36:02,670
Wao ni kila aina ya kupata
munged pamoja katika hatua hii.

859
00:36:02,670 --> 00:36:06,260
Unaweza kuangalia DynamoDB na kusema ndiyo,
tuko wote wawili hati na ufunguo thamani

860
00:36:06,260 --> 00:36:08,412
kuhifadhi hatua hii.

861
00:36:08,412 --> 00:36:10,620
Na unaweza kusema makala
ya moja juu ya nyingine.

862
00:36:10,620 --> 00:36:13,950
Kwangu mimi, mengi ya hii ni kweli sita
ya moja nusu kadhaa ya wengine.

863
00:36:13,950 --> 00:36:18,710
Kila moja ya teknolojia hizi ni
teknolojia faini na ufumbuzi faini.

864
00:36:18,710 --> 00:36:23,390
Napenda kusema MongoDB ni bora au
mbaya zaidi kuliko kitanda, kisha Cassandra,

865
00:36:23,390 --> 00:36:25,994
kisha Dynamo, au kinyume chake.

866
00:36:25,994 --> 00:36:27,285
I mean, hizi ni chaguzi tu.

867
00:36:27,285 --> 00:36:29,850

868
00:36:29,850 --> 00:36:32,700
>> Ni kwa haraka na ni
thabiti wakati wowote wadogo.

869
00:36:32,700 --> 00:36:36,210
Hivyo hii ni moja ya kubwa
mafao kupata na AWS.

870
00:36:36,210 --> 00:36:40,850
Kwa DynamoDB ni uwezo
kupata moja chini tarakimu

871
00:36:40,850 --> 00:36:44,040
millisecond utulivu wakati wowote wadogo.

872
00:36:44,040 --> 00:36:45,720
Hiyo ilikuwa ni mpango lengo la mfumo.

873
00:36:45,720 --> 00:36:49,130
Na sisi wateja kwamba wanafanya
mamilioni ya mashirikiano kwa pili.

874
00:36:49,130 --> 00:36:52,670
>> Sasa nitakwenda kupitia baadhi ya wale
kutumia kesi katika dakika chache hapa.

875
00:36:52,670 --> 00:36:55,660
Integrated upatikanaji control--
tuna kile tunachokiita

876
00:36:55,660 --> 00:36:57,920
Utambulisho Kupata Management, au IAM.

877
00:36:57,920 --> 00:37:01,980
Ni inaruhushu kila mfumo,
kila huduma ambayo inatoa AWS.

878
00:37:01,980 --> 00:37:03,630
DynamoDB ni hakuna ubaguzi.

879
00:37:03,630 --> 00:37:06,020
Unaweza kudhibiti upatikanaji
meza DynamoDB.

880
00:37:06,020 --> 00:37:09,960
Hela zote AWS yako akaunti na
kufafanua upatikanaji majukumu na ruhusa

881
00:37:09,960 --> 00:37:12,140
katika miundombinu IAM.

882
00:37:12,140 --> 00:37:16,630
>> Na ni muhimu na muhimu sehemu katika
kile tunachokiita Tukio Inaendeshwa Programu.

883
00:37:16,630 --> 00:37:19,056
Sasa hii ni dhana mpya.

884
00:37:19,056 --> 00:37:22,080
>> Watazamaji: Je, ni kiwango yako ya kweli
chanya dhidi negatives uongo

885
00:37:22,080 --> 00:37:24,052
juu ya upatikanaji mfumo wa kudhibiti yako?

886
00:37:24,052 --> 00:37:26,260
RICK Houlihan: chanya Kweli
dhidi ya negatives uongo?

887
00:37:26,260 --> 00:37:28,785
Watazamaji: Kurudi nini
unapaswa kuwa kurudi?

888
00:37:28,785 --> 00:37:33,720
Kinyume na mara moja kwa wakati ni
haina kurudi wakati ni lazima kuhalalisha?

889
00:37:33,720 --> 00:37:36,260

890
00:37:36,260 --> 00:37:38,050
>> RICK Houlihan: sikuweza kukuambia kwamba.

891
00:37:38,050 --> 00:37:40,140
Kama kuna mapungufu yoyote
yo juu ya kwamba,

892
00:37:40,140 --> 00:37:42,726
Sina mtu kuuliza
kwamba swali fulani.

893
00:37:42,726 --> 00:37:43,850
Lakini hiyo ni swali zuri.

894
00:37:43,850 --> 00:37:45,905
Napenda kuwa na hamu ya kujua
kwamba mimi mwenyewe, kwa kweli.

895
00:37:45,905 --> 00:37:48,810

896
00:37:48,810 --> 00:37:51,320
>> Na hivyo basi tena, dhana mpya
ni tukio inaendeshwa programu.

897
00:37:51,320 --> 00:37:55,160
Hili ni wazo kwamba unaweza
kupeleka maombi tata kwamba

898
00:37:55,160 --> 00:37:59,720
wanaweza kufanya kazi sana, juu sana wadogo
bila miundombinu yoyote ile.

899
00:37:59,720 --> 00:38:02,120
Bila fasta
miundombinu wowote.

900
00:38:02,120 --> 00:38:04,720
Na tutaweza kuzungumza kidogo
kuhusu nini maana sisi kama

901
00:38:04,720 --> 00:38:06,550
kupata kwenye michache ijayo chati.

902
00:38:06,550 --> 00:38:08,716
>> Jambo la kwanza tutaweza kufanya
ni tutaweza majadiliano juu ya meza.

903
00:38:08,716 --> 00:38:10,857
Aina ya Dynamo API data.

904
00:38:10,857 --> 00:38:13,190
Na jambo la kwanza utasikia
taarifa wakati ukiangalia hiyo,

905
00:38:13,190 --> 00:38:17,930
kama wewe ni ukoo na database yoyote,
databaser na kweli mbili aina ya APIs

906
00:38:17,930 --> 00:38:18,430
Ningependa simu yake.

907
00:38:18,430 --> 00:38:21,570
Au makundi mawili ya API.

908
00:38:21,570 --> 00:38:23,840
Mmoja wa wale itakuwa
utawala API.

909
00:38:23,840 --> 00:38:26,710
>> Mambo ya utunzaji wa
Kazi za database.

910
00:38:26,710 --> 00:38:31,340
Configuring injini kuhifadhi,
kuanzisha na kuongeza meza.

911
00:38:31,340 --> 00:38:35,180
kujenga database
catalogs na matukio.

912
00:38:35,180 --> 00:38:40,450
Hizi things-- katika DynamoDB, wewe
kuwa mfupi sana, orodha fupi.

913
00:38:40,450 --> 00:38:43,120
>> Hivyo katika database nyingine,
unaweza kuona kadhaa

914
00:38:43,120 --> 00:38:45,680
ya amri, ya utawala
amri, kwa ajili ya Configuring

915
00:38:45,680 --> 00:38:47,290
chaguzi hizo za ziada.

916
00:38:47,290 --> 00:38:51,234
Katika DynamoDB huna haja wale kwa sababu
huna configure mfumo, sisi kufanya.

917
00:38:51,234 --> 00:38:54,150
Hivyo kitu pekee unahitaji kufanya ni
kuniambia nini ukubwa meza nahitaji.

918
00:38:54,150 --> 00:38:55,660
Ili kupata sana
seti mdogo wa amri.

919
00:38:55,660 --> 00:38:58,618
>> Kupata Kujenga meza Mwisho, Meza,
Kufuta Meza, na Elezea Meza.

920
00:38:58,618 --> 00:39:01,150
Hayo ni mambo tu
unahitaji kwa DynamoDB.

921
00:39:01,150 --> 00:39:03,294
Huna haja ya kuhifadhi
injini Configuration.

922
00:39:03,294 --> 00:39:04,960
Sina haja ya kuwa na wasiwasi kuhusu replication.

923
00:39:04,960 --> 00:39:06,490
Sina haja ya kuwa na wasiwasi kuhusu sharding.

924
00:39:06,490 --> 00:39:07,800
>> Sina haja ya kuwa na wasiwasi
kuhusu yoyote ya mambo haya.

925
00:39:07,800 --> 00:39:08,740
Sisi kufanya yote kwa ajili yenu.

926
00:39:08,740 --> 00:39:11,867
Hivyo hiyo ni kiasi kikubwa cha uendeshaji
kwamba tu lile mbali sahani yako.

927
00:39:11,867 --> 00:39:13,200
Basi tuna waendeshaji CRUD.

928
00:39:13,200 --> 00:39:17,740
CRUD ni kitu gani sisi
piga katika orodha hiyo ni

929
00:39:17,740 --> 00:39:19,860
Kujenga, Mwisho, Futa waendeshaji.

930
00:39:19,860 --> 00:39:24,180
Hizi ni kawaida yako
shughuli database.

931
00:39:24,180 --> 00:39:31,299
Mambo kama kuweka bidhaa, kupata bidhaa, update
vitu, kufuta vitu, kundi swala, Scan.

932
00:39:31,299 --> 00:39:32,840
Kama unataka Scan meza nzima.

933
00:39:32,840 --> 00:39:34,220
Kuvuta kila kitu mbali ya meza.

934
00:39:34,220 --> 00:39:37,130
Moja ya mambo mazuri kuhusu DynamoDB
ni inaruhusu sambamba skanning.

935
00:39:37,130 --> 00:39:40,602
Hivyo unaweza kweli napenda kujua ni wangapi
nyuzi unataka kukimbia juu ya kwamba Scan.

936
00:39:40,602 --> 00:39:41,810
Na tunaweza kukimbia wale nyuzi.

937
00:39:41,810 --> 00:39:43,985
Tunaweza spin kwamba Scan up
hela nyuzi nyingi

938
00:39:43,985 --> 00:39:49,060
hivyo unaweza Scan meza nzima
nafasi sana, haraka sana katika DynamoDB.

939
00:39:49,060 --> 00:39:51,490
>> API mengine tuliyonayo ni
kile tunachokiita yetu mito API.

940
00:39:51,490 --> 00:39:52,940
Sisi siyo kwenda kuzungumza pia
mengi kuhusu hii hivi sasa.

941
00:39:52,940 --> 00:39:55,189
Mimi nimepata baadhi ya maudhui baadaye
juu ya staha katika jambo hili.

942
00:39:55,189 --> 00:39:59,910
Lakini mito ni kweli running--
kufikiria kama muda kuamuru

943
00:39:59,910 --> 00:40:01,274
na mabadiliko kuhesabu gogo.

944
00:40:01,274 --> 00:40:03,940
Kila kitu ambacho kinatokea kwenye
meza inaonyesha juu ya mkondo.

945
00:40:03,940 --> 00:40:05,940
>> Kila kuwaandikia meza
inaonyesha juu ya mkondo.

946
00:40:05,940 --> 00:40:08,370
Unaweza kusoma mkondo huo, na
unaweza kufanya mambo kwa hayo.

947
00:40:08,370 --> 00:40:10,150
Tutaweza majadiliano juu ya kile
aina ya mambo

948
00:40:10,150 --> 00:40:13,680
kufanya na mambo kama replication,
kujenga bahati sekondari.

949
00:40:13,680 --> 00:40:17,620
Kila aina ya kweli ya baridi
mambo unaweza kufanya na kwamba.

950
00:40:17,620 --> 00:40:19,150
>> Takwimu aina.

951
00:40:19,150 --> 00:40:23,320
Katika DynamoDB, sisi msaada wote muhimu
thamani na hati data aina.

952
00:40:23,320 --> 00:40:26,350
Upande wa kushoto wa screen
hapa, sisi tumepewa aina yetu ya msingi.

953
00:40:26,350 --> 00:40:27,230
Ufunguo thamani aina.

954
00:40:27,230 --> 00:40:30,040
Hizi ni masharti,
idadi, na binaries.

955
00:40:30,040 --> 00:40:31,640
>> Hivyo aina ya msingi tatu tu.

956
00:40:31,640 --> 00:40:33,700
Na kisha unaweza kuwa na seti ya wale.

957
00:40:33,700 --> 00:40:37,650
Moja ya mambo mazuri kuhusu NoSQL ni
unaweza vyenye arrays kama mali.

958
00:40:37,650 --> 00:40:42,050
Na kwa DynamoDB unaweza vyenye arrays
ya aina ya msingi kama mali mizizi.

959
00:40:42,050 --> 00:40:43,885
>> Na kisha kuna aina hati.

960
00:40:43,885 --> 00:40:45,510
Jinsi watu wengi ni ukoo na JSON?

961
00:40:45,510 --> 00:40:47,130
Nyie ukoo na JSON sana?

962
00:40:47,130 --> 00:40:49,380
Ni kimsingi JavaScript,
Kitu, nukuu.

963
00:40:49,380 --> 00:40:52,510
Ni utapata kimsingi
kufafanua muundo wa kihierarkia.

964
00:40:52,510 --> 00:40:58,107
>> Unaweza kuhifadhi JSON hati juu ya
DynamoDB kutumia vipengele kawaida

965
00:40:58,107 --> 00:41:00,940
au ujenzi wa vitalu ambayo inapatikana
katika lugha zaidi ya programu.

966
00:41:00,940 --> 00:41:03,602
Hivyo kama una Java, uko
kuangalia ramani na orodha.

967
00:41:03,602 --> 00:41:05,060
Siwezi kujenga vitu kwamba eneo ramani.

968
00:41:05,060 --> 00:41:08,030
Ramani kama maadili muhimu
kuhifadhiwa kama mali.

969
00:41:08,030 --> 00:41:10,890
Na inaweza kuwa na orodha ya
maadili ndani ya mali hizo.

970
00:41:10,890 --> 00:41:13,490
Unaweza kuhifadhi tata hii
muundo wa kihierarkia

971
00:41:13,490 --> 00:41:16,320
kama sifa moja
ya DynamoDB bidhaa.

972
00:41:16,320 --> 00:41:19,010

973
00:41:19,010 --> 00:41:24,460
>> Hivyo meza katika DynamoDB, kama wengi
NoSQL databaser, meza na vitu.

974
00:41:24,460 --> 00:41:26,469
Katika MongoDB wewe ungekuwa
piga nyaraka hizi.

975
00:41:26,469 --> 00:41:27,760
Na itakuwa kitanda msingi.

976
00:41:27,760 --> 00:41:28,900
Pia hati database.

977
00:41:28,900 --> 00:41:29,941
Wewe piga nyaraka hizi.

978
00:41:29,941 --> 00:41:32,930
Nyaraka au vitu na sifa.

979
00:41:32,930 --> 00:41:35,850
Sifa unaweza kuwepo au
haipo juu ya bidhaa.

980
00:41:35,850 --> 00:41:38,520
Katika DynamoDB, kuna
moja lazima sifa.

981
00:41:38,520 --> 00:41:43,880
Tu kama katika orodha kimahusiano,
una muhimu ya msingi juu ya meza.

982
00:41:43,880 --> 00:41:46,010
>> DynamoDB ina nini sisi kuwaita muhimu hash.

983
00:41:46,010 --> 00:41:48,280
Hash muhimu lazima kipekee.

984
00:41:48,280 --> 00:41:52,580
Hivyo wakati mimi kufafanua meza hash,
kimsingi nini mimi kusema

985
00:41:52,580 --> 00:41:54,110
ni kila kitu itakuwa na ufunguo hash.

986
00:41:54,110 --> 00:41:58,520
Na kila ufunguo hash lazima kipekee.

987
00:41:58,520 --> 00:42:01,200
>> Kila kitu inaelezwa
na kwamba kipekee hash muhimu.

988
00:42:01,200 --> 00:42:02,940
Na kuna inaweza tu kuwa moja.

989
00:42:02,940 --> 00:42:05,820
Hii ni sawa, lakini mara nyingi
nini watu haja

990
00:42:05,820 --> 00:42:08,170
ni wanachotaka ni hash hii
ufunguo wa kufanya kidogo zaidi

991
00:42:08,170 --> 00:42:11,010
kuliko tu kuwa kitambulisho kipekee.

992
00:42:11,010 --> 00:42:15,240
Mara nyingi tunataka kutumia ufunguo hash
kama ngazi ya juu kuwakusanya ndoo.

993
00:42:15,240 --> 00:42:19,160
Na njia ya sisi kufanya hivyo ni kwa
kuongeza kile tunachokiita ufunguo mbalimbali.

994
00:42:19,160 --> 00:42:22,460
>> Hivyo kama ni hash tu
meza, hii ni lazima kipekee.

995
00:42:22,460 --> 00:42:27,040
Kama ni hash na mbalimbali meza,
mchanganyiko wa hash na mbalimbali

996
00:42:27,040 --> 00:42:28,640
lazima kipekee.

997
00:42:28,640 --> 00:42:30,110
Hivyo kufikiri juu yake kwa njia hii.

998
00:42:30,110 --> 00:42:32,140
Kama mimi na jukwaa.

999
00:42:32,140 --> 00:42:39,010
Na aina ina mada, ina
posts, na ina majibu.

1000
00:42:39,010 --> 00:42:42,630
>> Hivyo nipate kuwa hash
muhimu, ambayo ni mada ID.

1001
00:42:42,630 --> 00:42:46,650
Na nipate kuwa muhimu mbalimbali,
ambayo ni mwitikio ID.

1002
00:42:46,650 --> 00:42:49,650
Kwa njia hiyo kama nataka kupata yote
majibu kwa mada fulani,

1003
00:42:49,650 --> 00:42:52,370
Naweza tu swala hash.

1004
00:42:52,370 --> 00:42:55,190
Siwezi kusema tu nipe zote
vitu kwamba kuwa hash hii.

1005
00:42:55,190 --> 00:43:01,910
Na mimi nina kwenda kupata kila swali
au baada ya mada fulani.

1006
00:43:01,910 --> 00:43:03,910
Hizi aggregations ngazi ya juu
ni muhimu sana.

1007
00:43:03,910 --> 00:43:07,370
Wao kusaidia upatikanaji msingi
mfano wa maombi.

1008
00:43:07,370 --> 00:43:09,420
Kwa ujumla, hii
ni nini tunataka kufanya.

1009
00:43:09,420 --> 00:43:11,780
Tunataka kuwa table--
kama wewe mzigo meza,

1010
00:43:11,780 --> 00:43:16,640
tunataka kuunda data
ndani ya meza kwa namna

1011
00:43:16,640 --> 00:43:20,140
kuwa maombi Unaweza sana
haraka kupata matokeo hayo.

1012
00:43:20,140 --> 00:43:24,510
Na mara nyingi njia ya kufanya hivyo ni
kudumisha aggregations hizi kama sisi

1013
00:43:24,510 --> 00:43:25,650
kuingiza data.

1014
00:43:25,650 --> 00:43:31,110
Kimsingi, sisi ni kueneza data
ndani ya ndoo mkali kama anakuja katika.

1015
00:43:31,110 --> 00:43:35,210
>> Funguo mbalimbali kuruhusu ME hash
funguo kuwa usawa.

1016
00:43:35,210 --> 00:43:39,490
Wakati mimi swala hash, mimi kusema
nipe hash kwamba ni sawa na hii.

1017
00:43:39,490 --> 00:43:41,950
Wakati mimi swala mbalimbali, mimi
anaweza kusema nipe mbalimbali

1018
00:43:41,950 --> 00:43:47,040
kwamba ni kwa kutumia aina yoyote ya
tajiri operator kwamba tunaunga mkono.

1019
00:43:47,040 --> 00:43:49,200
Nipe vitu vyote kwa hash.

1020
00:43:49,200 --> 00:43:52,520
Je, ni sawa, kubwa kuliko,
chini ya, je, ni kuanzia,

1021
00:43:52,520 --> 00:43:54,145
je, ni kuwepo kati ya maadili haya mawili?

1022
00:43:54,145 --> 00:43:56,811
Hivyo aina hii ya maswali mbalimbali
kwamba sisi ni daima nia ya.

1023
00:43:56,811 --> 00:43:59,650
Sasa jambo moja kuhusu data, wakati
ukiangalia kupata data, wakati

1024
00:43:59,650 --> 00:44:02,360
wewe kupata data, ni
Daima kuhusu kuwakusanya.

1025
00:44:02,360 --> 00:44:05,770
Ni siku zote kuhusu rekodi
kuwa ni kuhusiana na hii.

1026
00:44:05,770 --> 00:44:10,390
Nipe kila kitu hapa that's-- zote
shughuli katika kadi hii mikopo

1027
00:44:10,390 --> 00:44:12,500
kwa mwezi uliopita.

1028
00:44:12,500 --> 00:44:13,960
Hiyo ni kuwakusanya.

1029
00:44:13,960 --> 00:44:17,490
>> Karibu kila kitu wewe kufanya katika
Mbegu ni aina fulani ya kuwakusanya.

1030
00:44:17,490 --> 00:44:21,530
Hivyo kuwa na uwezo wa kuwa na uwezo wa kufafanua
hizi ndoo na kukupa hizi mbalimbali

1031
00:44:21,530 --> 00:44:24,950
sifa ya kuwa na uwezo wa swala juu,
wale maswali tajiri kusaidia wengi,

1032
00:44:24,950 --> 00:44:27,165
wengi, wengi maombi upatikanaji mwelekeo.

1033
00:44:27,165 --> 00:44:30,990

1034
00:44:30,990 --> 00:44:35,000
>> Kwa hiyo, jambo muhimu hash mengine
Je, ni inatupa utaratibu

1035
00:44:35,000 --> 00:44:37,740
kuwa na uwezo wa kuenea data kote.

1036
00:44:37,740 --> 00:44:40,390
NoSQL databaser kazi bora
wakati data ni sawasawa

1037
00:44:40,390 --> 00:44:41,740
kusambazwa katika nguzo.

1038
00:44:41,740 --> 00:44:44,530

1039
00:44:44,530 --> 00:44:47,050
Ni watu wangapi ni ukoo
na algorithms hashing?

1040
00:44:47,050 --> 00:44:49,860
Wakati mimi kusema hash na hashing--
kwa sababu hashing algorithm

1041
00:44:49,860 --> 00:44:54,140
ni njia ya kuwa na uwezo wa kuzalisha
thamani random kutoka thamani wowote.

1042
00:44:54,140 --> 00:44:59,300
Hivyo katika kesi hii,
hash algorithm sisi kukimbia ni ND 5 msingi.

1043
00:44:59,300 --> 00:45:04,765
>> Na kama nina kitambulisho, na hii
ni hash muhimu yangu, nina 1, 2, 3.

1044
00:45:04,765 --> 00:45:07,390
Wakati mimi kukimbia hash algorithm,
itakuja kurudi na kusema,

1045
00:45:07,390 --> 00:45:10,800
vizuri 1 ni sawa na 7B, 2
sawa 48, 3 sawa na CD.

1046
00:45:10,800 --> 00:45:13,092
Wao ni kuenea duniani nafasi muhimu.

1047
00:45:13,092 --> 00:45:14,050
Na kwa nini kufanya hivyo?

1048
00:45:14,050 --> 00:45:17,120
Kwa sababu hiyo inafanya kuhakikisha kwamba naweza
kuweka kumbukumbu katika nodes nyingi.

1049
00:45:17,120 --> 00:45:19,574
>> Kama mimi nina kufanya hii
kuongezwa, 1, 2, 3.

1050
00:45:19,574 --> 00:45:21,990
Na mimi kuwa hash mbalimbali kwamba
anaendesha katika kesi hii,

1051
00:45:21,990 --> 00:45:24,785
nafasi ndogo hash,
anaendesha kutoka 00 kwa FF,

1052
00:45:24,785 --> 00:45:27,951
kisha rekodi yatakuja katika
na wao ni kwenda 1, 2, 3, 4, 5,

1053
00:45:27,951 --> 00:45:30,390
6, 7, 8, 9, 10, 11, 12.

1054
00:45:30,390 --> 00:45:31,800
Nini kinatokea?

1055
00:45:31,800 --> 00:45:34,860
Kila kuingiza anaenda nodi moja.

1056
00:45:34,860 --> 00:45:36,070
Unaweza kuona nini namaanisha?

1057
00:45:36,070 --> 00:45:40,910
>> Kwa sababu wakati mimi kupasuliwa nafasi,
nikatandika kumbukumbu hizi hela,

1058
00:45:40,910 --> 00:45:45,950
na mimi kuhesabu, mimi nina kwenda kusema
kuhesabu 1 ina nafasi muhimu 0-54.

1059
00:45:45,950 --> 00:45:47,720
Kuhesabu 2 ni 55-89.

1060
00:45:47,720 --> 00:45:49,780
Kuhesabu 3 ni AA kwa FF.

1061
00:45:49,780 --> 00:45:53,740
Hivyo kama mimi nina kutumia mstari incrementing
Vitambulisho vya, unaweza kuona nini kinatokea.

1062
00:45:53,740 --> 00:45:57,410
1, 2, 3, 4, 5, 6, njia yote hadi 54.

1063
00:45:57,410 --> 00:46:00,030
Hivyo kama mimi nina hammering
Kumbukumbu katika mfumo,

1064
00:46:00,030 --> 00:46:02,030
kila kitu kuishia kwenda nodi moja.

1065
00:46:02,030 --> 00:46:03,160
>> Hiyo si nzuri.

1066
00:46:03,160 --> 00:46:04,820
Hiyo ni antipattern.

1067
00:46:04,820 --> 00:46:08,760
Katika MongoDB wana tatizo hili
kama huna kutumia ufunguo hash.

1068
00:46:08,760 --> 00:46:11,325
MongoDB inakupa fursa
ya hashing thamani muhimu.

1069
00:46:11,325 --> 00:46:13,950
Unapaswa daima kufanya hivyo, ikiwa
unatumia hash incrementing

1070
00:46:13,950 --> 00:46:17,380
muhimu katika MongoDB, au wewe utakuwa na
nailing kila kuandika kwa nodi moja,

1071
00:46:17,380 --> 00:46:21,290
na utakuwa kikwazo
kuandika throughput yako vibaya.

1072
00:46:21,290 --> 00:46:24,896
>> Watazamaji: Je, hivyo A9 169 katika alisema?

1073
00:46:24,896 --> 00:46:28,450
>> RICK Houlihan: Yeah, ni
mahali fulani karibu huko.

1074
00:46:28,450 --> 00:46:29,950
A9, sijui.

1075
00:46:29,950 --> 00:46:32,200
Wewe d na kupata mapacha wangu
kwa calculator alisema.

1076
00:46:32,200 --> 00:46:34,237
Ubongo wangu haifanyi kazi kama hiyo.

1077
00:46:34,237 --> 00:46:36,320
Watazamaji: Tu moja ya haraka
ya Mongo maoni yako.

1078
00:46:36,320 --> 00:46:39,530
Hivyo ni kitu ambacho huja ID
natively na Mongo kufanya hivyo?

1079
00:46:39,530 --> 00:46:40,179

1080
00:46:40,179 --> 00:46:41,470
RICK Houlihan: Je, ni kufanya hivyo?

1081
00:46:41,470 --> 00:46:42,970
Kama wewe taja hayo.

1082
00:46:42,970 --> 00:46:45,030
Kwa MongoDB, una fursa.

1083
00:46:45,030 --> 00:46:48,930
Unaweza specify-- kila hati katika
MongoDB ina kuwa na kusisitiza ID.

1084
00:46:48,930 --> 00:46:50,300
Hiyo ni thamani ya kipekee.

1085
00:46:50,300 --> 00:46:55,240
>> Katika MongoDB unaweza kutaja
kama hash au la.

1086
00:46:55,240 --> 00:46:56,490
Wao tu kuwapa fursa.

1087
00:46:56,490 --> 00:46:58,198
Kama unajua kwamba ni
kubahatisha, hakuna tatizo.

1088
00:46:58,198 --> 00:46:59,640
Huna haja ya kufanya hivyo.

1089
00:46:59,640 --> 00:47:04,260
Kama unajua kwamba siyo kubahatisha, kwamba
ni incrementing, basi kufanya hash.

1090
00:47:04,260 --> 00:47:06,880
>> Sasa jambo kuhusu
hashing, mara moja hash

1091
00:47:06,880 --> 00:47:08,800
a value-- na hii ni
kwa nini funguo hash ni daima

1092
00:47:08,800 --> 00:47:13,740
maswali ya kipekee, kwa sababu nimekuwa iliyopita
thamani, sasa siwezi kufanya swala mbalimbali.

1093
00:47:13,740 --> 00:47:15,640
Siwezi kusema ni hii
kati ya hiki au kile,

1094
00:47:15,640 --> 00:47:20,800
kwa sababu thamani hash si kwenda
kuwa sawa na thamani halisi.

1095
00:47:20,800 --> 00:47:24,570
Hivyo wakati wewe hash kwamba
ufunguo, ni usawa tu.

1096
00:47:24,570 --> 00:47:28,700
Hii ni kwa nini katika DynamoDB hash muhimu
maswali ni daima usawa tu.

1097
00:47:28,700 --> 00:47:32,090

1098
00:47:32,090 --> 00:47:34,700
>> Hivyo sasa katika mbalimbali key--
wakati mimi kuongeza kwamba ufunguo mbalimbali,

1099
00:47:34,700 --> 00:47:38,180
wale rekodi muhimu mbalimbali wote kuja katika na
wao kupata kuhifadhiwa kwenye kuhesabu huo.

1100
00:47:38,180 --> 00:47:42,430
Hivyo wao ni haraka sana, kwa urahisi
Rudishwa sababu hii ni hash,

1101
00:47:42,430 --> 00:47:43,220
hii ni mbalimbali.

1102
00:47:43,220 --> 00:47:44,928
Na unaona kila kitu
na hash sawa

1103
00:47:44,928 --> 00:47:48,550
anapata kuhifadhiwa kwenye kuhesabu nafasi hiyo.

1104
00:47:48,550 --> 00:47:53,889
Unaweza kutumia kwamba ufunguo mbalimbali ili kusaidia
Machapisho data yako karibu na mzazi wake.

1105
00:47:53,889 --> 00:47:55,180
Hivyo je, Mimi kweli kufanya hapa?

1106
00:47:55,180 --> 00:47:57,320
Hii ni moja ya uhusiano nyingi.

1107
00:47:57,320 --> 00:48:01,490
Uhusiano kati ya ufunguo hash
na ufunguo mbalimbali ni moja ya wengi.

1108
00:48:01,490 --> 00:48:03,490
Siwezi kuwa na funguo nyingi hash.

1109
00:48:03,490 --> 00:48:07,610
Naweza tu kuwa na aina mbalimbali
funguo ndani ya kila ufunguo hash.

1110
00:48:07,610 --> 00:48:11,910
>> Hash amefafanua mzazi,
mbalimbali amefafanua watoto.

1111
00:48:11,910 --> 00:48:15,240
Hivyo unaweza kuona kuna Analog hapa
kati ya kujenga mahusiano

1112
00:48:15,240 --> 00:48:18,840
na moja aina ya
anajenga katika NoSQL.

1113
00:48:18,840 --> 00:48:20,760
Watu majadiliano juu ya
NoSQL kama nonrelational.

1114
00:48:20,760 --> 00:48:22,200
Siyo nonrelational.

1115
00:48:22,200 --> 00:48:24,680
Takwimu daima ina uhusiano.

1116
00:48:24,680 --> 00:48:28,172
Mahusiano hayo tu
inatokana kwa njia tofauti.

1117
00:48:28,172 --> 00:48:29,880
Hebu majadiliano kidogo
kidogo kuhusu uimara.

1118
00:48:29,880 --> 00:48:34,860
Wakati kuandika kwa DynamoDB, anaandika
ni siku zote njia tatu kuigwa.

1119
00:48:34,860 --> 00:48:37,550
Kwa maana ya kuwa tuna tatu AZ ya.

1120
00:48:37,550 --> 00:48:39,160
AZ ya watu Upatikanaji Kanda.

1121
00:48:39,160 --> 00:48:43,430
Unaweza kufikiria Upatikanaji
Eneo la kituo cha data kama

1122
00:48:43,430 --> 00:48:45,447
au ukusanyaji wa vituo vya data.

1123
00:48:45,447 --> 00:48:47,780
Mambo hayo ni kijiografia
pekee kutoka kwa kila mmoja

1124
00:48:47,780 --> 00:48:51,610
katika maeneo mbalimbali kosa, hela
mbalimbali grids nguvu na mafuriko.

1125
00:48:51,610 --> 00:48:54,510
Kushindwa katika moja AZ si
kwenda kuchukua chini ya mwingine.

1126
00:48:54,510 --> 00:48:56,890
Pia ni wanaohusishwa
pamoja na nyuzi giza.

1127
00:48:56,890 --> 00:49:01,240
Ni inasaidia ndogo moja 1
millisecond utulivu kati ya AZS.

1128
00:49:01,240 --> 00:49:05,390
Hivyo muda halisi data replications
uwezo katika AZS mbalimbali.

1129
00:49:05,390 --> 00:49:09,990
>> Na mara nyingi mbalimbali AZ deployments
kukidhi mahitaji ya juu upatikanaji

1130
00:49:09,990 --> 00:49:12,930
ya mashirika mengi ya biashara.

1131
00:49:12,930 --> 00:49:16,139
Hivyo DynamoDB ni kuenea
hela AZS tatu na msingi.

1132
00:49:16,139 --> 00:49:19,430
Tunakwenda tu kwa maarifa kuandika
wakati mbili ya wale nodes tatu kurudi

1133
00:49:19,430 --> 00:49:21,470
na kusema, Yeah, mimi got it.

1134
00:49:21,470 --> 00:49:22,050
Kwanini hivyo?

1135
00:49:22,050 --> 00:49:25,950
Kwa sababu upande wa kusoma tuko tu
kwenda kukupa nyuma wakati data

1136
00:49:25,950 --> 00:49:27,570
sisi kupata kutoka nodes mbili.

1137
00:49:27,570 --> 00:49:30,490
>> Kama mimi nina kujinakilisha hela
tatu, na mimi nina kusoma kutoka mbili,

1138
00:49:30,490 --> 00:49:32,840
Mimi daima ni uhakika
kuwa na angalau moja

1139
00:49:32,840 --> 00:49:35,720
wale wasomaji kuwa
nakala hivi karibuni la data.

1140
00:49:35,720 --> 00:49:38,340
Hiyo ni nini inafanya DynamoDB thabiti.

1141
00:49:38,340 --> 00:49:42,450
Sasa unaweza kuchagua kurejea
wale thabiti wasomaji mbali.

1142
00:49:42,450 --> 00:49:45,070
Katika kesi ambayo mimi nina kwenda kusema,
Mimi itabidi tu kusoma kutoka nodi moja.

1143
00:49:45,070 --> 00:49:47,430
Na siwezi kuthibitisha itakuja
kuwa data zaidi sasa.

1144
00:49:47,430 --> 00:49:49,450
>> Hivyo kama kuandika anakuja katika,
hivyo siyo kuigwa bado,

1145
00:49:49,450 --> 00:49:50,360
wewe ni kwenda kupata nakala hiyo.

1146
00:49:50,360 --> 00:49:52,220
Hiyo ni kusoma hatimaye thabiti.

1147
00:49:52,220 --> 00:49:54,640
Na nini kwamba ni gharama nusu.

1148
00:49:54,640 --> 00:49:56,140
Hivyo hii ni kitu cha kufikiria.

1149
00:49:56,140 --> 00:50:00,160
Wakati wewe ni kusoma nje DynamoDB, na
wewe ni kuanzisha kusoma uwezo wako

1150
00:50:00,160 --> 00:50:04,430
vitengo, kama wewe kuchagua hatimaye
thabiti wasomaji, ni nafuu sana,

1151
00:50:04,430 --> 00:50:06,010
ni karibu nusu ya gharama.

1152
00:50:06,010 --> 00:50:09,342
>> Na hivyo anaokoa pesa.

1153
00:50:09,342 --> 00:50:10,300
Lakini hiyo ni uchaguzi wako.

1154
00:50:10,300 --> 00:50:12,925
Kama unataka kusoma thabiti au
kusoma hatimaye thabiti.

1155
00:50:12,925 --> 00:50:15,720
Hiyo ni kitu ambacho unaweza kuchagua.

1156
00:50:15,720 --> 00:50:17,659
>> Hebu majadiliano juu ya bahati.

1157
00:50:17,659 --> 00:50:19,450
Hivyo sisi alieleza kuwa
ngazi ya juu kuwakusanya.

1158
00:50:19,450 --> 00:50:23,720
Sisi tumepewa funguo hash, na
sisi tumepewa funguo mbalimbali.

1159
00:50:23,720 --> 00:50:24,320
Hiyo ni nzuri.

1160
00:50:24,320 --> 00:50:26,950
Na hiyo ndiyo mezani msingi, mimi
got muhimu moja hash, I got muhimu mbalimbali moja.

1161
00:50:26,950 --> 00:50:27,783
>> Hiyo ina maana gani?

1162
00:50:27,783 --> 00:50:30,410
Mimi nimepata sifa moja kwamba mimi
unaweza kukimbia maswali matajiri dhidi ya.

1163
00:50:30,410 --> 00:50:31,800
Ni muhimu mbalimbali.

1164
00:50:31,800 --> 00:50:35,530
Sifa nyingine ya kuwa item--
Siwezi kuchuja juu ya sifa hizo.

1165
00:50:35,530 --> 00:50:40,050
Lakini siwezi kufanya mambo kama, ni
huanza na, au ni mkuu kuliko mimi.

1166
00:50:40,050 --> 00:50:40,820
>> Je, mimi kufanya hivyo?

1167
00:50:40,820 --> 00:50:42,860
Mimi kujenga ripoti.

1168
00:50:42,860 --> 00:50:45,340
Kuna aina mbili za
bahati katika DynamoDB.

1169
00:50:45,340 --> 00:50:49,002
Ripoti ni kweli
mtazamo mwingine wa meza.

1170
00:50:49,002 --> 00:50:50,490
Na serikali za mitaa ripoti ya sekondari.

1171
00:50:50,490 --> 00:50:51,781
>> Wa kwanza tutaweza majadiliano juu.

1172
00:50:51,781 --> 00:50:57,740
Secondaries hivyo mitaa coexisted
juu ya kuhesabu sawa na data.

1173
00:50:57,740 --> 00:51:00,240
Na kama vile, wao ni juu ya
sawa kimwili nodi.

1174
00:51:00,240 --> 00:51:01,780
Wao ni kile tunachokiita thabiti.

1175
00:51:01,780 --> 00:51:04,599
Maana, wao kukiri
kuandika pamoja na meza.

1176
00:51:04,599 --> 00:51:06,890
Wakati kuandika huja katika,
tutaweza kuandika kupitia ripoti.

1177
00:51:06,890 --> 00:51:09,306
Tutaweza kuandika hadi meza,
na kisha sisi kukiri.

1178
00:51:09,306 --> 00:51:10,490
Hivyo hiyo ni thabiti.

1179
00:51:10,490 --> 00:51:13,174
Mara baada ya kuandika imekuwa
alikubali kutoka meza,

1180
00:51:13,174 --> 00:51:15,090
ni uhakika kwamba
ndani ripoti ya sekondari

1181
00:51:15,090 --> 00:51:18,380
itakuwa na maono sawa ya data.

1182
00:51:18,380 --> 00:51:22,390
Lakini nini wao kuruhusu kufanya ni
kufafanua funguo mbalimbali mbadala.

1183
00:51:22,390 --> 00:51:25,260
>> Una kutumia hash sawa
ufunguo kama meza ya msingi,

1184
00:51:25,260 --> 00:51:29,050
kwa sababu wao ni ushirikiano ziko juu
kuhesabu huo, na wao uko thabiti.

1185
00:51:29,050 --> 00:51:33,110
Lakini siwezi kujenga ripoti
na funguo mbalimbali tofauti.

1186
00:51:33,110 --> 00:51:41,590
Hivyo kwa mfano, kama ningekuwa na watengenezaji
kwamba alikuwa na mbichi sehemu meza kuja katika.

1187
00:51:41,590 --> 00:51:44,590
Na sehemu mbichi kuja, na
re kukusanywa na mkutano.

1188
00:51:44,590 --> 00:51:46,840
Na labda kuna kukumbuka.

1189
00:51:46,840 --> 00:51:50,240
>> Sehemu yoyote ambayo ilitolewa na huu
watengenezaji baada ya tarehe hii,

1190
00:51:50,240 --> 00:51:52,840
Mimi haja ya kuvuta kutoka mstari wangu.

1191
00:51:52,840 --> 00:51:55,950
Siwezi spin ripoti
kwamba itakuwa kuangalia,

1192
00:51:55,950 --> 00:52:00,760
kujumlisha katika tarehe ya
utengenezaji wa sehemu husika.

1193
00:52:00,760 --> 00:52:03,930
Hivyo kama kiwango cha juu yangu meza alikuwa
Tayari heshi na mtengenezaji,

1194
00:52:03,930 --> 00:52:07,655
labda ilikuwa kupangwa kwenye sehemu kitambulisho, mimi
Unaweza kuunda ripoti mbali meza kwamba

1195
00:52:07,655 --> 00:52:11,140
kama heshi na mtengenezaji na
kilicholengwa juu ya tarehe ya utengenezaji.

1196
00:52:11,140 --> 00:52:14,490
Na kwa njia hiyo mimi naweza kusema, kitu chochote ambacho
mara viwandani kati ya tarehe hizi,

1197
00:52:14,490 --> 00:52:16,804
Mimi haja ya kuvuta kutoka mstari.

1198
00:52:16,804 --> 00:52:18,220
Hivyo hiyo ni mtaa ripoti ya sekondari.

1199
00:52:18,220 --> 00:52:22,280
>> Hawa wana athari za
kikwazo hash yako nafasi muhimu.

1200
00:52:22,280 --> 00:52:24,360
Kwa sababu wao ushirikiano kuwepo
juu ya huo kuhifadhi nodi,

1201
00:52:24,360 --> 00:52:26,860
wao kikomo muhimu hash
nafasi ya 10 gigabytes.

1202
00:52:26,860 --> 00:52:28,950
DynamoDB, chini ya
meza, itakuwa kuigawa

1203
00:52:28,950 --> 00:52:31,380
meza yako kila gigabytes 10.

1204
00:52:31,380 --> 00:52:34,760
Wakati wewe kuweka gigs 10 ya data katika, sisi
kwenda [PHH], na sisi kuongeza nodi mwingine.

1205
00:52:34,760 --> 00:52:38,120

1206
00:52:38,120 --> 00:52:42,070
>> Sisi si kupasuliwa LSI
hela partitions nyingi.

1207
00:52:42,070 --> 00:52:43,200
Tutaweza umegawanyika meza.

1208
00:52:43,200 --> 00:52:44,679
Lakini sisi si kugawa LSI.

1209
00:52:44,679 --> 00:52:46,470
Hivyo hiyo ni kitu
muhimu kuelewa

1210
00:52:46,470 --> 00:52:50,070
ni kama wewe ni kufanya sana,
sana, aggregations kubwa sana,

1211
00:52:50,070 --> 00:52:53,860
kisha utaenda kuwa mdogo
kwa gigabytes 10 katika LSIs yako.

1212
00:52:53,860 --> 00:52:56,640
>> Kama hiyo kesi, tunaweza
kutumia secondaries kimataifa.

1213
00:52:56,640 --> 00:52:58,630
Global secondaries ni
kweli meza nyingine.

1214
00:52:58,630 --> 00:53:01,720
Zipo kabisa mbali na
upande wa meza yako ya msingi.

1215
00:53:01,720 --> 00:53:04,680
Nao naomba kupata
muundo tofauti kabisa.

1216
00:53:04,680 --> 00:53:08,010
Hivyo kufikiria kama data ni kuwa kuingizwa
ndani ya mbao mbili tofauti, muundo

1217
00:53:08,010 --> 00:53:09,220
katika njia mbili tofauti.

1218
00:53:09,220 --> 00:53:11,360
>> Siwezi kufafanua kabisa
tofauti hash muhimu.

1219
00:53:11,360 --> 00:53:13,490
Siwezi kufafanua kabisa
tofauti mbalimbali muhimu.

1220
00:53:13,490 --> 00:53:15,941
Na siwezi kukimbia huu
kabisa kujitegemea.

1221
00:53:15,941 --> 00:53:18,190
Kama jambo la kweli, nimekuwa
provisioned kusoma uwezo wangu

1222
00:53:18,190 --> 00:53:21,090
na kuandika uwezo wangu kwa
bahati kimataifa sekondari

1223
00:53:21,090 --> 00:53:24,240
kabisa kujitegemea
ya meza yangu ya msingi.

1224
00:53:24,240 --> 00:53:26,640
Kama mimi kufafanua kwamba ripoti, nawaambia
ni kiasi gani kusoma na kuandika

1225
00:53:26,640 --> 00:53:28,610
uwezo ni kwenda kutumia.

1226
00:53:28,610 --> 00:53:31,490
>> Na kwamba ni tofauti
kutoka meza yangu ya msingi.

1227
00:53:31,490 --> 00:53:35,240
Sasa wote wawili wa bahati kuruhusu sisi
si tu kufafanua hash na mbalimbali funguo,

1228
00:53:35,240 --> 00:53:38,610
lakini wao kuruhusu sisi
mradi maadili ziada.

1229
00:53:38,610 --> 00:53:44,950
Hivyo kama nataka kusoma mbali index,
na nataka kupata baadhi ya seti ya data,

1230
00:53:44,950 --> 00:53:48,327
Sina haja ya kwenda nyuma ya kuu
meza ya kupata sifa za ziada.

1231
00:53:48,327 --> 00:53:50,660
Siwezi mradi wale ziada
sifa katika meza

1232
00:53:50,660 --> 00:53:53,440
kusaidia upatikanaji mfano.

1233
00:53:53,440 --> 00:53:57,700
Najua sisi ni pengine kuingia katika baadhi
kweli, really-- kuingia katika Magugu

1234
00:53:57,700 --> 00:53:58,910
hapa juu ya baadhi ya mambo haya.

1235
00:53:58,910 --> 00:54:02,725
Sasa mimi got Drift nje ya hii.

1236
00:54:02,725 --> 00:54:07,320
>> Watazamaji: [inaudible]
--table muhimu maana alikuwa hash?

1237
00:54:07,320 --> 00:54:08,840
Awali hash?

1238
00:54:08,840 --> 00:54:09,340
Mbalimbali slats?

1239
00:54:09,340 --> 00:54:10,200
>> RICK Houlihan: Ndiyo.

1240
00:54:10,200 --> 00:54:11,070
Ndiyo.

1241
00:54:11,070 --> 00:54:15,260
Ufunguo meza kimsingi
anasema nyuma kwa bidhaa.

1242
00:54:15,260 --> 00:54:19,280
Hivyo ripoti ni pointer nyuma
vitu awali juu ya meza.

1243
00:54:19,280 --> 00:54:22,910
Sasa unaweza kuchagua kujenga
ripoti kwamba tu ana ufunguo meza,

1244
00:54:22,910 --> 00:54:24,840
na hakuna mali nyingine.

1245
00:54:24,840 --> 00:54:26,570
Na kwa nini huenda mimi kufanya hivyo?

1246
00:54:26,570 --> 00:54:28,570
Naam, labda nina vitu kubwa sana.

1247
00:54:28,570 --> 00:54:31,660
>> Mimi kwa kweli tu haja ya kujua which--
upatikanaji mfano wangu anaweza kusema,

1248
00:54:31,660 --> 00:54:33,760
ambayo vitu vyenye mali hii?

1249
00:54:33,760 --> 00:54:35,780
Hawana haja ya kurudi bidhaa.

1250
00:54:35,780 --> 00:54:37,800
Mimi tu haja ya kujua
ambayo vitu vyenye yake.

1251
00:54:37,800 --> 00:54:40,700
Hivyo unaweza kujenga bahati
kwamba tu wana ufunguo meza.

1252
00:54:40,700 --> 00:54:43,360
>> Lakini hiyo ni kimsingi nini
ripoti katika orodha ni kwa.

1253
00:54:43,360 --> 00:54:46,280
Ni kwa kuwa na uwezo wa haraka
kubaini ambayo rekodi,

1254
00:54:46,280 --> 00:54:49,470
ambayo safu, ambayo
vitu katika meza na

1255
00:54:49,470 --> 00:54:51,080
mali kwamba mimi nina kwa ajili ya kutafuta.

1256
00:54:51,080 --> 00:54:53,610

1257
00:54:53,610 --> 00:54:54,860
>> GSIs, hivyo ni jinsi gani kazi?

1258
00:54:54,860 --> 00:54:58,340
GSIs kimsingi ni Asynchronous.

1259
00:54:58,340 --> 00:55:02,570
Update anakuja katika meza,
meza ni kisha asynchronously updated

1260
00:55:02,570 --> 00:55:03,720
wote wa GSIs yako.

1261
00:55:03,720 --> 00:55:06,680
Hii ni kwa nini GSIs ni
Hatimaye thabiti.

1262
00:55:06,680 --> 00:55:09,440
>> Ni muhimu kutambua kwamba
wakati wewe ni kujenga GSIs,

1263
00:55:09,440 --> 00:55:13,110
na wewe kuelewa wewe ni kujenga
mwingine mwelekeo wa aggregation--

1264
00:55:13,110 --> 00:55:16,594
sasa hebu sema mfano mzuri
hapa ni watengenezaji.

1265
00:55:16,594 --> 00:55:19,260
Nadhani anaweza kuwa kuongelea
kifaa cha matibabu watengenezaji.

1266
00:55:19,260 --> 00:55:23,870
Wazalishaji kifaa cha matibabu
mara nyingi na sehemu serialized.

1267
00:55:23,870 --> 00:55:28,070
Sehemu ambayo kwenda katika
badala hip zote

1268
00:55:28,070 --> 00:55:30,200
kuwa kidogo idadi Serial juu yao.

1269
00:55:30,200 --> 00:55:33,584
Na wangeweza na mamilioni na
mamilioni na mabilioni ya sehemu

1270
00:55:33,584 --> 00:55:35,000
katika vifaa vyote walivyo meli.

1271
00:55:35,000 --> 00:55:37,440
Vizuri, wanahitaji jumla ya mabao chini ya
vipimo mbalimbali, maeneo yote

1272
00:55:37,440 --> 00:55:39,520
katika mkutano, kila
sehemu ambayo yalifanywa

1273
00:55:39,520 --> 00:55:41,670
kwenye mstari fulani, kila
sehemu waliokuja

1274
00:55:41,670 --> 00:55:44,620
katika kutoka kwa watengenezaji fulani
juu ya tarehe fulani.

1275
00:55:44,620 --> 00:55:47,940
Na aggregations hizi wakati mwingine
kuamka katika mabilioni.

1276
00:55:47,940 --> 00:55:50,550
>> Hivyo mimi kazi na baadhi ya
hizi watu ambao ni mateso

1277
00:55:50,550 --> 00:55:53,156
kwa sababu wao ni kujenga
aggregations haya ginormous

1278
00:55:53,156 --> 00:55:54,280
katika bahati zao za sekondari.

1279
00:55:54,280 --> 00:55:57,070
Wapate kuwa sehemu mbichi
meza kwamba anakuja kama hash tu.

1280
00:55:57,070 --> 00:55:59,090
Kila sehemu ina kipekee Serial idadi.

1281
00:55:59,090 --> 00:56:00,975
Mimi kutumia idadi Serial kama hash.

1282
00:56:00,975 --> 00:56:01,600
Ni nzuri.

1283
00:56:01,600 --> 00:56:04,160
Data My mbichi meza ni kuenea
wote katika nafasi muhimu.

1284
00:56:04,160 --> 00:56:05,930
My [? kuandika?]
[? kumeza?] ni wa kushangaza.

1285
00:56:05,930 --> 00:56:07,876
Mimi kuchukua mengi ya data.

1286
00:56:07,876 --> 00:56:09,500
Kisha wanachokifanya ni wao kujenga GSI.

1287
00:56:09,500 --> 00:56:12,666
Na mimi kusema, unajua nini, mimi wanahitaji kuona
sehemu zote kwa watengenezaji huu.

1288
00:56:12,666 --> 00:56:15,060
Naam, kwa ghafla mimi nina
kuchukua bilioni safu,

1289
00:56:15,060 --> 00:56:17,550
na mambo yao kwenye
nodi moja, kwa sababu wakati

1290
00:56:17,550 --> 00:56:21,170
Mimi kama jumla ya mabao
watengenezaji ID kama hash,

1291
00:56:21,170 --> 00:56:25,410
na sehemu ya simu kama mbalimbali,
kisha kwa ghafla mimi nina

1292
00:56:25,410 --> 00:56:30,530
kuweka bilioni sehemu katika kile
watengenezaji huu ina mikononi kwangu.

1293
00:56:30,530 --> 00:56:34,447
>> Ambazo zinaweza kusababisha mengi
ya shinikizo juu ya GSI,

1294
00:56:34,447 --> 00:56:36,030
tena, kwa sababu mimi nina hammering nodi moja.

1295
00:56:36,030 --> 00:56:38,350
Mimi nina kuweka haya yote
kuwekeza katika nodi moja.

1296
00:56:38,350 --> 00:56:40,940
Na hiyo ndiyo halisi ni tatizo matumizi ya kesi.

1297
00:56:40,940 --> 00:56:43,479
Sasa, I got mpango mzuri
mfano kwa jinsi gani kuepuka hilo.

1298
00:56:43,479 --> 00:56:45,770
Na hiyo ni moja ya matatizo
kwamba mimi daima kazi pamoja.

1299
00:56:45,770 --> 00:56:49,590
Lakini nini kinatokea, ni GSI inaweza
si kuwa na kuandika kutosha uwezo

1300
00:56:49,590 --> 00:56:52,330
kuwa na uwezo wa kushinikiza wale wote
safu katika nodi moja.

1301
00:56:52,330 --> 00:56:55,390
Na kile kinachotokea basi ni
msingi, meza ya mteja,

1302
00:56:55,390 --> 00:57:00,180
meza ya msingi itakuwa kabwa
kwa sababu GSI hawezi kuweka juu.

1303
00:57:00,180 --> 00:57:02,980
Hivyo kiwango cha yangu kuingiza mapenzi
kuanguka juu ya meza msingi

1304
00:57:02,980 --> 00:57:06,230
kama GSI yangu anajaribu kuweka juu.

1305
00:57:06,230 --> 00:57:08,850
>> Haki wote, hivyo GSI wa, LSI wa,
ambayo mtu anatakiwa mimi kutumia?

1306
00:57:08,850 --> 00:57:12,290
LSI ya ni thabiti.

1307
00:57:12,290 --> 00:57:13,750
GSI ya watu hatimaye thabiti.

1308
00:57:13,750 --> 00:57:17,490
Kama hiyo ni sawa, mimi kupendekeza kutumia
GSI, wao uko rahisi zaidi.

1309
00:57:17,490 --> 00:57:20,270
LSI inaweza kuwa inatokana kama GSI.

1310
00:57:20,270 --> 00:57:27,040
Na kama kawaida data per funguo hash katika
ukusanyaji yako kuzidi 10 gigabytes,

1311
00:57:27,040 --> 00:57:31,050
basi wewe ni kwenda kutaka kutumia kwamba
GSI kwa sababu ni tu kikomo kwa bidii.

1312
00:57:31,050 --> 00:57:32,035
>> Haki wote, hivyo kuongeza.

1313
00:57:32,035 --> 00:57:35,210

1314
00:57:35,210 --> 00:57:37,460
Throughput katika Dynamo DB, wewe
can utoaji [inaudible]

1315
00:57:37,460 --> 00:57:38,680
throughput kwa meza.

1316
00:57:38,680 --> 00:57:42,740
Sisi wateja ambazo zina
provisioned 60 billion--

1317
00:57:42,740 --> 00:57:45,970
wanafanya maombi bilioni 60, mara kwa mara
mbio katika zaidi ya milioni maombi

1318
00:57:45,970 --> 00:57:47,790
kwa pili juu ya meza yetu.

1319
00:57:47,790 --> 00:57:50,360
Kuna kweli hakuna
kikomo kinadharia kwa kiasi gani

1320
00:57:50,360 --> 00:57:53,730
na jinsi ya kufunga meza
wanaweza kukimbia katika Dynamo DB.

1321
00:57:53,730 --> 00:57:55,920
Kuna baadhi ya laini
mipaka juu ya akaunti yako

1322
00:57:55,920 --> 00:57:58,170
kwamba sisi kuweka katika huko ili
kwamba huna kwenda mambo.

1323
00:57:58,170 --> 00:58:00,070
Kama unataka zaidi ya
kwamba, si tatizo.

1324
00:58:00,070 --> 00:58:00,820
Wewe kuja kutuambia.

1325
00:58:00,820 --> 00:58:02,810
Tutaweza kurejea kwenye piga.

1326
00:58:02,810 --> 00:58:08,210
>> Kila akaunti ni mdogo kwa baadhi ya kiwango
katika kila huduma, tu mbali bat

1327
00:58:08,210 --> 00:58:11,920
hivyo watu hawana kwenda mambo
kupata wenyewe katika matatizo.

1328
00:58:11,920 --> 00:58:12,840
Hakuna kikomo kwa ukubwa.

1329
00:58:12,840 --> 00:58:14,940
Unaweza kuweka idadi yoyote
ya vitu kwenye meza.

1330
00:58:14,940 --> 00:58:17,620
Ukubwa wa bidhaa ni
mdogo kwa 400 kilobytes kila,

1331
00:58:17,620 --> 00:58:20,050
hiyo inaweza kuwa bidhaa si sifa.

1332
00:58:20,050 --> 00:58:24,200
Hivyo kiasi cha sifa zote
ni mdogo kwa 400 kilobytes.

1333
00:58:24,200 --> 00:58:27,300
Na kisha tena, tuna
kuwa kidogo LSI suala

1334
00:58:27,300 --> 00:58:30,405
na 10 gigabyte kikomo kwa hash.

1335
00:58:30,405 --> 00:58:33,280
Watazamaji: idadi ndogo, mimi kukosa
nini wewe kuniambia, kwamba is--

1336
00:58:33,280 --> 00:58:36,830
Watazamaji: Oh, 400 kilobaiti
ni kiwango cha juu kabisa kwa kila kitu.

1337
00:58:36,830 --> 00:58:39,570
Hivyo bidhaa ina sifa zote.

1338
00:58:39,570 --> 00:58:43,950
Hivyo 400 k ni ukubwa jumla
ya bidhaa kwamba, 400 kilobytes.

1339
00:58:43,950 --> 00:58:46,170
Hivyo sifa zote za
pamoja, takwimu zote

1340
00:58:46,170 --> 00:58:49,140
hiyo ni katika wale sifa zote,
zitakunjwa katika ukubwa jumla,

1341
00:58:49,140 --> 00:58:51,140
sasa leo bidhaa kikomo ni 400 k.

1342
00:58:51,140 --> 00:58:54,390

1343
00:58:54,390 --> 00:58:57,046
Hivyo kuongeza tena, mafanikio
kupitia partitioning.

1344
00:58:57,046 --> 00:58:58,920
Throughput ni provisioned
katika ngazi ya meza.

1345
00:58:58,920 --> 00:59:00,160
Na kuna kweli knobs mbili.

1346
00:59:00,160 --> 00:59:02,400
Tumesoma uwezo
na kuandika uwezo.

1347
00:59:02,400 --> 00:59:05,530
>> Basi hizi ni kubadilishwa
kujitegemea ya kila mmoja.

1348
00:59:05,530 --> 00:59:08,640
Hatua RCU ya madhubuti sambamba anasoma.

1349
00:59:08,640 --> 00:59:13,005
Sawa, hivyo kama wewe ni kusema nataka 1000
RCU ya wale ni madhubuti thabiti,

1350
00:59:13,005 --> 00:59:14,130
wale ni wasomaji thabiti.

1351
00:59:14,130 --> 00:59:17,130
Kama umesema nataka
hatimaye thabiti wasomaji,

1352
00:59:17,130 --> 00:59:19,402
unaweza utoaji 1000
RCU wa, wewe ni kwenda

1353
00:59:19,402 --> 00:59:21,840
kupata 2,000 hatimaye
thabiti anasoma.

1354
00:59:21,840 --> 00:59:25,940
Na nusu ya bei kwa wale
Hatimaye wajumbe katika anasoma.

1355
00:59:25,940 --> 00:59:28,520
>> Tena, kubadilishwa
kujitegemea ya kila mmoja.

1356
00:59:28,520 --> 00:59:32,900
Na wao wana throughput--
Kama wewe hutumia 100% ya RCU yako,

1357
00:59:32,900 --> 00:59:35,960
wewe si kwenda na athari
upatikanaji wa haki zako.

1358
00:59:35,960 --> 00:59:40,161
Hivyo wao ni kabisa
uhuru wa kila mmoja.

1359
00:59:40,161 --> 00:59:43,160
Haki wote, hivyo moja ya mambo ambayo
Nilivyoeleza kwa kifupi ilikuwa throttling.

1360
00:59:43,160 --> 00:59:44,320
Throttling ni mbaya.

1361
00:59:44,320 --> 00:59:47,311
Throttling inaonyesha mbaya hakuna SQL.

1362
00:59:47,311 --> 00:59:50,310
Kuna mambo tunaweza kufanya ili kusaidia
wewe kupunguza throttling kwamba

1363
00:59:50,310 --> 00:59:51,040
ni zinaendelea.

1364
00:59:51,040 --> 00:59:53,240
Lakini ufumbuzi bora
na hili ni hebu kuchukua

1365
00:59:53,240 --> 00:59:58,000
a kuangalia nini unafanya, kwa sababu
kuna kupambana na mfano katika kucheza hapa.

1366
00:59:58,000 --> 01:00:02,140
>> Mambo haya, mambo kama yasiyo ya sare
mzigo, funguo moto, partitions moto.

1367
01:00:02,140 --> 01:00:06,210
Mimi kupiga fulani nafasi muhimu
ngumu sana kwa sababu fulani fulani.

1368
01:00:06,210 --> 01:00:07,080
Kwa nini mimi kufanya hili?

1369
01:00:07,080 --> 01:00:08,710
Hebu kufikiri kuwa nje.

1370
01:00:08,710 --> 01:00:10,427
Mimi kuchanganya data zangu moto na data baridi.

1371
01:00:10,427 --> 01:00:12,510
Mimi kuruhusu meza yangu kupata
kubwa, lakini kuna kweli

1372
01:00:12,510 --> 01:00:15,970
tu baadhi subset ya data
hiyo ni kweli kuvutia kwangu.

1373
01:00:15,970 --> 01:00:20,290
Hivyo kwa data gogo, kwa mfano, mengi ya
wateja, wao kupata kuingia data kila siku.

1374
01:00:20,290 --> 01:00:22,490
Wao got kiasi kikubwa cha data gogo.

1375
01:00:22,490 --> 01:00:25,940
>> Kama wewe ni utupaji tu gogo kwamba wote
data katika moja kubwa meza, baada ya muda

1376
01:00:25,940 --> 01:00:28,070
meza ambayo inaenda kupata mkubwa.

1377
01:00:28,070 --> 01:00:30,950
Lakini mimi nina kweli nia tu katika
masaa 24 iliyopita, mwisho wa siku saba,

1378
01:00:30,950 --> 01:00:31,659
siku 30 zilizopita.

1379
01:00:31,659 --> 01:00:34,074
Chochote dirisha la muda
kwamba mimi nina nia ya kuangalia

1380
01:00:34,074 --> 01:00:37,010
kwa tukio hilo kuwa ananisumbua, au
tukio hilo kuwa jambo la kushangaza kwangu,

1381
01:00:37,010 --> 01:00:39,540
hiyo ni tu dirisha wakati huo nahitaji.

1382
01:00:39,540 --> 01:00:42,470
Hivyo kwa nini mimi kuweka miaka 10
thamani ya gogo data katika meza?

1383
01:00:42,470 --> 01:00:45,030
Nini kinachosababisha ni
meza kipande.

1384
01:00:45,030 --> 01:00:45,880
>> Anapata kubwa.

1385
01:00:45,880 --> 01:00:48,340
Ni kuanza kueneza
hela maelfu ya nodes.

1386
01:00:48,340 --> 01:00:51,380
Na kwa kuwa uwezo wako
ni hivyo chini, uko

1387
01:00:51,380 --> 01:00:54,090
kweli kiwango kikwazo juu ya kila
moja ya nodes wale binafsi.

1388
01:00:54,090 --> 01:00:57,120
Basi hebu kuanza kuangalia jinsi
kufanya sisi unaendelea meza kwamba zaidi.

1389
01:00:57,120 --> 01:01:01,502
Je, sisi kusimamia data kwamba kidogo
bora kuepuka matatizo haya.

1390
01:01:01,502 --> 01:01:02,710
Na nini ili kuangalia kama?

1391
01:01:02,710 --> 01:01:04,370
Hii ni nini kwamba inaonekana kama.

1392
01:01:04,370 --> 01:01:06,790
Hii ni nini mbaya NoSQL inaonekana kama.

1393
01:01:06,790 --> 01:01:07,830
>> I got muhimu moto hapa.

1394
01:01:07,830 --> 01:01:10,246
Kama ukiangalia kwa upande hapa,
hizi ni partitions yangu yote.

1395
01:01:10,246 --> 01:01:12,630
I got partitions 16 hapa
kwenye orodha hii tu.

1396
01:01:12,630 --> 01:01:13,630
Sisi kufanya hivyo wakati wote.

1397
01:01:13,630 --> 01:01:15,046
Mimi kukimbia hii kwa wateja wakati wote.

1398
01:01:15,046 --> 01:01:16,550
Ni wito ramani joto.

1399
01:01:16,550 --> 01:01:20,590
Joto ramani anasema mimi jinsi uko
kupata nafasi yako muhimu.

1400
01:01:20,590 --> 01:01:23,700
Na nini hii ni kuwaambia mimi ni
kwamba kuna mtu fulani hash

1401
01:01:23,700 --> 01:01:26,330
kwamba guy hii anapenda
kubwa sana, kwa sababu yeye ni

1402
01:01:26,330 --> 01:01:28,250
kupiga ni kweli, ngumu kweli kweli.

1403
01:01:28,250 --> 01:01:29,260
>> Hivyo bluu ni nzuri.

1404
01:01:29,260 --> 01:01:29,900
Tunapenda bluu.

1405
01:01:29,900 --> 01:01:30,720
Sisi si kama nyekundu.

1406
01:01:30,720 --> 01:01:33,120
Red ambako shinikizo
anapata hadi 100%.

1407
01:01:33,120 --> 01:01:35,560
100%, sasa wewe ni kwenda kuwa kabwa.

1408
01:01:35,560 --> 01:01:39,030
Hivyo wakati wowote unaweza kuona mistari yoyote nyekundu kama
Haya na siyo tu Dynamo DB--

1409
01:01:39,030 --> 01:01:41,630
kila database NoSQL ina tatizo hili.

1410
01:01:41,630 --> 01:01:44,640
Kuna kupambana na mwelekeo kwamba wanaweza
gari aina hii ya hali ya.

1411
01:01:44,640 --> 01:01:49,070
Nini mimi ni mimi kazi na wateja
kupunguza masharti hayo.

1412
01:01:49,070 --> 01:01:51,840
>> Na nini ili kuangalia kama?

1413
01:01:51,840 --> 01:01:54,260
Na hii ni kupata zaidi
nje ya Dynamo DB throughput,

1414
01:01:54,260 --> 01:01:56,176
lakini ni kweli kupata
zaidi nje ya NoSQL.

1415
01:01:56,176 --> 01:01:58,740
Hii si vikwazo kwa Dynamo.

1416
01:01:58,740 --> 01:02:02,050
Hii ni definitely-- mimi
nafanya kazi katika Mongo.

1417
01:02:02,050 --> 01:02:04,090
Mimi nina mazoea na majukwaa mengi NoSQL.

1418
01:02:04,090 --> 01:02:06,830
Kila mmoja ana aina hii
matatizo moto muhimu.

1419
01:02:06,830 --> 01:02:10,320
Ili kupata zaidi nje ya yoyote NoSQL
Mbegu, hasa Dynamo DB,

1420
01:02:10,320 --> 01:02:13,320
unataka kujenga meza
ambapo hash muhimu kipengele ina

1421
01:02:13,320 --> 01:02:18,590
idadi kubwa ya maadili tofauti,
shahada ya juu ya cardinality.

1422
01:02:18,590 --> 01:02:22,530
Kwa sababu hiyo ina maana mimi nina kuandika
kwa kura ya ndoo tofauti.

1423
01:02:22,530 --> 01:02:24,870
>> Ndoo zaidi mimi nina
kuandika, zaidi ya uwezekano

1424
01:02:24,870 --> 01:02:29,100
Mimi ni kueneza kwamba kuandika mzigo au
kusoma mzigo nje hela nodes nyingi,

1425
01:02:29,100 --> 01:02:33,560
zaidi Mimi ni kuwa na
throughput ya juu juu ya meza.

1426
01:02:33,560 --> 01:02:37,440
Na kisha nataka maadili kuwa
aliomba haki sawasawa baada ya muda

1427
01:02:37,440 --> 01:02:39,430
na usawa kama nasibu iwezekanavyo.

1428
01:02:39,430 --> 01:02:42,410
Naam, hiyo ni aina ya kuvutia,
kwa sababu siwezi kweli

1429
01:02:42,410 --> 01:02:43,960
kudhibiti wakati watumiaji kuja.

1430
01:02:43,960 --> 01:02:47,645
Hivyo inatosha kusema, kama sisi kuenea
mambo ya nje katika nafasi muhimu,

1431
01:02:47,645 --> 01:02:49,270
tutaweza pengine kuwa katika umbo bora.

1432
01:02:49,270 --> 01:02:51,522
>> Kuna baadhi ya
kiasi cha utoaji wa muda

1433
01:02:51,522 --> 01:02:53,230
kwamba wewe si kwenda
kuweza kudhibiti.

1434
01:02:53,230 --> 01:02:55,438
Lakini hayo ni kweli
vipimo mbili kwamba tuna,

1435
01:02:55,438 --> 01:02:58,800
nafasi, upatikanaji sawasawa
kuenea, wakati, maombi

1436
01:02:58,800 --> 01:03:01,040
alipofika sawasawa spaced kwa wakati.

1437
01:03:01,040 --> 01:03:03,110
Na kama hayo mawili
hali ni kuwa alikutana,

1438
01:03:03,110 --> 01:03:05,610
basi hiyo ni nini ni
kwenda kuangalia kama.

1439
01:03:05,610 --> 01:03:07,890
Hii ni nicer.

1440
01:03:07,890 --> 01:03:08,890
Sisi ni kweli na furaha hapa.

1441
01:03:08,890 --> 01:03:10,432
Sisi tumepewa hata sana upatikanaji mfano.

1442
01:03:10,432 --> 01:03:13,098
Naam, labda wewe ni kupata
shinikizo kidogo kila sasa na kisha,

1443
01:03:13,098 --> 01:03:14,830
lakini hakuna kitu kweli pia kina.

1444
01:03:14,830 --> 01:03:17,660
Hivyo ni ajabu mara ngapi,
wakati mimi kazi na wateja,

1445
01:03:17,660 --> 01:03:20,670
kwamba graph kwanza na nyekundu kubwa
bar na vitu vyote mbaya njano ni

1446
01:03:20,670 --> 01:03:23,147
kila mahali, sisi
kupata kufanyika kwa zoezi

1447
01:03:23,147 --> 01:03:24,980
baada ya miezi michache
ya re-usanifu,

1448
01:03:24,980 --> 01:03:28,050
wao ni mbio exact
mzigo wa kazi katika halisi mzigo huo.

1449
01:03:28,050 --> 01:03:30,140
Na hii ni nini ni kuangalia kama sasa.

1450
01:03:30,140 --> 01:03:36,600
Hivyo nini kupata na NoSQL ni
data schema kwamba ni kabisa

1451
01:03:36,600 --> 01:03:38,510
amefungwa kwa upatikanaji mfano.

1452
01:03:38,510 --> 01:03:42,170
>> Na unaweza kuongeza takwimu ambazo schema
kuunga mkono kwamba upatikanaji mfano.

1453
01:03:42,170 --> 01:03:45,490
Kama huna, basi wewe ni kwenda
kuona wale aina ya matatizo

1454
01:03:45,490 --> 01:03:46,710
na funguo wale moto.

1455
01:03:46,710 --> 01:03:50,518
>> Watazamaji: Naam, inevitably baadhi ya maeneo
ni kwenda kuwa moto zaidi kuliko wengine.

1456
01:03:50,518 --> 01:03:51,450
>> RICK Houlihan: Daima.

1457
01:03:51,450 --> 01:03:51,960
Daima.

1458
01:03:51,960 --> 01:03:54,620
Yeah, I mean kuna siku zote
a-- na tena, kuna

1459
01:03:54,620 --> 01:03:56,980
baadhi kubuni mifumo tutaweza kupata njia
kwamba majadiliano kuhusu jinsi ya kukabiliana

1460
01:03:56,980 --> 01:03:58,480
na haya aggregations super kubwa.

1461
01:03:58,480 --> 01:04:01,260
I mean, I got kuwa nao,
jinsi gani sisi kukabiliana na changamoto hizo?

1462
01:04:01,260 --> 01:04:03,760
I got nzuri matumizi ya kesi
kwamba tutaweza majadiliano juu ya jambo hilo.

1463
01:04:03,760 --> 01:04:05,940
>> Haki wote, hivyo hebu majadiliano
kuhusu baadhi ya wateja sasa.

1464
01:04:05,940 --> 01:04:06,950
Haya guys ni AdRoll.

1465
01:04:06,950 --> 01:04:08,990
Sijui kama wewe ni
ukoo na AdRoll.

1466
01:04:08,990 --> 01:04:10,781
Pengine kuwaona
mengi juu ya browser.

1467
01:04:10,781 --> 01:04:14,230
Wao ni tangazo re-kulenga, wao uko
tangazo re-kulenga biashara kubwa

1468
01:04:14,230 --> 01:04:14,940
huko nje.

1469
01:04:14,940 --> 01:04:17,792
Wao kwa kawaida mara kwa mara kukimbia juu
Shughuli bilioni 60 kwa siku.

1470
01:04:17,792 --> 01:04:20,000
Re kufanya zaidi ya milioni
shughuli kwa pili.

1471
01:04:20,000 --> 01:04:22,660
Wao nimepata meza pretty rahisi
muundo, meza shughuli nyingi zaidi.

1472
01:04:22,660 --> 01:04:26,450
Ni kimsingi tu
hash muhimu ni cookie,

1473
01:04:26,450 --> 01:04:29,010
mbalimbali ni idadi ya watu
jamii, na kisha

1474
01:04:29,010 --> 01:04:31,220
Sifa ya tatu ni alama.

1475
01:04:31,220 --> 01:04:33,720
>> Hivyo sisi sote tuna cookies katika
kisakuzi wetu kutoka guys haya.

1476
01:04:33,720 --> 01:04:35,900
Na wakati wa kwenda
mfanyabiashara kushiriki,

1477
01:04:35,900 --> 01:04:39,390
wao kimsingi alama wewe hela
idadi ya watu makundi mbalimbali.

1478
01:04:39,390 --> 01:04:42,070
Baada ya kwenda kwa tovuti na
unasema nataka kuona ad-- hii

1479
01:04:42,070 --> 01:04:44,920
au kimsingi huna kusema that--
lakini wakati kwenda kwenye tovuti

1480
01:04:44,920 --> 01:04:47,550
wanasema wanataka kuona tangazo hili.

1481
01:04:47,550 --> 01:04:49,370
Na wao kwenda kupata kwamba tangazo kutoka AdRoll.

1482
01:04:49,370 --> 01:04:51,130
AdRoll inaonekana wewe juu ya meza zao.

1483
01:04:51,130 --> 01:04:52,115
Wao kupata cookie yako.

1484
01:04:52,115 --> 01:04:53,990
Matangazo kuwaambia
yao, nataka mtu

1485
01:04:53,990 --> 01:04:58,632
ambaye ni makamo,
Mtu 40 umri wa miaka, katika michezo.

1486
01:04:58,632 --> 01:05:01,590
Nao alama wewe katika idadi ya watu wale
na wao kuamua kama au

1487
01:05:01,590 --> 01:05:02,740
hiyo ni tangazo nzuri kwa ajili yenu.

1488
01:05:02,740 --> 01:05:10,330
>> Sasa wana SLA kwa
watoa matangazo yao

1489
01:05:10,330 --> 01:05:14,510
kutoa ndogo 10 millisecond
majibu juu ya kila ombi moja.

1490
01:05:14,510 --> 01:05:16,090
Hivyo wao ni kutumia Dynamo DB kwa hili.

1491
01:05:16,090 --> 01:05:18,131
Wao ni kupiga sisi
milioni maombi kwa pili.

1492
01:05:18,131 --> 01:05:21,120
Wao ni uwezo wa kufanya yote wao
lookups, triage data kwamba wote,

1493
01:05:21,120 --> 01:05:26,130
na kupata kwamba kuongeza kiungo nyuma na kwamba
watangazaji katika chini ya 10 milliseconds.

1494
01:05:26,130 --> 01:05:29,800
Ni kweli pretty phenomenal
utekelezaji waliyo nayo.

1495
01:05:29,800 --> 01:05:36,210
>> Haya guys actually--
ni haya guys.

1496
01:05:36,210 --> 01:05:38,010
Sina hakika kama ni guys haya.

1497
01:05:38,010 --> 01:05:40,127
Inaweza kuwa guys haya.

1498
01:05:40,127 --> 01:05:42,210
Kimsingi aliiambia us-- hapana, mimi
sidhani ilikuwa yao.

1499
01:05:42,210 --> 01:05:43,000
Nadhani ilikuwa ni mtu mwingine.

1500
01:05:43,000 --> 01:05:44,750
Nilikuwa kazi na
mteja kwamba aliniambia

1501
01:05:44,750 --> 01:05:47,040
kwamba sasa kwamba wameweza
wamekwenda Dynamo DB, wao uko

1502
01:05:47,040 --> 01:05:50,330
matumizi ya fedha zaidi juu ya vitafunio kwa
maendeleo ya timu yao kila mwezi

1503
01:05:50,330 --> 01:05:52,886
kuliko wao kutumia katika orodha yao.

1504
01:05:52,886 --> 01:05:54,760
Hivyo nitakupa
wazo la gharama za akiba

1505
01:05:54,760 --> 01:05:57,889
uweze kupata katika Dynamo DB ni kubwa.

1506
01:05:57,889 --> 01:05:59,430
Haki wote, dropcam ni kampuni nyingine.

1507
01:05:59,430 --> 01:06:02,138
Hizi guy aina of-- kama unadhani
ya biashara ya mambo, dropcam

1508
01:06:02,138 --> 01:06:05,150
kimsingi ni usalama wa internet video.

1509
01:06:05,150 --> 01:06:06,660
Kuweka kamera yako huko nje.

1510
01:06:06,660 --> 01:06:08,180
Kamera ina detector mwendo.

1511
01:06:08,180 --> 01:06:10,290
Mtu huja pamoja,
kuchochea cue uhakika.

1512
01:06:10,290 --> 01:06:13,540
Kamera kuanza kurekodi kwa muda mpaka
haina kuchunguza mwendo yoyote tena.

1513
01:06:13,540 --> 01:06:15,310
Unaweka kwamba video juu ya biashara ya.

1514
01:06:15,310 --> 01:06:19,800
>> Dropcam ilikuwa kampuni hiyo ni
kimsingi switched Dynamo DB

1515
01:06:19,800 --> 01:06:22,200
kwa sababu wao walikuwa wakikabiliwa
kubwa kuongezeka maumivu.

1516
01:06:22,200 --> 01:06:25,820
Na nini walituambia,
ghafla petabytes ya data.

1517
01:06:25,820 --> 01:06:28,070
Hawakuwa na wazo huduma zao
itakuwa hivyo mafanikio.

1518
01:06:28,070 --> 01:06:32,310
Zaidi inbound video ya YouTube
ni nini hawa guys ni kupata.

1519
01:06:32,310 --> 01:06:36,780
Wao kutumia DynamoDB kufuatilia yote
metadata wote pointi zao video muhimu.

1520
01:06:36,780 --> 01:06:40,282
>> Hivyo kuwa na S3 ndoo wao kushinikiza
zote mapacha mabaki katika.

1521
01:06:40,282 --> 01:06:41,990
Na kisha wana
Rekodi Dynamo DB kwamba

1522
01:06:41,990 --> 01:06:44,070
kuwaelekeza watu kwa vitu wale S3 tatu.

1523
01:06:44,070 --> 01:06:47,070
Wakati wao haja ya kuangalia video,
wao kuangalia juu rekodi katika Dynamo DB.

1524
01:06:47,070 --> 01:06:47,903
Wao bonyeza kiungo.

1525
01:06:47,903 --> 01:06:49,770
Wao kubomoa video kutoka S3.

1526
01:06:49,770 --> 01:06:51,590
Hivyo hiyo ni aina ya nini hii inaonekana kama.

1527
01:06:51,590 --> 01:06:53,580
Na hii ni moja kwa moja kutoka timu yao.

1528
01:06:53,580 --> 01:06:56,010
>> Dynamo DB inapunguza yao
wakati wa kujifungua kwa matukio video

1529
01:06:56,010 --> 01:06:57,590
kutoka sekunde tano hadi 10.

1530
01:06:57,590 --> 01:07:00,470
Katika miaka yao kimahusiano kuhifadhi,
walitumia una kwenda na kutekeleza

1531
01:07:00,470 --> 01:07:03,780
maswali mbalimbali tata kwa takwimu
nje ambayo video kubomoa,

1532
01:07:03,780 --> 01:07:06,690
kwa chini ya 50 milliseconds.

1533
01:07:06,690 --> 01:07:08,990
Hivyo ni ajabu, ajabu
utendaji ni kiasi gani

1534
01:07:08,990 --> 01:07:12,990
unaweza kupata wakati kuongeza na
tune orodha ya msingi

1535
01:07:12,990 --> 01:07:15,110
kusaidia upatikanaji mfano.

1536
01:07:15,110 --> 01:07:20,500
Halfbrick, haya guys, ni nini,
Matunda Ninja mimi nadhani ni jambo wao.

1537
01:07:20,500 --> 01:07:22,590
Hiyo anaendesha yote juu ya Dynamo DB.

1538
01:07:22,590 --> 01:07:26,810
Na guys haya, ni kubwa sana
timu ya maendeleo, maendeleo makubwa

1539
01:07:26,810 --> 01:07:27,670
duka.

1540
01:07:27,670 --> 01:07:29,364
>> Si nzuri ops timu.

1541
01:07:29,364 --> 01:07:31,280
Hawakuwa na mengi
ya rasilimali operesheni.

1542
01:07:31,280 --> 01:07:33,940
Walikuwa wanajitahidi kujaribu kuweka
maombi miundombinu yao juu

1543
01:07:33,940 --> 01:07:34,290
na kukimbia.

1544
01:07:34,290 --> 01:07:35,000
Walikuja kwetu.

1545
01:07:35,000 --> 01:07:36,251
Wao inaonekana katika kwamba Dynamo DB.

1546
01:07:36,251 --> 01:07:37,291
Walisema, hiyo ni kwa ajili yetu.

1547
01:07:37,291 --> 01:07:39,470
Wao kujengwa zima zao
maombi ya mfumo juu yake.

1548
01:07:39,470 --> 01:07:43,640
Baadhi ya maoni kwa kweli ni nzuri hapa
kutoka kwa timu juu ya uwezo wao

1549
01:07:43,640 --> 01:07:46,800
kwa sasa italenga katika kujenga
mchezo na si

1550
01:07:46,800 --> 01:07:49,010
kuwa na kudumisha
miundombinu, ambayo

1551
01:07:49,010 --> 01:07:51,910
ilikuwa kuwa kiasi kikubwa
ya uendeshaji kwa timu yao.

1552
01:07:51,910 --> 01:07:56,170
Hivyo hii ni kitu that--
kufaidika kwamba kupata kutoka Dynamo DB.

1553
01:07:56,170 --> 01:08:00,930
>> Haki wote, kuingia katika
data modeling hapa.

1554
01:08:00,930 --> 01:08:03,440
Na sisi aliyesema kidogo kuhusu
hii moja kwa moja, moja kwa wengi,

1555
01:08:03,440 --> 01:08:05,060
na wengi kwa mahusiano ya aina nyingi.

1556
01:08:05,060 --> 01:08:07,630
Na jinsi gani unaweza kudumisha wale walio katika Dynamo.

1557
01:08:07,630 --> 01:08:10,500
Katika Dynamo DB tunatumia
bahati, kwa ujumla kuzungumza,

1558
01:08:10,500 --> 01:08:12,910
na mzunguko wa data kutoka
ladha mmoja hadi mwingine.

1559
01:08:12,910 --> 01:08:15,210
Funguo hash, funguo mbalimbali, na bahati.

1560
01:08:15,210 --> 01:08:18,540
>> Katika hii hasa
mfano, kama nchi nyingi

1561
01:08:18,540 --> 01:08:23,802
una mahitaji ya leseni kwamba
tu leseni ya dereva mmoja kwa kila mtu.

1562
01:08:23,802 --> 01:08:26,510
Huwezi kwenda kupata mbili ya dereva
leseni katika jimbo la Boston.

1563
01:08:26,510 --> 01:08:27,500
Siwezi kufanya hivyo katika Texas.

1564
01:08:27,500 --> 01:08:28,708
Hiyo ni aina ya njia ni.

1565
01:08:28,708 --> 01:08:32,779
Na hivyo katika DMV, tuna lookups, sisi
wanataka kuangalia juu leseni ya dereva

1566
01:08:32,779 --> 01:08:35,180
na usalama wa jamii idadi.

1567
01:08:35,180 --> 01:08:39,990
Nataka kuangalia maelezo ya mtumiaji up
na leseni ya dereva idadi.

1568
01:08:39,990 --> 01:08:43,620
>> Hivyo tuwe na mtumiaji meza kwamba
ina hash muhimu juu ya idadi Serial,

1569
01:08:43,620 --> 01:08:47,830
au usalama wa jamii idadi, na
sifa mbalimbali inavyoelezwa kwenye kipengele.

1570
01:08:47,830 --> 01:08:49,859
Sasa juu ya meza mimi
aliweza kuainisha GSI kwamba

1571
01:08:49,859 --> 01:08:53,370
flips kwamba suala hilo anasema nataka
hash muhimu juu ya leseni na kisha

1572
01:08:53,370 --> 01:08:54,252
vitu vingine vyote.

1573
01:08:54,252 --> 01:08:57,210
Sasa kama nataka swala na kupata
leseni namba kwa wowote wa Jamii

1574
01:08:57,210 --> 01:08:59,609
Usalama idadi, siwezi
swala kuu meza.

1575
01:08:59,609 --> 01:09:02,130
>> Kama mimi nataka swala na nataka
kupata usalama wa jamii

1576
01:09:02,130 --> 01:09:05,735
idadi au sifa nyingine na
leseni namba, siwezi swala GSI.

1577
01:09:05,735 --> 01:09:08,689
Mfano kwamba ni kwamba moja
kwa uhusiano moja.

1578
01:09:08,689 --> 01:09:12,460
Tu GSI rahisi sana,
flip mambo hayo karibu.

1579
01:09:12,460 --> 01:09:13,979
Sasa, majadiliano juu ya moja kwa wengi.

1580
01:09:13,979 --> 01:09:16,450
Moja kwa wengi kimsingi
hash mbalimbali muhimu yako.

1581
01:09:16,450 --> 01:09:20,510
Ambapo sisi kupata mengi na hii
matumizi ya kesi ni kufuatilia data.

1582
01:09:20,510 --> 01:09:23,880
Kufuatilia data huja katika mara kwa mara
muda, kama biashara ya mambo.

1583
01:09:23,880 --> 01:09:26,890
Sisi daima kupata haya yote
Kumbukumbu kuja katika wakati wote.

1584
01:09:26,890 --> 01:09:31,420
>> Na nataka kupata masomo yote
kati ya kipindi cha muda fulani.

1585
01:09:31,420 --> 01:09:34,220
Ni swala la kawaida sana katika
miundombinu ya ufuatiliaji.

1586
01:09:34,220 --> 01:09:38,430
Njia ya kwenda juu ya hilo ni kupata
muundo rahisi meza, meza moja.

1587
01:09:38,430 --> 01:09:42,250
Mimi nimepata vipimo kifaa meza
na hash muhimu kwenye kifaa ID.

1588
01:09:42,250 --> 01:09:47,340
Na mimi kuwa na aina muhimu kwenye
timestamp, au katika kesi hiyo, Epic.

1589
01:09:47,340 --> 01:09:50,350
Na kwamba inaruhusu mimi nitafanya tata
maswali dhidi kuwa suala muhimu mbalimbali

1590
01:09:50,350 --> 01:09:54,950
na kurudi kumbukumbu hizo kwamba
ni jamaa na matokeo

1591
01:09:54,950 --> 01:09:56,310
kuweka kwamba mimi nina kuangalia kwa.

1592
01:09:56,310 --> 01:09:58,360
Na hujenga kwamba moja
kwa uhusiano wengi

1593
01:09:58,360 --> 01:10:02,340
ndani ya meza ya msingi kwa kutumia
hash muhimu, mbalimbali ya muundo muhimu.

1594
01:10:02,340 --> 01:10:04,600
>> Hivyo hiyo ni aina ya kujengwa
ndani ya meza katika Dynamo DB.

1595
01:10:04,600 --> 01:10:07,290
Wakati mimi kufafanua hash
na mbalimbali t meza, mimi nina

1596
01:10:07,290 --> 01:10:09,240
kufafanua moja kwa uhusiano wengi.

1597
01:10:09,240 --> 01:10:12,770
Ni uhusiano wa mzazi na mtoto.

1598
01:10:12,770 --> 01:10:14,620
>> Hebu majadiliano juu ya wengi
kwa mahusiano mengi.

1599
01:10:14,620 --> 01:10:19,170
Na kwa mfano fulani,
tena, tunakwenda kutumia GSI ya.

1600
01:10:19,170 --> 01:10:23,500
Na hebu majadiliano juu ya michezo ya kubahatisha
mazingira ambapo nina mtumiaji fulani.

1601
01:10:23,500 --> 01:10:26,500
Nataka kujua michezo yote
yeye kusajiliwa kwa au kucheza katika.

1602
01:10:26,500 --> 01:10:29,600
Na kwa mchezo huo, mimi
wanataka kupata watumiaji wote.

1603
01:10:29,600 --> 01:10:31,010
Hivyo ni jinsi gani mimi kufanya hivyo?

1604
01:10:31,010 --> 01:10:34,330
Yangu michezo mtumiaji meza, mimi nina kwenda
kuwa na hash muhimu ya mtumiaji ID

1605
01:10:34,330 --> 01:10:35,810
na mbalimbali muhimu ya mchezo.

1606
01:10:35,810 --> 01:10:37,810
>> Hivyo mtumiaji anaweza kuwa na michezo mbalimbali.

1607
01:10:37,810 --> 01:10:41,380
Ni moja kwa uhusiano kati ya wengi
user na michezo yeye anacheza.

1608
01:10:41,380 --> 01:10:43,410
Na kisha juu ya GSI,
Mimi itabidi flip kwamba karibu.

1609
01:10:43,410 --> 01:10:46,679
Mimi itabidi hash juu ya mchezo na
Mimi itabidi mbalimbali juu ya mtumiaji.

1610
01:10:46,679 --> 01:10:48,970
Hivyo kama nataka kupata zote
mchezo mtumiaji kucheza katika,

1611
01:10:48,970 --> 01:10:49,950
Mimi itabidi swala meza kuu.

1612
01:10:49,950 --> 01:10:52,699
Kama nataka kupata watumiaji wote
kwamba wanacheza mchezo fulani,

1613
01:10:52,699 --> 01:10:53,887
Mimi swala GSI.

1614
01:10:53,887 --> 01:10:54,970
Hivyo unaweza kuona jinsi sisi kufanya hivyo?

1615
01:10:54,970 --> 01:10:58,369
Kujenga hizi GSI ya kusaidia
matumizi ya kesi, maombi, upatikanaji

1616
01:10:58,369 --> 01:10:59,410
mfano, maombi.

1617
01:10:59,410 --> 01:11:01,440
>> Kama mimi haja ya swala juu ya
mwelekeo huu, hebu

1618
01:11:01,440 --> 01:11:03,500
mimi kuunda ripoti juu ya kwamba mwelekeo.

1619
01:11:03,500 --> 01:11:05,850
Kama sifanyi, Sijali.

1620
01:11:05,850 --> 01:11:09,060
Na kutegemea kesi ya matumizi, mimi
kuhitaji ripoti au nipate si.

1621
01:11:09,060 --> 01:11:12,390
Kama ni moja rahisi wengi,
meza kuu ni faini.

1622
01:11:12,390 --> 01:11:15,860
Kama mimi haja ya kufanya mingi
ya wengi, au mimi haja ya kufanya moja na wale,

1623
01:11:15,860 --> 01:11:18,390
basi labda sijui haja
kwa pili ripoti.

1624
01:11:18,390 --> 01:11:20,840
Kwa yote inategemea juu ya
nini mimi kujaribu kufanya

1625
01:11:20,840 --> 01:11:24,550
na nini mimi kujaribu kupata yametimia.

1626
01:11:24,550 --> 01:11:28,000
>> Pengine mimi si kwenda kutumia pia
muda mwingi kuzungumza juu ya hati.

1627
01:11:28,000 --> 01:11:31,460
Hii anapata kidogo, pengine,
zaidi kuliko tunahitaji kwenda katika.

1628
01:11:31,460 --> 01:11:33,710
Hebu majadiliano kidogo
kuhusu tajiri swala kujieleza.

1629
01:11:33,710 --> 01:11:37,831
Hivyo katika Dynamo DB tuna
uwezo wa kujenga

1630
01:11:37,831 --> 01:11:39,330
kile tunachokiita maneno makadirio.

1631
01:11:39,330 --> 01:11:42,660
Maneno makadirio ni tu
kuokota mashamba au maadili

1632
01:11:42,660 --> 01:11:44,290
kwamba unataka kuonyesha.

1633
01:11:44,290 --> 01:11:46,000
OK, hivyo mimi kufanya uteuzi.

1634
01:11:46,000 --> 01:11:48,010
Mimi kufanya swala dhidi ya Dynamo DB.

1635
01:11:48,010 --> 01:11:51,730
Na mimi kusema, unajua nini, show
mimi tu kitaalam nyota tano

1636
01:11:51,730 --> 01:11:54,544
kwa bidhaa fulani.

1637
01:11:54,544 --> 01:11:55,710
Hivyo hiyo ni yote nataka kuona.

1638
01:11:55,710 --> 01:11:57,320
Sitaki kuona yote
sifa nyingine ya mstari,

1639
01:11:57,320 --> 01:11:58,319
Mimi nataka tu kuona hii.

1640
01:11:58,319 --> 01:12:01,209
Ni kama tu katika SQL wakati
kusema kuchagua nyota au kutoka meza,

1641
01:12:01,209 --> 01:12:02,000
kupata kila kitu.

1642
01:12:02,000 --> 01:12:05,450
Wakati mimi kusema kuchagua jina kutoka
meza, mimi tu kupata sifa moja.

1643
01:12:05,450 --> 01:12:09,070
Ni aina hiyo ya kitu katika
Dynamo DB au databaser nyingine NoSQL.

1644
01:12:09,070 --> 01:12:14,510
Kuchuja maneno naomba
kimsingi kukata matokeo kuketi.

1645
01:12:14,510 --> 01:12:15,540
Hivyo mimi kufanya swala.

1646
01:12:15,540 --> 01:12:17,260
Swala wapate kurejea tena kwa vitu 500.

1647
01:12:17,260 --> 01:12:20,255
Lakini mimi tu wanataka vitu kuwa
na sifa kwamba anasema hii.

1648
01:12:20,255 --> 01:12:23,380
Sawa, hivyo hebu kuchuja vitu hivyo
kwamba si mechi kwamba swala fulani.

1649
01:12:23,380 --> 01:12:25,540
Hivyo tuna maneno filter.

1650
01:12:25,540 --> 01:12:28,310
>> Kuchuja maneno Unaweza
kuwa na kukimbia juu ya sifa yoyote.

1651
01:12:28,310 --> 01:12:30,260
Wao siyo kama maswali mbalimbali.

1652
01:12:30,260 --> 01:12:32,690
Kuongeza maswali ni kuchagua zaidi.

1653
01:12:32,690 --> 01:12:36,470
Maswali kuchuja zinahitaji niende
kupata matokeo nzima kuweka na kisha

1654
01:12:36,470 --> 01:12:39,170
kuchonga nje data Sitaki.

1655
01:12:39,170 --> 01:12:40,660
Nini hilo ni muhimu?

1656
01:12:40,660 --> 01:12:42,770
Kwa sababu mimi kusoma yote.

1657
01:12:42,770 --> 01:12:46,597
Katika swala, mimi nina kwenda kusoma na
ni kwenda kuwa kubwa kuhusu data.

1658
01:12:46,597 --> 01:12:48,430
Na kisha mimi nina kwenda kwa
kuchonga nje kile haja.

1659
01:12:48,430 --> 01:12:52,080
Na kama mimi nina tu kuchora nje
michache ya safu, basi hiyo ni sawa.

1660
01:12:52,080 --> 01:12:53,620
Siyo ufanisi.

1661
01:12:53,620 --> 01:12:57,800
>> Lakini kama mimi nina kusoma rundo zima la
data, tu kuchonga nje bidhaa moja,

1662
01:12:57,800 --> 01:13:01,490
basi mimi nina kwenda kuwa bora
mbali kwa kutumia swala mbalimbali,

1663
01:13:01,490 --> 01:13:03,030
kwa sababu ni mengi zaidi kuwachagua.

1664
01:13:03,030 --> 01:13:06,330
Ni kwenda kuokoa yangu mengi ya
fedha, kwa sababu mimi kulipa kwa kuwa kusoma.

1665
01:13:06,330 --> 01:13:10,430
Ambapo matokeo ya kuwa anakuja nyuma
kuvuka kwamba waya inaweza kuwa ndogo,

1666
01:13:10,430 --> 01:13:11,890
lakini mimi nina kulipa kwa kusoma.

1667
01:13:11,890 --> 01:13:14,340
Hivyo kuelewa jinsi
wewe ni kupata data.

1668
01:13:14,340 --> 01:13:16,420
Hiyo ni muhimu sana katika Dynamo DB.

1669
01:13:16,420 --> 01:13:19,710
>> Maneno masharti, hii ni nini
unaweza wito matumaini locking.

1670
01:13:19,710 --> 01:13:28,470
Mwisho IF lipo, au kama thamani hii
ni sawa na kile bayana.

1671
01:13:28,470 --> 01:13:31,494
Na kama nina muda wa stempu kwenye
rekodi, nipate kusoma data.

1672
01:13:31,494 --> 01:13:32,535
Nipate mabadiliko ya data hiyo.

1673
01:13:32,535 --> 01:13:35,030
Nipate kwenda kuandika kwamba
data ya nyuma na database.

1674
01:13:35,030 --> 01:13:38,100
Kama mtu imebadilika rekodi,
timestamp inaweza kuwa iliyopita.

1675
01:13:38,100 --> 01:13:40,370
Na kwa njia hiyo zangu masharti
update naweza kusema update

1676
01:13:40,370 --> 01:13:42,340
kama timestamp sawa na hii.

1677
01:13:42,340 --> 01:13:46,290
Au update kushindwa kwa sababu mtu
updated rekodi katika huo huo.

1678
01:13:46,290 --> 01:13:48,290
>> Hiyo ni nini sisi kuwaita matumaini locking.

1679
01:13:48,290 --> 01:13:50,670
Ina maana kwamba mtu
wanaweza kuja katika na mabadiliko hayo,

1680
01:13:50,670 --> 01:13:53,100
na mimi nina kwenda kuchunguza hayo
wakati mimi kurejea kuandika.

1681
01:13:53,100 --> 01:13:56,106
Na kisha mimi kweli anaweza kusoma kwamba
data na kusema, loo, yeye iliyopita hii.

1682
01:13:56,106 --> 01:13:57,230
Mimi haja ya akaunti kwa ajili ya jambo hilo.

1683
01:13:57,230 --> 01:14:00,490
Na siwezi kubadili data katika wangu
kurekodi na kuomba sasisho mwingine.

1684
01:14:00,490 --> 01:14:04,330
Hivyo unaweza kupata wale Unaozidi
updates kutokea kati ya wakati

1685
01:14:04,330 --> 01:14:08,740
kwamba kusoma data na
muda unaweza kuandika data.

1686
01:14:08,740 --> 01:14:11,520
>> Watazamaji: Na filter
kujieleza kwa kweli ina maana si

1687
01:14:11,520 --> 01:14:13,020
katika idadi au not--

1688
01:14:13,020 --> 01:14:14,316
>> [INTERPOSING SAUTI]

1689
01:14:14,316 --> 01:14:16,232
RICK Houlihan: sipendi
kupata sana katika hili.

1690
01:14:16,232 --> 01:14:17,700
Hii ni keyword zimehifadhiwa.

1691
01:14:17,700 --> 01:14:20,130
Chupa mtazamo ni akiba
Keyword katika Dynamo DB.

1692
01:14:20,130 --> 01:14:24,500
Kila database ina yake mwenyewe zimehifadhiwa
majina ya makusanyo huwezi kutumia.

1693
01:14:24,500 --> 01:14:27,240
Dynamo DB, kama wewe taja
chupa mbele ya hii,

1694
01:14:27,240 --> 01:14:29,310
unaweza kufafanua majina hayo hadi hapo juu.

1695
01:14:29,310 --> 01:14:31,840
Hii ni thamani inatazamwa.

1696
01:14:31,840 --> 01:14:34,880
Ni pengine si syntax bora kwa
kuwa hadi pale kwa mjadala huu,

1697
01:14:34,880 --> 01:14:38,090
kwa sababu anapata katika baadhi real--
Napenda wamekuwa wakizungumza zaidi

1698
01:14:38,090 --> 01:14:41,360
juu ya hilo kwa undani zaidi.

1699
01:14:41,360 --> 01:14:46,130
>> Lakini inatosha kusema, hii inaweza
kuwa swala Scan ambako views--

1700
01:14:46,130 --> 01:14:50,190
wala paundi maoni ni mkubwa kuliko 10.

1701
01:14:50,190 --> 01:14:54,660
Ni thamani ya namba, ndiyo.

1702
01:14:54,660 --> 01:14:57,322
Kama unataka, tunaweza kuongea kuhusu
kwamba baada ya majadiliano.

1703
01:14:57,322 --> 01:15:00,030
Haki wote, hivyo sisi ni kuingia katika
baadhi ya matukio katika njia bora

1704
01:15:00,030 --> 01:15:02,000
ambapo sisi ni kwenda kuzungumza
kuhusu baadhi ya programu hapa.

1705
01:15:02,000 --> 01:15:03,810
Je, ni kesi kwa Dynamo DB matumizi.

1706
01:15:03,810 --> 01:15:06,120
Je, ni kubuni
mwelekeo katika Dynamo DB.

1707
01:15:06,120 --> 01:15:09,110
>> Na moja ya kwanza tunakwenda
majadiliano juu ni biashara ya mambo.

1708
01:15:09,110 --> 01:15:15,010
Hivyo sisi kupata mengi of-- mimi nadhani,
ni nini it-- zaidi ya 50%

1709
01:15:15,010 --> 01:15:19,370
ya trafiki kwenye mtandao siku hizi
ni kweli yanayotokana na mashine,

1710
01:15:19,370 --> 01:15:21,930
michakato automatiska, si na wanadamu.

1711
01:15:21,930 --> 01:15:25,140
I mean jambo hili jambo hili kwamba
wewe kubeba kuzunguka katika mfuko wako,

1712
01:15:25,140 --> 01:15:28,840
ni kiasi gani data kuwa kwamba jambo ni
kweli kutuma kuzunguka bila wewe

1713
01:15:28,840 --> 01:15:30,550
kujua ni ajabu kabisa.

1714
01:15:30,550 --> 01:15:34,970
Eneo lako, maelezo
kuhusu jinsi ya kufunga wewe ni kwenda.

1715
01:15:34,970 --> 01:15:38,400
Je unafikiri Google Maps kazi
wakati wao kukuambia nini trafiki ni.

1716
01:15:38,400 --> 01:15:41,275
Ni kwa sababu kuna mamilioni na
mamilioni ya watu kuendesha gari karibu

1717
01:15:41,275 --> 01:15:44,667
kwa simu kwamba ni kutuma
data kila mahali wakati wote.

1718
01:15:44,667 --> 01:15:46,500
Hivyo moja ya mambo
kuhusu aina hii ya data

1719
01:15:46,500 --> 01:15:50,980
kwamba anakuja katika, kufuatilia data, kuingia
data, data mfululizo wakati, ni ni

1720
01:15:50,980 --> 01:15:53,540
Kwa kawaida kuvutia tu
kwa muda kidogo.

1721
01:15:53,540 --> 01:15:55,580
Baada ya muda huo, ni
si hivyo kuvutia.

1722
01:15:55,580 --> 01:15:58,390
Hivyo kuongelea, si lazima
meza wale kukua bila mipaka.

1723
01:15:58,390 --> 01:16:03,410
Wazo hapa ni kwamba labda mimi nimepata 24
masaa ya thamani ya matukio katika meza yangu moto.

1724
01:16:03,410 --> 01:16:06,160
Na kwamba meza moto ni kwenda kuwa
provisioned kwa kiwango cha juu sana,

1725
01:16:06,160 --> 01:16:07,950
kwa sababu ni kuchukua mengi ya data.

1726
01:16:07,950 --> 01:16:10,920
Ni kuchukua mengi ya data
katika na mimi nina kusoma ni mengi.

1727
01:16:10,920 --> 01:16:14,560
Mimi nimepata mengi ya uendeshaji
maswali mbio dhidi ya data hizo.

1728
01:16:14,560 --> 01:16:18,120
>> Baada ya masaa 24, hey, wewe
kujua nini, sijali.

1729
01:16:18,120 --> 01:16:21,150
Hivyo labda kila usiku wa manane mimi roll
meza yangu juu ya meza mpya

1730
01:16:21,150 --> 01:16:22,430
na mimi deprovision meza hii.

1731
01:16:22,430 --> 01:16:26,440
Na mimi itabidi kuchukua RCU na
Masaa WCU ya chini kwa sababu 24 baadaye

1732
01:16:26,440 --> 01:16:28,630
Mimi si mbio kama wengi
maswali dhidi data hizo.

1733
01:16:28,630 --> 01:16:30,200
Hivyo nina kwenda kuokoa fedha.

1734
01:16:30,200 --> 01:16:32,940
Na labda siku 30 baadaye mimi si
hata haja ya huduma kuhusu hayo yote.

1735
01:16:32,940 --> 01:16:35,020
Mimi naweza kuchukua WCU ya
njia yote chini ya moja,

1736
01:16:35,020 --> 01:16:36,990
kwa sababu unajua nini, ni
kamwe kwenda kupata kuandikwa kwa.

1737
01:16:36,990 --> 01:16:38,300
Data ni umri wa siku 30.

1738
01:16:38,300 --> 01:16:40,000
Ni kamwe mabadiliko.

1739
01:16:40,000 --> 01:16:44,200
>> Na ni karibu kamwe kwenda kupata kusoma,
hivyo hebu tu kuchukua kwamba RCU chini ya 10.

1740
01:16:44,200 --> 01:16:49,372
Na mimi nina kuokoa tani ya fedha juu ya hili
data, na tu kulipa kwa ajili ya data zangu moto.

1741
01:16:49,372 --> 01:16:52,330
Hivyo hiyo ni jambo muhimu kwa kuangalia
katika wakati ukiangalia mfululizo wakati

1742
01:16:52,330 --> 01:16:54,716
data akija kwa kiasi.

1743
01:16:54,716 --> 01:16:55,590
Hizi ni mikakati.

1744
01:16:55,590 --> 01:16:58,010
Sasa, mimi naweza tu basi ni
wote kwenda meza moja

1745
01:16:58,010 --> 01:16:59,461
na tu basi meza kwamba kukua.

1746
01:16:59,461 --> 01:17:01,460
Hatimaye, Mimi nina kwenda
ona masuala ya utendaji.

1747
01:17:01,460 --> 01:17:04,060
Mimi nina kwenda kuanza archive
baadhi ya kwamba data mbali meza,

1748
01:17:04,060 --> 01:17:04,720
kile si.

1749
01:17:04,720 --> 01:17:07,010
>> Hebu bora zaidi
kubuni maombi yako

1750
01:17:07,010 --> 01:17:08,900
ili uweze kufanya kazi kwa njia hii haki.

1751
01:17:08,900 --> 01:17:11,460
Hivyo ni tu moja kwa moja
katika maombi kificho.

1752
01:17:11,460 --> 01:17:13,580
Usiku wa manane kila usiku
Rolls meza.

1753
01:17:13,580 --> 01:17:17,170
Labda kile haja ni sliding
dirisha la masaa 24 ya data.

1754
01:17:17,170 --> 01:17:20,277
Kisha mara kwa mara mimi nina
wito data mbali ya meza.

1755
01:17:20,277 --> 01:17:22,360
Mimi trimming kwa
Cron na mimi nina kuweka ni

1756
01:17:22,360 --> 01:17:24,160
kwenye mbao hizo mengine,
chochote unahitaji.

1757
01:17:24,160 --> 01:17:25,940
Hivyo kama rollover kazi, hiyo ni kubwa.

1758
01:17:25,940 --> 01:17:27,080
Kama siyo, trim yake.

1759
01:17:27,080 --> 01:17:29,640
Lakini hebu kuendelea kuwa data moto
mbali na data baridi yako.

1760
01:17:29,640 --> 01:17:32,535
Ni itabidi kuokoa fedha nyingi na
kufanya meza yako zaidi maonyesho.

1761
01:17:32,535 --> 01:17:35,960

1762
01:17:35,960 --> 01:17:38,210
Hivyo jambo la pili tutaweza majadiliano
kuhusu ni bidhaa catalog.

1763
01:17:38,210 --> 01:17:42,000
Bidhaa catalog ni
matumizi pretty kawaida kesi.

1764
01:17:42,000 --> 01:17:46,600
Hii ni kweli mfano kawaida sana
kwamba tutaweza kuona katika vitu mbalimbali.

1765
01:17:46,600 --> 01:17:48,870
Unajua, Twitter kwa
mfano, tweet moto.

1766
01:17:48,870 --> 01:17:51,280
Kila mtu kuja na
grabbing kwamba tweet.

1767
01:17:51,280 --> 01:17:52,680
Bidhaa catalog, I got kuuza.

1768
01:17:52,680 --> 01:17:54,120
I got kuuza moto.

1769
01:17:54,120 --> 01:17:57,277
I got 70,000 maombi kwa
kuja mara ya pili kwa bidhaa

1770
01:17:57,277 --> 01:17:58,860
maelezo kutoka katika bidhaa yangu catalog.

1771
01:17:58,860 --> 01:18:02,384
Tunaona hii juu ya rejareja
operesheni kidogo kabisa.

1772
01:18:02,384 --> 01:18:03,550
Hivyo ni jinsi gani sisi kukabiliana na kwamba?

1773
01:18:03,550 --> 01:18:04,924
Hakuna njia ya kukabiliana na kwamba.

1774
01:18:04,924 --> 01:18:07,110
Watumiaji wangu wote wanataka kuona
kipande kimoja cha data.

1775
01:18:07,110 --> 01:18:09,410
Re ni kuja katika, Sanjari.

1776
01:18:09,410 --> 01:18:11,920
Na wao ni wote kufanya maombi
kwa kipande kimoja cha data.

1777
01:18:11,920 --> 01:18:16,240
Hii inanipa kwamba moto muhimu ili nyekundu kubwa
mstari kwenye chati yangu kwamba sisi si kama.

1778
01:18:16,240 --> 01:18:17,720
Na kwamba ni nini kwamba inaonekana kama.

1779
01:18:17,720 --> 01:18:22,290
Hivyo katika nafasi yangu muhimu mimi nina kupata
hammered katika vitu kuuza.

1780
01:18:22,290 --> 01:18:24,070
Mimi nina kupata kitu mahali popote.

1781
01:18:24,070 --> 01:18:26,050
>> Je, mimi kuondokana na tatizo hili?

1782
01:18:26,050 --> 01:18:28,410
Naam, sisi kupunguza huu kwa cache.

1783
01:18:28,410 --> 01:18:33,630
Cache, kuweka kimsingi katika-kumbukumbu
kuhesabu mbele ya database.

1784
01:18:33,630 --> 01:18:37,260
Tumeweza
[Inaudible] cache, jinsi gani

1785
01:18:37,260 --> 01:18:40,260
Unaweza kuanzisha cache yako mwenyewe, [inaudible]
cache [? d,?] chochote unataka.

1786
01:18:40,260 --> 01:18:42,220
Kuweka kwamba up mbele ya database.

1787
01:18:42,220 --> 01:18:47,250
Na kwa njia hiyo unaweza kuhifadhi data kwamba
kutoka kwa wale funguo moto up kwa kuwa cache

1788
01:18:47,250 --> 01:18:49,390
nafasi na kusoma kwa njia ya kashe.

1789
01:18:49,390 --> 01:18:51,962
>> Na kisha zaidi ya wasomaji yako
kuanza kuangalia kama hii.

1790
01:18:51,962 --> 01:18:54,920
I got zote hizi cache hits hapa
na mimi got chochote kinachoendelea hapa chini

1791
01:18:54,920 --> 01:18:59,330
kwa sababu database ni ameketi nyuma
cache na wasomaji kamwe kuja kwa njia ya.

1792
01:18:59,330 --> 01:19:02,520
Kama mimi kubadili data katika
Mbegu, nina update cache.

1793
01:19:02,520 --> 01:19:04,360
Tunaweza kutumia kitu
kama steams kufanya hivyo.

1794
01:19:04,360 --> 01:19:07,360
Na mimi itabidi kueleza jinsi kazi.

1795
01:19:07,360 --> 01:19:09,060
Haki wote, ujumbe.

1796
01:19:09,060 --> 01:19:11,180
Barua pepe, sisi wote kutumia barua pepe.

1797
01:19:11,180 --> 01:19:12,540
>> Huu ni mfano nzuri sana.

1798
01:19:12,540 --> 01:19:14,950
Sisi tumepewa baadhi ya aina ya ujumbe meza.

1799
01:19:14,950 --> 01:19:17,040
Na tulipata Inbox na toezi.

1800
01:19:17,040 --> 01:19:19,760
Hii ni nini SQL ingekuwa
kuangalia kama kujenga kwamba Inbox.

1801
01:19:19,760 --> 01:19:23,350
Sisi aina ya kutumia aina hiyo
ya mkakati wa kutumia GSI wa, GSI ya

1802
01:19:23,350 --> 01:19:25,320
kwa Inbox yangu na toezi yangu.

1803
01:19:25,320 --> 01:19:27,600
Hivyo mimi got ujumbe mbichi kuja
ndani ya meza yangu ujumbe.

1804
01:19:27,600 --> 01:19:30,194
Na njia ya kwanza kwa hii
inaweza kuwa, kusema, sawa, hakuna tatizo.

1805
01:19:30,194 --> 01:19:31,110
Mimi nimepata ujumbe ghafi.

1806
01:19:31,110 --> 01:19:33,710
Ujumbe kuja [inaudible],
Ujumbe ID, kwamba ni kubwa.

1807
01:19:33,710 --> 01:19:35,070
Hiyo ni yangu hash kipekee.

1808
01:19:35,070 --> 01:19:38,280
Mimi nina kwenda kujenga mbili GSI, mmoja
kwa Inbox yangu, moja kwa toezi yangu.

1809
01:19:38,280 --> 01:19:40,530
Na jambo la kwanza mimi itabidi kufanya
ni mimi itabidi kusema hash muhimu yangu ni

1810
01:19:40,530 --> 01:19:43,310
kwenda kuwa mpokeaji na
Mimi nina kwenda kupanga tarehe.

1811
01:19:43,310 --> 01:19:44,220
Hii ni ajabu.

1812
01:19:44,220 --> 01:19:45,890
I got maoni yangu nzuri hapa.

1813
01:19:45,890 --> 01:19:47,780
Lakini kuna suala kidogo hapa.

1814
01:19:47,780 --> 01:19:50,891
Na wewe kukimbia katika hii katika
databaser kimahusiano pia.

1815
01:19:50,891 --> 01:19:52,390
Walitoa wito wima partitioning.

1816
01:19:52,390 --> 01:19:55,840
Unataka kuweka data yako kubwa
mbali na data yako kidogo.

1817
01:19:55,840 --> 01:20:00,470
>> Na sababu ni kwa nini ni kwa sababu mimi gotta
kwenda kusoma vitu ya kupata sifa.

1818
01:20:00,470 --> 01:20:05,570
Na kama miili wangu wote ni juu ya hapa,
kisha kusoma vitu chache tu

1819
01:20:05,570 --> 01:20:08,560
kama mwili wangu urefu ni
wastani wa 256 kilobytes kila,

1820
01:20:08,560 --> 01:20:10,991
math anapata pretty mbaya.

1821
01:20:10,991 --> 01:20:12,490
Hivyo kusema nataka kusoma Inbox Daudi.

1822
01:20:12,490 --> 01:20:14,520
Inbox Daudi ana vitu 50.

1823
01:20:14,520 --> 01:20:17,880
Wastani na ukubwa ni 256 kilobytes.

1824
01:20:17,880 --> 01:20:21,730
Hapa ni kubadilika uwiano wangu
kwa RCU ni kilobytes nne.

1825
01:20:21,730 --> 01:20:24,450
>> OK, hebu kwenda kwa
Hatimaye thabiti anasoma.

1826
01:20:24,450 --> 01:20:28,640
Mimi bado kula 1600 RCU ya
tu kusoma Inbox Daudi.

1827
01:20:28,640 --> 01:20:29,950
Ouch.

1828
01:20:29,950 --> 01:20:31,980
Sawa, sasa hebu fikiria
kuhusu jinsi programu kazi.

1829
01:20:31,980 --> 01:20:35,340
Kama mimi niko katika programu email na
Mimi nina kuangalia Inbox yangu,

1830
01:20:35,340 --> 01:20:39,680
na mimi kuangalia mwili wa kila ujumbe,
hapana, mimi nina kuangalia muhtasari.

1831
01:20:39,680 --> 01:20:41,850
Mimi nina kuangalia tu headers.

1832
01:20:41,850 --> 01:20:46,310
Basi hebu kujenga mfumo meza
kwamba inaonekana zaidi kama hiyo.

1833
01:20:46,310 --> 01:20:49,470
>> Hivyo hapa ni maelezo
kwamba workflow yangu mahitaji.

1834
01:20:49,470 --> 01:20:50,890
Ni katika Inbox yangu GSI.

1835
01:20:50,890 --> 01:20:53,800
Ni tarehe, mtumaji,
somo, na kisha

1836
01:20:53,800 --> 01:20:56,790
Ujumbe kitambulisho, ambayo pointi
nyuma ya meza ujumbe

1837
01:20:56,790 --> 01:20:57,850
ambapo naweza kupata mwili.

1838
01:20:57,850 --> 01:21:01,260

1839
01:21:01,260 --> 01:21:04,420
Naam, haya itakuwa vitambulisho rekodi.

1840
01:21:04,420 --> 01:21:09,850
Wangekuwa uhakika nyuma
Vitambulisho vya bidhaa kwenye meza Dynamo DB.

1841
01:21:09,850 --> 01:21:12,220
Kila ripoti daima creates--
daima ina bidhaa

1842
01:21:12,220 --> 01:21:15,750
ID kama sehemu of-- kwamba
kuja na ripoti.

1843
01:21:15,750 --> 01:21:17,414
>> Sawa.

1844
01:21:17,414 --> 01:21:19,080
Watazamaji: Ni anaelezea ni ambapo ni kuhifadhiwa?

1845
01:21:19,080 --> 01:21:21,420
RICK Houlihan: Ndiyo, ni anaelezea
exactly-- kwamba ni nini hasa ni gani.

1846
01:21:21,420 --> 01:21:22,644
Inasema hapa ni re rekodi yangu.

1847
01:21:22,644 --> 01:21:24,310
Na kutakuwa na uhakika nyuma ya re rekodi yangu.

1848
01:21:24,310 --> 01:21:26,460
Hasa.

1849
01:21:26,460 --> 01:21:29,490
OK, hivyo sasa Inbox yangu ni
kweli ndogo sana.

1850
01:21:29,490 --> 01:21:32,210
Na hii kwa kweli inasaidia
workflow ya programu ya barua pepe.

1851
01:21:32,210 --> 01:21:34,230
Hivyo Inbox yangu, mimi click.

1852
01:21:34,230 --> 01:21:38,160
Mimi kwenda pamoja na mimi click kwenye ujumbe,
hiyo ni wakati mimi haja ya kwenda kupata mwili,

1853
01:21:38,160 --> 01:21:40,180
kwa sababu mimi naenda
kwenda mtazamo tofauti.

1854
01:21:40,180 --> 01:21:43,870
Hivyo kama unadhani kuhusu MVC aina ya
mfumo, mfano mtazamo mtawala.

1855
01:21:43,870 --> 01:21:46,120
>> Mfano ina
data kwamba mahitaji mtazamo

1856
01:21:46,120 --> 01:21:48,130
na mtawala interacts na.

1857
01:21:48,130 --> 01:21:51,670
Wakati mimi kubadili sura, wakati
Mimi kubadili mtazamo,

1858
01:21:51,670 --> 01:21:55,080
ni sawa na kwenda nyuma ya
server na repopulate mfano,

1859
01:21:55,080 --> 01:21:56,860
kwa sababu hiyo ndiyo user anatarajia.

1860
01:21:56,860 --> 01:22:00,530
Wakati wao kubadilisha maoni, kwamba wakati
tunaweza kurudi nyuma na database.

1861
01:22:00,530 --> 01:22:02,480
Hivyo barua pepe, click.

1862
01:22:02,480 --> 01:22:03,710
Mimi nina kuangalia kwa mwili.

1863
01:22:03,710 --> 01:22:04,330
Raundi ya safari.

1864
01:22:04,330 --> 01:22:05,680
Kwenda kupata mwili.

1865
01:22:05,680 --> 01:22:06,950
>> Mimi kusoma data mengi kidogo.

1866
01:22:06,950 --> 01:22:09,960
Mimi nina kusoma miili tu kwamba
David mahitaji wakati yeye mahitaji yao.

1867
01:22:09,960 --> 01:22:14,230
Na mimi si kuchoma katika 1600
RCU ya tu kuonyesha Inbox yake.

1868
01:22:14,230 --> 01:22:17,670
Hivyo sasa that-- hii ni njia
kuwa LSI au GSI-- Samahani,

1869
01:22:17,670 --> 01:22:19,900
GSI, ingekuwa kazi nje.

1870
01:22:19,900 --> 01:22:25,450
Sisi tumepewa hash yetu juu ya mpokeaji.

1871
01:22:25,450 --> 01:22:27,030
Sisi tumepewa mbalimbali muhimu tarehe.

1872
01:22:27,030 --> 01:22:31,380
Na sisi tumepewa sifa makadirio
kuwa tunahitaji tu kusaidia maoni.

1873
01:22:31,380 --> 01:22:34,300
>> Sisi mzunguko kwamba kwa toezi.

1874
01:22:34,300 --> 01:22:35,770
Hash juu ya mtumaji.

1875
01:22:35,770 --> 01:22:39,612
Na kwa asili, tuna
nzuri sana, mtazamo safi.

1876
01:22:39,612 --> 01:22:41,570
Na ni basically-- sisi
kuwa ujumbe huu mzuri

1877
01:22:41,570 --> 01:22:45,870
meza hiyo kuwa kuenea vizuri kwa sababu
ni hash tu, heshi ujumbe ID.

1878
01:22:45,870 --> 01:22:51,750
Na tuna bahati mawili ambayo
ni kupokezana mbali ya meza hiyo.

1879
01:22:51,750 --> 01:22:57,411
Haki wote, hivyo Wazo hapa ni kufanya si
kuweka data kubwa na hii data dogo

1880
01:22:57,411 --> 01:22:57,910
pamoja.

1881
01:22:57,910 --> 01:23:00,700
Kuigawa wima,
kuigawa meza hizo.

1882
01:23:00,700 --> 01:23:03,150
Je, si kusoma data huna kwa.

1883
01:23:03,150 --> 01:23:04,850
Haki wote, michezo ya kubahatisha.

1884
01:23:04,850 --> 01:23:06,990
Sote kama michezo.

1885
01:23:06,990 --> 01:23:10,902
Angalau mimi kama michezo wakati huo.

1886
01:23:10,902 --> 01:23:12,735
Hivyo baadhi ya mambo
kwamba sisi kukabiliana na wakati

1887
01:23:12,735 --> 01:23:14,193
sisi ni kufikiri kuhusu michezo ya kubahatisha, sawa?

1888
01:23:14,193 --> 01:23:16,999
Michezo ya kubahatisha siku hizi, hasa mkononi
michezo ya kubahatisha, ni wote kuhusu kufikiri.

1889
01:23:16,999 --> 01:23:19,540
Na mimi nina kwenda kwa mzunguko hapa
kidogo mbali na DynamoDB.

1890
01:23:19,540 --> 01:23:21,373
Mimi nina kwenda kuleta katika
baadhi ya majadiliano

1891
01:23:21,373 --> 01:23:24,240
kuzunguka baadhi ya
AWS teknolojia nyingine.

1892
01:23:24,240 --> 01:23:28,930
>> Lakini wazo kuhusu michezo ya kubahatisha ni kufikiri
kuhusu katika suala la APIs, APIs kwamba ni,

1893
01:23:28,930 --> 01:23:31,730
kwa ujumla kuzungumza, HTTP na JSON.

1894
01:23:31,730 --> 01:23:34,550
Ni jinsi mkononi aina ya michezo
kuingiliana na kuishia zao nyuma.

1895
01:23:34,550 --> 01:23:35,850
Wao kufanya JSON posting.

1896
01:23:35,850 --> 01:23:40,660
Wao kupata data, na ni wote,
kwa ujumla kuzungumza, katika APIs nzuri JSON.

1897
01:23:40,660 --> 01:23:44,950
>> Mambo kama kupata marafiki, kupata
data leaderboard, kubadilishana,

1898
01:23:44,950 --> 01:23:47,699
user yanayoletwa,
kushinikiza nyuma hadi mfumo,

1899
01:23:47,699 --> 01:23:49,740
hizi ni aina ya mambo
kwamba sisi ni kwenda kufanya.

1900
01:23:49,740 --> 01:23:52,542
Mapacha mali data, data hii
wanaweza kukaa katika database.

1901
01:23:52,542 --> 01:23:54,250
Hii inaweza kukaa katika
kitu duka, sawa?

1902
01:23:54,250 --> 01:23:56,541
Lakini orodha ni kwenda
kuishia kumwambia mfumo,

1903
01:23:56,541 --> 01:23:59,140
kuwaambia maombi
wapi pa kwenda kupata.

1904
01:23:59,140 --> 01:24:03,550
Na inevitably, multiplayer
watumishi, nyuma mwisho miundombinu,

1905
01:24:03,550 --> 01:24:06,180
na iliyoundwa kwa ajili ya
upatikanaji na scalability.

1906
01:24:06,180 --> 01:24:09,400
Hivyo haya ni mambo ambayo sisi wote wanataka
katika michezo ya kubahatisha miundombinu leo.

1907
01:24:09,400 --> 01:24:12,160
>> Basi hebu tuangalie
nini kwamba inaonekana kama.

1908
01:24:12,160 --> 01:24:16,070
Got msingi nyuma mwisho,
rahisi sana.

1909
01:24:16,070 --> 01:24:19,880
Sisi tumepewa mfumo hapa kwa
kanda nyingi upatikanaji.

1910
01:24:19,880 --> 01:24:23,780
Kuongelea AZS kama being-- kufikiri
wao kama tofauti vituo vya data.

1911
01:24:23,780 --> 01:24:26,040
Kituo cha data zaidi ya moja
per AZ, lakini hiyo ni sawa,

1912
01:24:26,040 --> 01:24:28,831
tu kufikiri wao kama data tofauti
Vituo kwamba ni kijiografia

1913
01:24:28,831 --> 01:24:30,090
na kosa pekee.

1914
01:24:30,090 --> 01:24:32,172
>> Tunakwenda kuwa na
wanandoa EC2 matukio.

1915
01:24:32,172 --> 01:24:33,880
Tunakwenda kuwa na
baadhi nyuma mwisho server.

1916
01:24:33,880 --> 01:24:35,800
Labda kama wewe ni urithi
usanifu, tuko

1917
01:24:35,800 --> 01:24:38,920
kutumia kile tunachokiita RDS,
kimahusiano huduma database.

1918
01:24:38,920 --> 01:24:42,040
Inaweza kuwa MSSQL, MySQL,
au kitu kama hicho.

1919
01:24:42,040 --> 01:24:47,080
Hii ni njia maombi mengi
ni iliyoundwa kwa leo.

1920
01:24:47,080 --> 01:24:49,594
>> Naam sisi kutaka kwenda na
huu ni wakati sisi kuongeza nje.

1921
01:24:49,594 --> 01:24:51,510
Tutaweza kwenda mbele na kuweka
S3 ndoo hadi pale.

1922
01:24:51,510 --> 01:24:54,200
Na kwamba S3 ndoo, badala ya kuwahudumia
up vitu wale wa kutoka servers-- yetu

1923
01:24:54,200 --> 01:24:55,220
tunaweza kufanya hivyo.

1924
01:24:55,220 --> 01:24:57,210
Kuweka binary yako yote
vitu kwenye seva yako

1925
01:24:57,210 --> 01:24:59,751
na unaweza kutumia wale server
matukio ya kuwatumikia takwimu ambazo up.

1926
01:24:59,751 --> 01:25:01,860
Lakini hiyo ni pretty ghali.

1927
01:25:01,860 --> 01:25:05,107
>> Njia bora ya kufanya ni kwenda mbele na
kuweka vitu wale walio katika S3 ndoo.

1928
01:25:05,107 --> 01:25:06,315
S3 ni hifadhi za seli kitu.

1929
01:25:06,315 --> 01:25:10,860
Ni kujengwa mahsusi kwa ajili ya
kuwahudumia up aina hii ya mambo.

1930
01:25:10,860 --> 01:25:13,690
Na kuruhusu wateja hao kuomba
moja kwa moja kutoka kwa wale ndoo kitu,

1931
01:25:13,690 --> 01:25:15,390
kuiuza watumishi.

1932
01:25:15,390 --> 01:25:17,020
Hivyo sisi ni kuanzia wadogo nje hapa.

1933
01:25:17,020 --> 01:25:19,140
>> Sasa tulipata watumiaji duniani kote.

1934
01:25:19,140 --> 01:25:19,730
I got watumiaji.

1935
01:25:19,730 --> 01:25:23,380
Mimi haja ya kuwa na maudhui ndani ya nchi
iko karibu na watumiaji hawa, sawa?

1936
01:25:23,380 --> 01:25:26,200
Nimekuwa kuundwa ndoo S3
kama chanzo wangu there.

1937
01:25:26,200 --> 01:25:29,370
Na mimi itabidi mbele kwamba pamoja na
CloudFront usambazaji.

1938
01:25:29,370 --> 01:25:31,720
>> CloudFront ni CD na
yaliyomo utoaji wa mtandao.

1939
01:25:31,720 --> 01:25:35,750
Kimsingi inachukua data kwamba bayana
na kukamatwa kwa yote juu ya mtandao

1940
01:25:35,750 --> 01:25:39,230
hivyo watumiaji wanaweza kuwa na kila mahali
majibu ya haraka sana wakati

1941
01:25:39,230 --> 01:25:40,960
wao kuomba vitu hizo.

1942
01:25:40,960 --> 01:25:41,960
>> Hivyo kupata wazo.

1943
01:25:41,960 --> 01:25:48,230
Wewe ni aina ya leveraging zote
masuala ya AWS hapa kwa kupata hii kufanyika.

1944
01:25:48,230 --> 01:25:50,790
Na hatimaye, sisi kutupa
katika kundi auto kuongeza.

1945
01:25:50,790 --> 01:25:52,737
Hivyo matukio yetu AC2
ya mchezo server yetu,

1946
01:25:52,737 --> 01:25:54,820
kama wao kuanza kupata busier
na busier na busier,

1947
01:25:54,820 --> 01:25:57,236
wao itabidi tu spin nyingine
Mathalani, spin mfano mwingine,

1948
01:25:57,236 --> 01:25:58,210
spin mfano mwingine.

1949
01:25:58,210 --> 01:26:02,090
Hivyo teknolojia AWS ina, ni
inaruhusu wewe taja vigezo

1950
01:26:02,090 --> 01:26:04,650
kote ambayo seva yako kukua.

1951
01:26:04,650 --> 01:26:08,110
Hivyo unaweza kuwa n idadi ya watumishi
huko nje wakati wowote.

1952
01:26:08,110 --> 01:26:11,870
Na kama mzigo wako huenda zake, wao itabidi
kuogopa, idadi mapenzi shrink.

1953
01:26:11,870 --> 01:26:15,250
Na kama mzigo anakuja nyuma,
kutakuwa na kukua nyuma nje, elastically.

1954
01:26:15,250 --> 01:26:17,050
>> Hivyo hii inaonekana ni kubwa.

1955
01:26:17,050 --> 01:26:19,800
Sisi tumepewa mengi ya matukio EC2.

1956
01:26:19,800 --> 01:26:21,671
Tunaweza kuweka cache katika
mbele ya database,

1957
01:26:21,671 --> 01:26:23,045
kujaribu na kuharakisha database.

1958
01:26:23,045 --> 01:26:25,030
Shinikizo hatua ya pili
kawaida watu kuona

1959
01:26:25,030 --> 01:26:28,850
ni wao wadogo mchezo kutumia
kimahusiano mfumo database.

1960
01:26:28,850 --> 01:26:30,790
Jeez, Mbegu
utendaji ni ya kutisha.

1961
01:26:30,790 --> 01:26:31,932
Je, sisi kuboresha hiyo?

1962
01:26:31,932 --> 01:26:33,640
Hebu jaribu kuweka
cache mbele ya jambo hilo.

1963
01:26:33,640 --> 01:26:36,780
>> Naam, cache haifanyi kazi
kubwa sana katika michezo, sawa?

1964
01:26:36,780 --> 01:26:39,330
Kwa ajili ya michezo, kuandika ni chungu.

1965
01:26:39,330 --> 01:26:40,930
Michezo ni kuandika sana nzito.

1966
01:26:40,930 --> 01:26:43,610
Cache haifanyi kazi wakati uko
kuandika nzito kwa sababu wameweza daima

1967
01:26:43,610 --> 01:26:44,610
got update cache.

1968
01:26:44,610 --> 01:26:47,780
Update cache, ni
lisilo kuwa Caching.

1969
01:26:47,780 --> 01:26:49,780
Ni kweli tu kazi ya ziada.

1970
01:26:49,780 --> 01:26:51,970
>> Hivyo ambapo sisi kwenda hapa?

1971
01:26:51,970 --> 01:26:54,400
Nimepata bottleneck kubwa
chini huko katika database.

1972
01:26:54,400 --> 01:26:57,661
Na mahali pa kwenda
wazi ni partitioning.

1973
01:26:57,661 --> 01:26:59,410
Partitioning si
rahisi kufanya wakati uko

1974
01:26:59,410 --> 01:27:01,900
kushughulika na database kimahusiano.

1975
01:27:01,900 --> 01:27:05,080
Na database kimahusiano, wewe ni
jukumu la kusimamia, kwa ufanisi,

1976
01:27:05,080 --> 01:27:06,210
nafasi muhimu.

1977
01:27:06,210 --> 01:27:10,527
Wewe ni watumiaji kati ya A na M akisema
kwenda hapa, kati ya N na Z kwenda huko.

1978
01:27:10,527 --> 01:27:12,360
Na wewe ni byte
hela maombi.

1979
01:27:12,360 --> 01:27:15,000
Hivyo wewe ni kushughulika na
taarifa hii chanzo kuhesabu.

1980
01:27:15,000 --> 01:27:18,670
Una matatizo kikazi
ambayo hayana span partitions.

1981
01:27:18,670 --> 01:27:20,560
Nimepata kila aina ya
messiness kwamba wewe ni

1982
01:27:20,560 --> 01:27:23,040
kushughulika na chini huko akijaribu
kukabiliana na kuongeza nje

1983
01:27:23,040 --> 01:27:25,120
na ujenzi wa miundombinu kubwa.

1984
01:27:25,120 --> 01:27:27,284
Ni tu hakuna furaha.

1985
01:27:27,284 --> 01:27:30,930
>> Watazamaji: Hivyo ni wewe kusema kwamba
kuongeza pointi chanzo kasi up

1986
01:27:30,930 --> 01:27:31,430
mchakato?

1987
01:27:31,430 --> 01:27:32,513
RICK Houlihan: Kuongeza?

1988
01:27:32,513 --> 01:27:33,520
Pointi Chanzo: Watazamaji.

1989
01:27:33,520 --> 01:27:34,410
RICK Houlihan: pointi Chanzo?

1990
01:27:34,410 --> 01:27:37,500
Watazamaji: Kutokana na habari,
ambapo habari ni kuja kutoka?

1991
01:27:37,500 --> 01:27:38,250
RICK Houlihan: Hapana

1992
01:27:38,250 --> 01:27:41,820
Ninachosema ni kuongeza
idadi ya partitions katika kuhifadhi data

1993
01:27:41,820 --> 01:27:44,060
inaboresha throughput.

1994
01:27:44,060 --> 01:27:48,300
Hivyo nini kinatokea hapa ni watumiaji
kuja ndani EC2 mfano hapa,

1995
01:27:48,300 --> 01:27:50,780
vizuri, kama mimi haja ya mtumiaji
hiyo ni kwa M, nitakwenda hapa.

1996
01:27:50,780 --> 01:27:53,560
Kutoka N kupita, nitakwenda hapa.

1997
01:27:53,560 --> 01:27:55,060
Kutoka P A to Z, nitakwenda hapa.

1998
01:27:55,060 --> 01:27:57,120
>> Watazamaji: sawa, wale hivyo wale watu
zote kuhifadhiwa katika nodes mbalimbali?

1999
01:27:57,120 --> 01:27:57,911
>> RICK Houlihan: Ndiyo.

2000
01:27:57,911 --> 01:28:00,210
Fikiria hayo kama
maghala mbalimbali ya data.

2001
01:28:00,210 --> 01:28:01,660
Hivyo wewe ni kuwa kwa kufanya hivyo.

2002
01:28:01,660 --> 01:28:02,910
Kama wewe ni kujaribu kufanya
hivyo, kama wewe ni kujaribu

2003
01:28:02,910 --> 01:28:05,730
wadogo kwenye jukwaa kimahusiano,
hii ni nini unafanya.

2004
01:28:05,730 --> 01:28:08,100
Wewe ni kuchukua takwimu na
wewe ni kukata chini.

2005
01:28:08,100 --> 01:28:10,975
Na wewe ni partitioning ni hela
matukio mbalimbali ya database.

2006
01:28:10,975 --> 01:28:13,580
Na wewe ni kusimamia yote
katika maombi daraja.

2007
01:28:13,580 --> 01:28:14,729
Siyo furaha.

2008
01:28:14,729 --> 01:28:15,770
Basi je, tunataka kwenda?

2009
01:28:15,770 --> 01:28:20,240
Tunataka kwenda DynamoDB, kusimamiwa kikamilifu,
NoSQL kuhifadhi data, utoaji throughput.

2010
01:28:20,240 --> 01:28:22,680
Sisi kutumia bahati sekondari.

2011
01:28:22,680 --> 01:28:26,154
Ni kimsingi HTTP API na
pamoja na hati msaada.

2012
01:28:26,154 --> 01:28:28,570
Hivyo huna kuwa na wasiwasi
kuhusu yoyote ya kwamba partitioning.

2013
01:28:28,570 --> 01:28:30,740
Sisi kufanya yote kwa ajili yenu.

2014
01:28:30,740 --> 01:28:33,260
Hivyo sasa, badala yake, ninyi
tu kuandika kwenye meza.

2015
01:28:33,260 --> 01:28:36,490
Kama meza inahitaji partitioned,
kitu kinachotokea nyuma ya pazia.

2016
01:28:36,490 --> 01:28:40,642
Wewe ni kabisa maboksi
na kwamba kama developer.

2017
01:28:40,642 --> 01:28:42,350
Basi hebu majadiliano juu ya
baadhi ya kesi ya matumizi

2018
01:28:42,350 --> 01:28:47,564
kwamba sisi kukimbia katika katika michezo ya kubahatisha, kawaida
matukio ya michezo ya kubahatisha, leaderboard.

2019
01:28:47,564 --> 01:28:49,980
Basi nimepata watumiaji anaingia,
BoardNames kwamba wao ni

2020
01:28:49,980 --> 01:28:52,930
juu ya, alama kwa mtumiaji huyu.

2021
01:28:52,930 --> 01:28:57,700
Tupate hashing juu ya kitambulisho cha mtumiaji,
na kisha tuna mbalimbali juu ya mchezo.

2022
01:28:57,700 --> 01:28:59,960
Hivyo kila mtumiaji anataka kuona
mchezo zote yeye alicheza

2023
01:28:59,960 --> 01:29:01,770
na alama yake yote juu
hela zote mchezo.

2024
01:29:01,770 --> 01:29:04,000
Hivyo hiyo ni leaderboard yake binafsi.

2025
01:29:04,000 --> 01:29:10,010
>> Sasa nataka kwenda katika na nataka get--
hivyo mimi kupata bao hizi binafsi.

2026
01:29:10,010 --> 01:29:12,827
Nini nataka kufanya ni kwenda kupata
alama za juu nchini watumiaji wote.

2027
01:29:12,827 --> 01:29:13,660
Hivyo ni jinsi gani mimi kufanya hivyo?

2028
01:29:13,660 --> 01:29:18,070
Wakati rekodi yangu ni heshi juu ya
kitambulisho cha mtumiaji, kilicholengwa juu ya mchezo,

2029
01:29:18,070 --> 01:29:20,740
vizuri mimi nina kwenda mbele
na urekebishaji, kujenga GSI,

2030
01:29:20,740 --> 01:29:22,370
na mimi nina kwenda kufanyia marekebisho data hizo.

2031
01:29:22,370 --> 01:29:27,310
>> Sasa mimi nina kwenda kwa hash juu ya
BoardName, ambayo ni mchezo.

2032
01:29:27,310 --> 01:29:29,800
Na mimi nina kwenda kwa mbalimbali juu ya alama ya juu.

2033
01:29:29,800 --> 01:29:31,540
Na sasa nimekuwa kuundwa ndoo tofauti.

2034
01:29:31,540 --> 01:29:34,790
Mimi nina kutumia meza moja,
data bidhaa hiyo.

2035
01:29:34,790 --> 01:29:39,870
Lakini mimi nina kujenga ndoo kwamba anatoa
mimi kuwakusanya alama za juu na mchezo.

2036
01:29:39,870 --> 01:29:43,180
>> Na siwezi swala meza kwamba
kupata taarifa hiyo.

2037
01:29:43,180 --> 01:29:50,890
Hivyo nimekuwa kuweka kwamba mfano swala hadi
kuungwa mkono na ripoti ya sekondari.

2038
01:29:50,890 --> 01:29:54,556
Sasa wanaweza kuwa yamepangwa kwa BoardName
na yamepangwa kwa TopScore, kutegemea.

2039
01:29:54,556 --> 01:29:57,180
Hivyo unaweza kuona, haya ni aina
ya kutumia kesi ya kupata katika michezo ya kubahatisha.

2040
01:29:57,180 --> 01:30:02,190
Nyingine nzuri ya matumizi kesi tunapata katika michezo ya kubahatisha
ni tuzo na ambaye ni mshindi wa tuzo.

2041
01:30:02,190 --> 01:30:05,340
Na hii ni matumizi ya kesi kubwa
ambapo tunatoa wito bahati sparse.

2042
01:30:05,340 --> 01:30:07,340
Bahati sparse ni
uwezo wa kuzalisha

2043
01:30:07,340 --> 01:30:10,850
ripoti hiyo haina si lazima
vyenye kila kitu moja juu ya meza.

2044
01:30:10,850 --> 01:30:11,470
Na kwa nini?

2045
01:30:11,470 --> 01:30:14,540
Kwa sababu sifa hiyo kuwa
indexed haipo juu ya kila kitu.

2046
01:30:14,540 --> 01:30:16,460
>> Hivyo katika hili hasa
kutumia kesi, mimi kusema,

2047
01:30:16,460 --> 01:30:19,240
unajua nini, mimi nina kwenda kwa
kujenga sifa aitwaye tuzo.

2048
01:30:19,240 --> 01:30:22,970
Na mimi nina kwenda kumpa kila mtumiaji
ambayo ina tuzo hiyo wanampa.

2049
01:30:22,970 --> 01:30:25,950
Watumiaji kuwa hawana tuzo ni
si kwenda na kwamba sifa.

2050
01:30:25,950 --> 01:30:27,800
Hivyo wakati mimi kuunda
ripoti, watumiaji tu

2051
01:30:27,800 --> 01:30:28,960
kwamba ni kwenda kuonyesha
up katika ripoti ni

2052
01:30:28,960 --> 01:30:31,050
wale ambao kwa kweli kuwa mshindi wa tuzo.

2053
01:30:31,050 --> 01:30:34,440
Hivyo hiyo ni njia kuu ya kuwa na uwezo
kujenga kuchujwa bahati kwamba

2054
01:30:34,440 --> 01:30:40,580
ni sana, kuchagua sana kwamba hawana
kuwa na ripoti meza nzima.

2055
01:30:40,580 --> 01:30:43,050
>> Hivyo sisi ni kupata chini juu ya muda hapa.

2056
01:30:43,050 --> 01:30:49,190
Mimi nina kwenda kwenda mbele na ruka
nje na ruka hali hii.

2057
01:30:49,190 --> 01:30:52,625
Kuzungumza kidogo about--

2058
01:30:52,625 --> 01:30:54,460
>> Watazamaji: Je, mimi kuuliza swali haraka?

2059
01:30:54,460 --> 01:30:56,722
Moja ni kuandika nzito?

2060
01:30:56,722 --> 01:30:57,680
RICK Houlihan: Je, ni?

2061
01:30:57,680 --> 01:30:58,596
Watazamaji: Andika zito.

2062
01:30:58,596 --> 01:31:01,270
RICK Houlihan: Andika zito.

2063
01:31:01,270 --> 01:31:03,460
Ngoja nione.

2064
01:31:03,460 --> 01:31:06,220
>> Watazamaji: Au ni kwamba si
kitu unaweza tu

2065
01:31:06,220 --> 01:31:08,809
sauti ya katika suala hilo la sekunde?

2066
01:31:08,809 --> 01:31:10,850
RICK Houlihan: Sisi kwenda
kupitia upigaji kura mazingira.

2067
01:31:10,850 --> 01:31:11,670
Siyo kwamba mbaya.

2068
01:31:11,670 --> 01:31:14,580
Je, guys kuwa dakika chache?

2069
01:31:14,580 --> 01:31:15,860
SAWA.

2070
01:31:15,860 --> 01:31:17,890
>> Hivyo tutaweza majadiliano juu ya kupiga kura.

2071
01:31:17,890 --> 01:31:20,250
Hivyo kupiga kura muda halisi, tuna
mahitaji kwa ajili ya kupiga kura.

2072
01:31:20,250 --> 01:31:25,250
Mahitaji ni kwamba tunaruhusu
kila mtu kupiga kura mara moja tu.

2073
01:31:25,250 --> 01:31:28,060
Tunataka hakuna mtu kuwa na uwezo
kubadili kura zao.

2074
01:31:28,060 --> 01:31:31,045
Tunataka kweli muda kuwakusanya
na analytics kwa idadi ya watu

2075
01:31:31,045 --> 01:31:34,210
kwamba tunakwenda kuwa
kuonyesha kwa watumiaji kwenye tovuti.

2076
01:31:34,210 --> 01:31:35,200
>> Fikiria hali hii.

2077
01:31:35,200 --> 01:31:37,550
Sisi kazi nyingi ukweli
TV inaonyesha ambapo wao uko

2078
01:31:37,550 --> 01:31:38,960
kufanya aina hizi halisi ya mambo.

2079
01:31:38,960 --> 01:31:41,584
Hivyo unaweza kufikiria mazingira,
tuna mamilioni na mamilioni

2080
01:31:41,584 --> 01:31:43,959
wasichana wa umri mdogo pale
na simu zao za mkononi

2081
01:31:43,959 --> 01:31:46,250
na kupiga kura, na kupiga kura, na
kupiga kura kwa ajili mtu wao ni

2082
01:31:46,250 --> 01:31:48,610
kupata kuwa maarufu zaidi.

2083
01:31:48,610 --> 01:31:50,830
Basi hizi ni baadhi ya
mahitaji sisi kukimbia nje.

2084
01:31:50,830 --> 01:31:52,990
>> Na hivyo kwanza kuchukua
katika kutatua tatizo hili

2085
01:31:52,990 --> 01:31:55,090
itakuwa kujenga
rahisi sana maombi.

2086
01:31:55,090 --> 01:31:56,490
Hivyo mimi nimepata programu hii.

2087
01:31:56,490 --> 01:31:57,950
Mimi na baadhi ya wapiga kura huko nje.

2088
01:31:57,950 --> 01:31:59,980
Wao kuja katika, wao kugonga programu kupiga kura.

2089
01:31:59,980 --> 01:32:03,440
Mimi nimepata baadhi mbichi kura meza
Mimi itabidi dampo kura wale katika.

2090
01:32:03,440 --> 01:32:05,780
Mimi itabidi baadhi mabao
kura meza kwamba

2091
01:32:05,780 --> 01:32:09,490
atafanya analytics yangu na idadi ya watu,
na tutaweza kuweka yote haya katika huko.

2092
01:32:09,490 --> 01:32:11,420
>> Na hii ni kubwa.

2093
01:32:11,420 --> 01:32:12,332
Maisha ni mazuri.

2094
01:32:12,332 --> 01:32:15,040
Maisha ya wema mpaka tunaona kwamba
kuna siku zote moja au mbili tu

2095
01:32:15,040 --> 01:32:16,879
Watu hawa walio maarufu katika uchaguzi.

2096
01:32:16,879 --> 01:32:19,420
Kuna mambo moja au mbili tu
kwamba watu kweli huduma kuhusu.

2097
01:32:19,420 --> 01:32:22,340
Na kama wewe ni kupiga kura katika
wadogo, kwa ghafla mimi nina

2098
01:32:22,340 --> 01:32:26,360
kwenda kuwa hammering kuzimu nje ya
wagombea wawili, wagombea moja au mbili.

2099
01:32:26,360 --> 01:32:29,390
Idadi ndogo sana ya vitu
watu wanaona kuwa maarufu.

2100
01:32:29,390 --> 01:32:31,710
>> Hii si nzuri kubuni muundo.

2101
01:32:31,710 --> 01:32:33,549
Hii ni kweli
mbaya sana kubuni muundo

2102
01:32:33,549 --> 01:32:36,340
kwa sababu inajenga nini hasa sisi
kuongelea ambayo ilikuwa funguo moto.

2103
01:32:36,340 --> 01:32:38,960
Moto funguo ni kitu sisi si kama.

2104
01:32:38,960 --> 01:32:40,470
>> Hivyo ni jinsi gani sisi kurekebisha hayo?

2105
01:32:40,470 --> 01:32:47,640
Na kwa kweli, njia ya kutatua tatizo hili ni
kwa kuchukua wale ndoo mgombea

2106
01:32:47,640 --> 01:32:51,490
na kwa kila mgombea tuna,
tunakwenda append thamani kubahatisha,

2107
01:32:51,490 --> 01:32:54,192
kitu ambacho tunajua, bila mpangilio
thamani kati ya moja na 100,

2108
01:32:54,192 --> 01:32:56,620
kati ya 100 na 1,000,
au kati ya mmoja na 1000,

2109
01:32:56,620 --> 01:32:59,940
Hata hivyo maadili wengi bila mpangilio unataka
append kwenye mwisho wa mgombea huyo.

2110
01:32:59,940 --> 01:33:01,330
>> Na nini mimi kweli amefanya basi?

2111
01:33:01,330 --> 01:33:05,830
Kama mimi nina kutumia mgombea ID kama
ndoo kwa kura jumla ya mabao,

2112
01:33:05,830 --> 01:33:08,780
kama nimekuwa aliongeza bila mpangilio
idadi hadi mwisho wa kwamba,

2113
01:33:08,780 --> 01:33:12,000
Nimekuwa kuundwa sasa 10 ndoo,
ndoo mia, elfu ndoo

2114
01:33:12,000 --> 01:33:14,160
kwamba mimi nina kujumlisha kura hela.

2115
01:33:14,160 --> 01:33:18,030
>> Hivyo mimi na mamilioni, na mamilioni,
na mamilioni ya kumbukumbu kuja katika

2116
01:33:18,030 --> 01:33:22,050
kwa wagombea hawa, Mimi sasa kueneza
kura wale hela Mgombea A_1

2117
01:33:22,050 --> 01:33:24,630
kupitia Mgombea A_100, kwa sababu
kila wakati kura huja katika,

2118
01:33:24,630 --> 01:33:26,530
Mimi kuzalisha random
thamani kati ya moja na 100.

2119
01:33:26,530 --> 01:33:29,446
Mimi tacking ni kwenye mwisho wa
Mgombea wa mtu huyo kupiga kura kwa ajili.

2120
01:33:29,446 --> 01:33:31,120
Mimi utupaji ndani kwamba ndoo.

2121
01:33:31,120 --> 01:33:33,910
>> Sasa nyuma, najua
ndipo nilipata mia ndoo.

2122
01:33:33,910 --> 01:33:36,350
Hivyo wakati mimi nataka kwenda mbele
na jumla ya mabao kura,

2123
01:33:36,350 --> 01:33:38,244
Mimi kusoma na zile ndoo wote.

2124
01:33:38,244 --> 01:33:39,160
Hivyo mimi kwenda mbele na kuongeza.

2125
01:33:39,160 --> 01:33:42,410
Na kisha mimi kuwatawanya kukusanya
ambapo mimi kwenda nje na kusema hey,

2126
01:33:42,410 --> 01:33:45,399
unajua nini, muhimu mgombea huyu
nafasi ni ndoo zaidi ya mia.

2127
01:33:45,399 --> 01:33:47,940
Mimi nina kwenda kukusanya wote
kura kutoka ndoo mia hizo.

2128
01:33:47,940 --> 01:33:49,981
Mimi nina kwenda kwa jumla ya mabao
wao na mimi nina kwenda kusema,

2129
01:33:49,981 --> 01:33:53,830
Mgombea A sasa ina
jumla kuhesabu kura za x.

2130
01:33:53,830 --> 01:33:55,690
>> Sasa wote wawili kuandika
swala na kusoma swala

2131
01:33:55,690 --> 01:33:58,160
ni vizuri kusambazwa
kwa sababu mimi nina kuandika hela

2132
01:33:58,160 --> 01:34:00,320
na mimi nina kusoma katika mamia ya funguo.

2133
01:34:00,320 --> 01:34:03,500
Mimi si kuandika na
kusoma hela ufunguo moja sasa.

2134
01:34:03,500 --> 01:34:04,950
Hivyo hiyo ni mfano mkuu.

2135
01:34:04,950 --> 01:34:08,090
>> Hii ni kweli pengine ni moja
ya kubuni muhimu zaidi

2136
01:34:08,090 --> 01:34:10,420
chati kwa wadogo katika NoSQL.

2137
01:34:10,420 --> 01:34:14,470
Utaona aina hii ya
mfano kubuni katika kila ladha.

2138
01:34:14,470 --> 01:34:19,100
MongoDB, DynamoDB, haina
suala hilo, sisi sote tuna kufanya hivyo.

2139
01:34:19,100 --> 01:34:21,840
Kwa sababu wakati wewe ni kushughulika
kwa aggregations wale kubwa,

2140
01:34:21,840 --> 01:34:26,650
una kufikiri njia ya
kuzigawanya katika ndoo.

2141
01:34:26,650 --> 01:34:29,512
Hivyo hii ni njia ya kufanya hivyo.

2142
01:34:29,512 --> 01:34:31,220
Haki wote, hivyo nini
unafanya hivi sasa

2143
01:34:31,220 --> 01:34:35,252
ni wewe biashara mbali kusoma
gharama kwa kuandika scalability.

2144
01:34:35,252 --> 01:34:37,085
Gharama ya kusoma yangu ni
kidogo ngumu zaidi

2145
01:34:37,085 --> 01:34:40,220
na mimi kuwa na kwenda kusoma kutoka
ndoo mia badala ya moja.

2146
01:34:40,220 --> 01:34:41,310
Lakini nina uwezo wa kuandika.

2147
01:34:41,310 --> 01:34:44,860
Na throughput yangu, kuandika yangu
throughput ni ajabu.

2148
01:34:44,860 --> 01:34:49,450
Hivyo ni kawaida ya thamani
mbinu kwa ajili ya kuongeza DynamoDB,

2149
01:34:49,450 --> 01:34:51,350
au orodha yoyote NoSQL kwa jambo hilo.

2150
01:34:51,350 --> 01:34:53,824

2151
01:34:53,824 --> 01:34:55,240
Kwa hiyo sisi figured nje ya jinsi ya kuongeza yake.

2152
01:34:55,240 --> 01:34:56,930
Na sisi figured jinsi ya
kuondoa funguo yetu moto.

2153
01:34:56,930 --> 01:34:57,820
Na hii ni ajabu.

2154
01:34:57,820 --> 01:34:58,960
Na tulipata mfumo huu vizuri.

2155
01:34:58,960 --> 01:35:02,043
Na ni ametupa kupiga kura sahihi sana
kwa sababu tuna rekodi kura de-baradhuli.

2156
01:35:02,043 --> 01:35:03,130
Ni kujengwa katika DynamoDB.

2157
01:35:03,130 --> 01:35:05,380
Kuongelea haki za masharti.

2158
01:35:05,380 --> 01:35:08,170
>> Wakati wapiga kura unakuja, unaweka
kuingiza kwenye meza,

2159
01:35:08,170 --> 01:35:11,220
wao kuingiza na wapiga ID zao,
kama wao kujaribu kuingiza kura mwingine,

2160
01:35:11,220 --> 01:35:13,320
Mimi kufanya kuandika masharti.

2161
01:35:13,320 --> 01:35:16,960
Kusema tu kuandika hii
kama hii haipo.

2162
01:35:16,960 --> 01:35:19,270
Hivyo kwa haraka kama mimi kuona kwamba
kwamba kura ya kugonga meza,

2163
01:35:19,270 --> 01:35:20,460
hakuna mtu mwingine kwenda kuwa
uwezo wa kuweka kura zao katika.

2164
01:35:20,460 --> 01:35:21,634
Na hiyo ndiyo ajabu.

2165
01:35:21,634 --> 01:35:23,550
Na sisi ni incrementing
mgombea wetu counters.

2166
01:35:23,550 --> 01:35:25,466
Na sisi ni kufanya wetu
idadi ya watu na vitu vyote.

2167
01:35:25,466 --> 01:35:29,110
Lakini kile kinachotokea kama yangu
maombi iko juu?

2168
01:35:29,110 --> 01:35:31,350
Sasa wote wa kura ghafla
ni akiingia ndani na mimi

2169
01:35:31,350 --> 01:35:34,840
sijui kama wao ni kupata kusindika
ndani ya analytics yangu na idadi ya watu

2170
01:35:34,840 --> 01:35:36,040
tena.

2171
01:35:36,040 --> 01:35:38,462
Na wakati maombi
anakuja nyuma juu, jinsi

2172
01:35:38,462 --> 01:35:41,420
kuzimu sijui mambo kura na
wamekuwa kusindika na wapi mimi kuanza?

2173
01:35:41,420 --> 01:35:44,530
>> Hivyo hii ni tatizo halisi wakati
kuanza kuangalia aina hii ya mazingira.

2174
01:35:44,530 --> 01:35:45,571
Na jinsi gani sisi kutatua hayo?

2175
01:35:45,571 --> 01:35:48,070
Sisi kutatua hayo na kile sisi
piga DynamoDB mito.

2176
01:35:48,070 --> 01:35:53,470
Mito ni muda kuamuru na
partitioned mabadiliko logi ya kila upatikanaji

2177
01:35:53,470 --> 01:35:55,700
kwa meza, kila kuandika
upatikanaji wa meza.

2178
01:35:55,700 --> 01:35:58,810
Data yoyote ambayo imeandikwa kwa
meza inaonyesha juu ya mkondo.

2179
01:35:58,810 --> 01:36:01,815
>> Ni kimsingi foleni saa 24.

2180
01:36:01,815 --> 01:36:03,690
Vitu kugonga mkondo wa maji,
wanaishi kwa saa 24.

2181
01:36:03,690 --> 01:36:05,990
Wao inaweza kusomwa mara nyingi.

2182
01:36:05,990 --> 01:36:09,400
Uhakika wa kufikishwa
tu mara moja kwa mkondo wa maji,

2183
01:36:09,400 --> 01:36:11,180
inaweza kusomwa n idadi ya nyakati.

2184
01:36:11,180 --> 01:36:14,910
Hivyo hata hivyo hatua nyingi unataka
hutumia data ya hapo, unaweza kutosheleza.

2185
01:36:14,910 --> 01:36:16,350
Ni itaonekana kila update.

2186
01:36:16,350 --> 01:36:18,455
Kila kuandika mapenzi tu
kuonekana mara moja juu ya mkondo.

2187
01:36:18,455 --> 01:36:20,621
Hivyo huna kuwa na wasiwasi
kuhusu usindikaji ni mara mbili

2188
01:36:20,621 --> 01:36:22,500
kutoka katika mchakato huo.

2189
01:36:22,500 --> 01:36:25,350
>> Ni madhubuti kuamuru kwa kila kitu.

2190
01:36:25,350 --> 01:36:28,180
Tunaposema wakati
kuamuru na partitioned,

2191
01:36:28,180 --> 01:36:30,680
utaona kwa kuhesabu juu ya mkondo.

2192
01:36:30,680 --> 01:36:33,169
Utaona vitu, updates kwa utaratibu.

2193
01:36:33,169 --> 01:36:35,210
Sisi si kuhakikisha
juu ya mkondo kwamba wewe ni

2194
01:36:35,210 --> 01:36:40,240
kwenda kupata kila shughuli
ili hela vitu.

2195
01:36:40,240 --> 01:36:42,440
>> Hivyo mito ni idempotent.

2196
01:36:42,440 --> 01:36:44,037
Je, sisi wote kujua nini maana idempotent?

2197
01:36:44,037 --> 01:36:46,620
Idempotent ina maana unaweza kufanya hivyo
tena na tena, na tena.

2198
01:36:46,620 --> 01:36:48,200
Matokeo yake itakuja kuwa sawa.

2199
01:36:48,200 --> 01:36:49,991
>> Mito ni idempotent,
lakini wao kuwa

2200
01:36:49,991 --> 01:36:54,860
alicheza kutoka kianzio,
popote wewe kuchagua, hadi mwisho,

2201
01:36:54,860 --> 01:36:57,950
au wao si kusababisha
katika maadili sawa.

2202
01:36:57,950 --> 01:36:59,727
>> Same kitu na MongoDB.

2203
01:36:59,727 --> 01:37:01,560
MongoDB ina kujenga
watataka oplog.

2204
01:37:01,560 --> 01:37:04,140
Ni halisi kujenga huo.

2205
01:37:04,140 --> 01:37:06,500
NoSQL databaser wengi
na kujenga hii.

2206
01:37:06,500 --> 01:37:08,790
Wao kuitumia kufanya mambo
kama replication, ambayo

2207
01:37:08,790 --> 01:37:10,475
ni nini hasa sisi kufanya na mito.

2208
01:37:10,475 --> 01:37:12,350
Watazamaji: Labda
uzushi swali, lakini wewe

2209
01:37:12,350 --> 01:37:13,975
majadiliano juu ya programu ya kufanya chini kadhalika.

2210
01:37:13,975 --> 01:37:16,089
Ni mito uhakika
kamwe uwezekano wa kwenda chini?

2211
01:37:16,089 --> 01:37:18,630
RICK Houlihan: Yeah, mito
ni uhakika wa kamwe kwenda chini.

2212
01:37:18,630 --> 01:37:21,040
Sisi kusimamia miundombinu
nyuma. mito moja kwa moja

2213
01:37:21,040 --> 01:37:22,498
kupeleka katika auto kuongeza kundi lao.

2214
01:37:22,498 --> 01:37:25,910
Tutaweza kwenda kupitia kidogo
kidogo kuhusu nini kinatokea.

2215
01:37:25,910 --> 01:37:30,060
>> Mimi lazima kusema wao siyo
uhakika na kamwe kwenda chini.

2216
01:37:30,060 --> 01:37:33,110
Mambo ni uhakika
kuonekana katika mkondo.

2217
01:37:33,110 --> 01:37:36,740
Na mkondo itakuwa kupatikana.

2218
01:37:36,740 --> 01:37:40,580
Kwa hiyo kile inakwenda chini au anakuja nyuma
up, ambayo hufanyika chini.

2219
01:37:40,580 --> 01:37:43,844
Ni covers-- ni sawa.

2220
01:37:43,844 --> 01:37:46,260
Haki wote, ili kupata mbalimbali
Mtazamo aina mbali screen.

2221
01:37:46,260 --> 01:37:51,040
Mtazamo aina ambazo ni muhimu kwa
programu kwa kawaida ni, nini ilikuwa hivyo?

2222
01:37:51,040 --> 01:37:52,370
Mimi kupata maoni ya zamani.

2223
01:37:52,370 --> 01:37:55,630
Wakati update hits meza, ni itabidi
kushinikiza mtazamo wa zamani wa mkondo

2224
01:37:55,630 --> 01:38:02,070
hivyo data unaweza archive, au mabadiliko
kudhibiti, mabadiliko ya utambulisho, mabadiliko

2225
01:38:02,070 --> 01:38:03,600
usimamizi.

2226
01:38:03,600 --> 01:38:07,160
>> Sura mpya, ni nini sasa baada ya
update, hiyo ni aina nyingine ya maoni

2227
01:38:07,160 --> 01:38:07,660
unaweza kupata.

2228
01:38:07,660 --> 01:38:09,660
Unaweza kupata wawili taswira ya zamani na mpya.

2229
01:38:09,660 --> 01:38:10,660
Labda nataka wote wawili.

2230
01:38:10,660 --> 01:38:11,790
Nataka kuona ni kitu gani.

2231
01:38:11,790 --> 01:38:13,290
Nataka kuona nini iliyopita na.

2232
01:38:13,290 --> 01:38:15,340
>> Nina aina kufuata
mchakato kwamba anaendesha.

2233
01:38:15,340 --> 01:38:17,430
Inahitaji kuthibitisha kwamba
Wakati mambo hayo mabadiliko,

2234
01:38:17,430 --> 01:38:21,840
kwamba wao ni ndani ya mipaka fulani
au ndani ya vigezo fulani.

2235
01:38:21,840 --> 01:38:23,840
>> Na kisha labda mimi tu
haja ya kujua nini iliyopita.

2236
01:38:23,840 --> 01:38:26,240
Sijali nini bidhaa iliyopita.

2237
01:38:26,240 --> 01:38:28,580
Sina haja ya haja ya kujua
nini sifa iliyopita.

2238
01:38:28,580 --> 01:38:30,882
Mimi tu haja ya kujua kwamba
Vitu ni kuguswa.

2239
01:38:30,882 --> 01:38:33,340
Basi hizi ni aina ya maoni
kwamba kupata mbali mkondo

2240
01:38:33,340 --> 01:38:35,960
na unaweza kuingiliana na.

2241
01:38:35,960 --> 01:38:37,840
>> Maombi ambayo
hutumia mkondo wa maji,

2242
01:38:37,840 --> 01:38:39,298
hii ni aina ya njia hii kazi.

2243
01:38:39,298 --> 01:38:42,570
DynamoDB mteja kuuliza kwa
kushinikiza data na meza.

2244
01:38:42,570 --> 01:38:44,750
Mito kupeleka kwenye kile tunachokiita shards.

2245
01:38:44,750 --> 01:38:47,380
Shards ni scaled
kujitegemea ya meza.

2246
01:38:47,380 --> 01:38:50,660
Hawana kujipanga kabisa
kwa partitions ya meza yako.

2247
01:38:50,660 --> 01:38:52,540
Na sababu ni kwa nini ni
kwa sababu wao kujipanga

2248
01:38:52,540 --> 01:38:55,430
kupita uwezo wake, sasa
uwezo wa meza.

2249
01:38:55,430 --> 01:38:57,600
>> Wao kupeleka katika zao
mwenyewe auto kuongeza kundi,

2250
01:38:57,600 --> 01:39:00,800
na wao kuanza spin nje kulingana
jinsi anaandika wengi wanakuja katika,

2251
01:39:00,800 --> 01:39:03,090
jinsi reads-- wengi kweli ni anaandika.

2252
01:39:03,090 --> 01:39:05,820
Hakuna reads-- lakini jinsi
anaandika wengi wanakuja katika.

2253
01:39:05,820 --> 01:39:08,200
>> Na kisha nyuma
mwisho, tuna nini sisi

2254
01:39:08,200 --> 01:39:11,390
piga KCL, au Kinesis Mteja maktaba.

2255
01:39:11,390 --> 01:39:19,190
Kinesis ni data mkondo
teknolojia ya usindikaji kutoka Amazon.

2256
01:39:19,190 --> 01:39:22,040
Na mito ni kujengwa juu ya jambo hilo.

2257
01:39:22,040 --> 01:39:25,670
>> Hivyo kutumia KCL kuwezeshwa
programu kusoma mkondo.

2258
01:39:25,670 --> 01:39:28,752
Kinesis Mteja Library kweli
itaweza wafanyakazi kwa ajili yenu.

2259
01:39:28,752 --> 01:39:30,460
Na pia anafanya baadhi
mambo ya kuvutia.

2260
01:39:30,460 --> 01:39:35,630
Itakuwa kujenga baadhi meza up
katika DynamoDB yako tablespace

2261
01:39:35,630 --> 01:39:38,410
kufuatilia ambayo vitu
zimeshafanyiwa kazi.

2262
01:39:38,410 --> 01:39:41,190
Hivyo njia hii kama iko nyuma, ikiwa
yake huanguka juu na kuja na anapata

2263
01:39:41,190 --> 01:39:45,570
alisimama nyuma juu, inaweza kuamua ambapo
Ilikuwa ni katika usindikaji mkondo.

2264
01:39:45,570 --> 01:39:48,360
>> Hiyo ni muhimu sana wakati
wewe kuzungumza juu replication.

2265
01:39:48,360 --> 01:39:50,350
Mimi haja ya kujua nini
data alikuwa wamekuwa kusindika

2266
01:39:50,350 --> 01:39:52,810
na kile data bado kuwa processed.

2267
01:39:52,810 --> 01:39:57,380
Hivyo maktaba KCL kwa mito mapenzi
kukupa mengi ya kwamba utendaji.

2268
01:39:57,380 --> 01:39:58,990
Ni inachukua huduma ya utunzaji wa nyumba zote.

2269
01:39:58,990 --> 01:40:01,140
Ni anasimama mfanyakazi kwa kila Shard.

2270
01:40:01,140 --> 01:40:04,620
Ni inajenga meza utawala
kwa kila Shard, kwa kila mfanyakazi.

2271
01:40:04,620 --> 01:40:07,560
Na kama wale wafanyakazi moto,
wao kudumisha meza wale

2272
01:40:07,560 --> 01:40:10,510
ili kujua rekodi hii
ilikuwa kusoma na kusindika.

2273
01:40:10,510 --> 01:40:13,850
Na kisha kwa njia hiyo kama mchakato
akifa na anakuja nyuma online,

2274
01:40:13,850 --> 01:40:17,940
inaweza kuendelea kulia ambako ilichukua mbali.

2275
01:40:17,940 --> 01:40:20,850
>> Hivyo sisi kutumia hii kwa
msalaba-kanda replication.

2276
01:40:20,850 --> 01:40:24,680
Mengi ya wateja na haja ya
hoja data au sehemu ya meza zao data

2277
01:40:24,680 --> 01:40:25,920
karibu na mikoa mbalimbali.

2278
01:40:25,920 --> 01:40:29,230
Kuna mikoa tisa
wote duniani.

2279
01:40:29,230 --> 01:40:32,100
Hivyo huenda kuna mimi need--
wanaweza kuwa watumiaji katika bara la Asia, watumiaji

2280
01:40:32,100 --> 01:40:34,150
katika Pwani ya Mashariki ya Marekani.

2281
01:40:34,150 --> 01:40:38,980
Wana data mbalimbali ambazo
mahitaji ya kuwa ndani ya nchi kusambazwa.

2282
01:40:38,980 --> 01:40:42,510
Na labda mtumiaji inzi kutoka
Asia juu ya Umoja wa Mataifa,

2283
01:40:42,510 --> 01:40:45,020
na mimi nataka kuiga
data wake pamoja naye.

2284
01:40:45,020 --> 01:40:49,340
Basi alipo anapata mbali ya ndege, ana
uzoefu mzuri kwa kutumia programu yake ya mkononi.

2285
01:40:49,340 --> 01:40:52,360
>> Unaweza kutumia msalaba-kanda
replication maktaba kwa kufanya hivyo.

2286
01:40:52,360 --> 01:40:55,730
Kimsingi tuna
zinazotolewa teknolojia hizo mbili.

2287
01:40:55,730 --> 01:40:59,400
Moja ni console maombi unaweza
kusimama juu ya EC2 yako mwenyewe mfano.

2288
01:40:59,400 --> 01:41:01,240
Ni anaendesha replication safi.

2289
01:41:01,240 --> 01:41:02,720
Na kisha tuliyowapa maktaba.

2290
01:41:02,720 --> 01:41:06,070
Maktaba unaweza kutumia ili kujenga
maombi yako mwenyewe kama wewe

2291
01:41:06,070 --> 01:41:10,740
wanataka kufanya mambo mambo na kwamba data--
filter, kuiga sehemu tu ya hayo,

2292
01:41:10,740 --> 01:41:14,120
mzunguko data, hoja hiyo ndani ya
mbalimbali meza, kadhalika na kadhalika.

2293
01:41:14,120 --> 01:41:18,700

2294
01:41:18,700 --> 01:41:20,520
Basi hiyo ni aina ya nini kwamba inaonekana kama.

2295
01:41:20,520 --> 01:41:23,690
>> DynamoDB mito inaweza kuwa
kusindika na kile tunachokiita Lambda.

2296
01:41:23,690 --> 01:41:27,394
Sisi zilizotajwa kidogo kuhusu tukio
inaendeshwa maombi usanifu.

2297
01:41:27,394 --> 01:41:28,810
Lambda ni sehemu muhimu ya kwamba.

2298
01:41:28,810 --> 01:41:32,840
Lambda ni kificho kwamba moto juu ya mahitaji
katika kukabiliana na tukio fulani.

2299
01:41:32,840 --> 01:41:36,020
Moja ya matukio hayo inaweza kuwa
rekodi ya kuonekana kwenye mkondo.

2300
01:41:36,020 --> 01:41:39,100
Kama rekodi inaonekana kwenye mkondo wa maji,
tutaweza wito huu kazi Java.

2301
01:41:39,100 --> 01:41:44,980
Naam, hii ni JavaScript, na Lambda
inasaidia Node.js, Java, Python,

2302
01:41:44,980 --> 01:41:47,820
na hivi karibuni kuunga mkono
lugha zingine vilevile.

2303
01:41:47,820 --> 01:41:50,940
Na inatosha kusema, ni kificho safi.

2304
01:41:50,940 --> 01:41:53,610
kuandika Katika Java, unaweza kufafanua darasani.

2305
01:41:53,610 --> 01:41:55,690
Kushinikiza JAR juu katika Lambda.

2306
01:41:55,690 --> 01:42:00,200
Na kisha kutaja darasa
kuwaita katika kukabiliana na ambayo tukio hilo.

2307
01:42:00,200 --> 01:42:04,770
Na kisha miundombinu Lambda
nyuma ya kwamba inakwenda kwamba kanuni.

2308
01:42:04,770 --> 01:42:06,730
>> Kificho kwamba inaweza mchakato
rekodi mbali mkondo.

2309
01:42:06,730 --> 01:42:08,230
Ni anaweza kufanya kitu chochote anataka nayo.

2310
01:42:08,230 --> 01:42:11,650
Katika mfano huu hasa, kila tuko
kweli kufanya ni magogo sifa.

2311
01:42:11,650 --> 01:42:13,480
Lakini hii ni kanuni.

2312
01:42:13,480 --> 01:42:15,260
Kanuni anaweza kufanya kitu chochote, sawa?

2313
01:42:15,260 --> 01:42:16,600
>> Hivyo unaweza mzunguko data hizo.

2314
01:42:16,600 --> 01:42:18,160
Unaweza kuunda mtazamo derivative.

2315
01:42:18,160 --> 01:42:21,160
Kama ni muundo hati,
unaweza flatten muundo.

2316
01:42:21,160 --> 01:42:24,300
Unaweza kuunda bahati mbadala.

2317
01:42:24,300 --> 01:42:27,100
Kila aina ya mambo unaweza
kufanya na mito DynamoDB.

2318
01:42:27,100 --> 01:42:28,780
>> Na kwa kweli, kwamba ni nini kwamba inaonekana kama.

2319
01:42:28,780 --> 01:42:29,940
Ili kupata updates wale kuja katika.

2320
01:42:29,940 --> 01:42:31,190
Wao ni kuja mbali kamba.

2321
01:42:31,190 --> 01:42:32,720
Wao ni kusoma kwa kazi Lambda.

2322
01:42:32,720 --> 01:42:37,480
Wao ni kupokezana data na
kusukuma juu katika meza derivative,

2323
01:42:37,480 --> 01:42:42,200
kumfahamisha mifumo ya nje ya mabadiliko,
na kusukuma data kwenye ElastiCache.

2324
01:42:42,200 --> 01:42:45,900
>> Kuongelea jinsi ya kuweka cache
mbele ya database kwa kuwa mauzo

2325
01:42:45,900 --> 01:42:46,450
mazingira.

2326
01:42:46,450 --> 01:42:50,049
Vizuri kile kinachotokea kama mimi
update bidhaa maelezo?

2327
01:42:50,049 --> 01:42:52,340
Naam, kama ningekuwa na Lambda
kazi mbio juu ya meza kwamba,

2328
01:42:52,340 --> 01:42:55,490
kama mimi update bidhaa maelezo, ni itabidi
kuchukua rekodi mbali mkondo wa maji,

2329
01:42:55,490 --> 01:42:58,711
na kutakuwa na update ElastiCache
mfano kwa takwimu mpya.

2330
01:42:58,711 --> 01:43:00,460
Hivyo hiyo ni mengi ya
nini cha kufanya na Lambda.

2331
01:43:00,460 --> 01:43:02,619
Ni gundi kificho, viungio.

2332
01:43:02,619 --> 01:43:04,410
Na ni kweli inatoa
uwezo wa uzinduzi

2333
01:43:04,410 --> 01:43:07,930
na kuendesha maombi ngumu sana
bila ari server

2334
01:43:07,930 --> 01:43:10,371
miundombinu, ambayo ni kweli baridi.

2335
01:43:10,371 --> 01:43:13,100
>> Basi hebu kwenda nyuma ya yetu
halisi wakati wa kupiga kura usanifu.

2336
01:43:13,100 --> 01:43:17,984
Hii ni mpya na kuboresha na yetu
mito na KCL kuwezeshwa maombi.

2337
01:43:17,984 --> 01:43:20,150
Sawa mbele, tunaweza
kushughulikia wadogo yoyote ya uchaguzi.

2338
01:43:20,150 --> 01:43:21,100
Tunapenda hii.

2339
01:43:21,100 --> 01:43:24,770
Sisi ni kufanya nje kuwatawanya unakusanya
hela ndoo nyingi.

2340
01:43:24,770 --> 01:43:26,780
Sisi tumepewa matumaini locking kinachoendelea.

2341
01:43:26,780 --> 01:43:30,192
Tunaweza kuweka wapiga kura wetu
kutoka kubadilisha kura zao.

2342
01:43:30,192 --> 01:43:31,400
Wanaweza tu kupiga kura mara moja tu.

2343
01:43:31,400 --> 01:43:32,880
Hii ni ajabu.

2344
01:43:32,880 --> 01:43:35,895
Halisi wakati kosa kuvumiliana,
scalable kuwakusanya sasa.

2345
01:43:35,895 --> 01:43:38,270
Kama jambo iko juu, ni
anajua wapi upya yenyewe

2346
01:43:38,270 --> 01:43:41,300
linapokuja suala la nyuma hadi kwa sababu
sisi ni kutumia programu KCL.

2347
01:43:41,300 --> 01:43:45,700
Na kisha tunaweza pia kutumia kwamba
KCL maombi kushinikiza data nje

2348
01:43:45,700 --> 01:43:48,820
kwa redshift kwa wengine
analytics programu, au matumizi

2349
01:43:48,820 --> 01:43:51,990
MapReduce Elastic kuendesha
halisi wakati Streaming mbali aggregations

2350
01:43:51,990 --> 01:43:53,180
ya data hizo.

2351
01:43:53,180 --> 01:43:55,480
>> Hivyo haya ni mambo sisi
si aliongea kuhusu kiasi hicho.

2352
01:43:55,480 --> 01:43:57,375
Lakini wao uko ziada
teknolojia ambayo kuja

2353
01:43:57,375 --> 01:44:00,310
kubeba wakati wewe ni kuangalia
katika aina hii ya matukio.

2354
01:44:00,310 --> 01:44:03,160
>> Haki wote, hivyo hiyo ni juu
analytics na DynamoDB mito.

2355
01:44:03,160 --> 01:44:05,340
Unaweza kukusanya de-baradhuli
data, kufanya kila aina

2356
01:44:05,340 --> 01:44:09,490
ya mambo mazuri, jumla ya mabao data katika
kumbukumbu, kujenga meza wale derivative.

2357
01:44:09,490 --> 01:44:13,110
Hiyo ni mkubwa matumizi ya kesi
kwamba mengi ya wateja

2358
01:44:13,110 --> 01:44:16,950
wanahusika na, kwa kuchukua nested
mali ya hati hizo JSON

2359
01:44:16,950 --> 01:44:18,946
na kujenga bahati ziada.

2360
01:44:18,946 --> 01:44:21,680

2361
01:44:21,680 --> 01:44:23,150
>> Tuko mwishoni.

2362
01:44:23,150 --> 01:44:26,689
Asante kwa kuzaa na mimi.

2363
01:44:26,689 --> 01:44:28,480
Basi hebu majadiliano juu ya
kumbukumbu usanifu.

2364
01:44:28,480 --> 01:44:33,440
DynamoDB yapo katikati ya hivyo
sehemu kubwa ya miundombinu AWS.

2365
01:44:33,440 --> 01:44:37,090
Kimsingi unaweza ndoano yake
hadi kitu chochote unataka.

2366
01:44:37,090 --> 01:44:45,600
Maombi kujengwa kwa kutumia Dynamo ni pamoja na
Lambda, ElastiCache, CloudSearch,

2367
01:44:45,600 --> 01:44:49,890
kushinikiza data kutoka ndani ya Elastic
MapReduce, kuagiza nje kutoka DynamoDB

2368
01:44:49,890 --> 01:44:52,370
ndani ya S3, kila aina ya workflows.

2369
01:44:52,370 --> 01:44:54,120
Lakini pengine ni bora
Jambo kuzungumzia,

2370
01:44:54,120 --> 01:44:56,119
na hii ni nini kweli
kuvutia ni wakati sisi

2371
01:44:56,119 --> 01:44:58,350
majadiliano juu ya maombi tukio inaendeshwa.

2372
01:44:58,350 --> 01:45:00,300
>> Huu ni mfano wa
Mradi wa ndani

2373
01:45:00,300 --> 01:45:04,850
kwamba tuna ambapo sisi ni kweli
kuchapisha kukusanya matokeo ya utafiti.

2374
01:45:04,850 --> 01:45:07,700
Hivyo katika barua pepe kiungo kwamba
sisi kutuma nje, kuna itabidi

2375
01:45:07,700 --> 01:45:11,350
kuwa ni kidogo kiungo akisema click
hapa kujibu utafiti.

2376
01:45:11,350 --> 01:45:14,070
Na wakati Clicks mtu
kiungo kwamba, kile kinachotokea

2377
01:45:14,070 --> 01:45:18,020
ni wao kubomoa salama
HTML utafiti fomu kutoka S3.

2378
01:45:18,020 --> 01:45:18,980
Hakuna server.

2379
01:45:18,980 --> 01:45:20,600
Hii ni S3 kitu.

2380
01:45:20,600 --> 01:45:22,770
>> Fomu kuja juu,
mizigo juu katika browser.

2381
01:45:22,770 --> 01:45:24,240
Ni got uti wa mgongo.

2382
01:45:24,240 --> 01:45:30,160
Ni got ngumu JavaScript
kwamba ni mbio.

2383
01:45:30,160 --> 01:45:33,557
Hivyo ni maombi tajiri sana
mbio katika browser mteja.

2384
01:45:33,557 --> 01:45:36,390
Hawajui kwamba wao siyo
mazungumzo na nyuma mwisho server.

2385
01:45:36,390 --> 01:45:38,220
Katika hatua hii, ni kisakuzi wote.

2386
01:45:38,220 --> 01:45:41,780
>> Wao kuchapisha matokeo ya kile
tunatoa wito Amazon API Gateway.

2387
01:45:41,780 --> 01:45:46,270
API Gateway ni tu mtandao API
kwamba unaweza kufafanua na hook up

2388
01:45:46,270 --> 01:45:47,760
kwa chochote unataka.

2389
01:45:47,760 --> 01:45:50,990
Katika kesi hii, tuko
yatakuwapo hadi kazi Lambda.

2390
01:45:50,990 --> 01:45:54,797
>> Hivyo POST operesheni yangu ni
kinachotokea na hakuna kompyuta.

2391
01:45:54,797 --> 01:45:56,380
Kimsingi kwamba API Gateway anakaa huko.

2392
01:45:56,380 --> 01:45:58,770
Ni gharama mimi kitu mpaka watu
kuanza posting yake, sawa?

2393
01:45:58,770 --> 01:46:00,269
Kazi Lambda anakaa tu pale.

2394
01:46:00,269 --> 01:46:03,760
Na ni gharama mimi kitu mpaka
watu kuanza kupiga yake.

2395
01:46:03,760 --> 01:46:07,270
Hivyo unaweza kuona, kama kiasi
ongezeko, kwamba wakati mashtaka kuja.

2396
01:46:07,270 --> 01:46:09,390
Mimi si mbio server 24/7.

2397
01:46:09,390 --> 01:46:12,310
>> Hivyo mimi kuvuta fomu
chini nje ya ndoo,

2398
01:46:12,310 --> 01:46:15,719
na mimi baada ya kupitia API
Gateway katika kazi Lambda.

2399
01:46:15,719 --> 01:46:17,510
Na kisha Lambda
kazi anasema, unajua

2400
01:46:17,510 --> 01:46:20,600
nini, mimi nimepata baadhi PIIs, baadhi
binafsi zinazotambulika

2401
01:46:20,600 --> 01:46:21,480
katika majibu hayo.

2402
01:46:21,480 --> 01:46:23,020
I got maoni kutoka kwa watumiaji.

2403
01:46:23,020 --> 01:46:24,230
Mimi nimepata anwani ya barua pepe.

2404
01:46:24,230 --> 01:46:26,190
Mimi nimepata majina ya watumiaji.

2405
01:46:26,190 --> 01:46:27,810
>> Napenda umegawanyika hii mbali.

2406
01:46:27,810 --> 01:46:30,280
Mimi nina kwenda kuzalisha baadhi
metadata mbali rekodi hii.

2407
01:46:30,280 --> 01:46:32,850
Na mimi nina kwenda kushinikiza
metadata ndani ya DynamoDB.

2408
01:46:32,850 --> 01:46:36,059
Na mimi naweza encrypt data zote
na kuiondoa katika DynamoDB kama nataka.

2409
01:46:36,059 --> 01:46:38,600
Lakini ni rahisi kwa ajili yangu, katika hili
kutumia kesi, kwa kwenda mbele kusema,

2410
01:46:38,600 --> 01:46:42,800
Mimi nina kwenda kushinikiza takwimu ghafi
ndani ya encrypted S3 ndoo.

2411
01:46:42,800 --> 01:46:47,240
Hivyo mimi kutumia kujengwa katika S3 server upande
encryption na Amazon muhimu Management

2412
01:46:47,240 --> 01:46:51,600
Huduma ili niweze kuwa muhimu ambayo
unaweza mzunguko juu ya kipindi mara kwa mara,

2413
01:46:51,600 --> 01:46:55,010
na siwezi kulinda kwamba data PII
kama sehemu ya workflow hili lote.

2414
01:46:55,010 --> 01:46:55,870
>> Kwa hiyo kile Nimefanya nini?

2415
01:46:55,870 --> 01:47:00,397
Nimekuwa tu uliotumika nzima
maombi, na mimi sina server.

2416
01:47:00,397 --> 01:47:02,980
Kwa hiyo kile ni tukio inaendeshwa maombi
usanifu gani kwa ajili yenu.

2417
01:47:02,980 --> 01:47:05,730
>> Sasa kama unadhani kuhusu
matumizi ya kesi kwa Haya

2418
01:47:05,730 --> 01:47:08,730
tuna wateja wengine Mimi kuzungumza
kwa kuhusu hili usanifu halisi ambao

2419
01:47:08,730 --> 01:47:14,560
kuendesha kampeni phenomenally kubwa, ambaye
ni kuangalia hii na kwenda, oh wangu.

2420
01:47:14,560 --> 01:47:17,840
Kwa sababu sasa, wanaweza
kimsingi kuiondoa huko nje,

2421
01:47:17,840 --> 01:47:21,900
basi kampeni kwamba kukaa tu
kuna mpaka yazindua, na si

2422
01:47:21,900 --> 01:47:24,400
kuwa na wasiwasi kuhusu mitini
ni aina gani ya miundombinu

2423
01:47:24,400 --> 01:47:26,120
ni kwenda kuwa kuna kusaidia yake.

2424
01:47:26,120 --> 01:47:28,600
Na kisha kwa haraka kama
kampeni kwamba ni kosa,

2425
01:47:28,600 --> 01:47:31,520
ni kama miundombinu
tu mara moja huenda zake

2426
01:47:31,520 --> 01:47:33,680
kwa sababu kuna kweli
hakuna miundombinu.

2427
01:47:33,680 --> 01:47:35,660
Ni tu kificho kwamba yapo juu ya Lambda.

2428
01:47:35,660 --> 01:47:38,560
Ni tu data kwamba yapo katika DynamoDB.

2429
01:47:38,560 --> 01:47:41,340
Ni njia ya ajabu
kujenga maombi.

2430
01:47:41,340 --> 01:47:43,970
>> Watazamaji: Hivyo ni zaidi
ephemeral kuliko itakuwa

2431
01:47:43,970 --> 01:47:45,740
kama ilikuwa kuhifadhiwa kwenye kompyuta halisi?

2432
01:47:45,740 --> 01:47:46,823
>> RICK Houlihan: Ndiyo.

2433
01:47:46,823 --> 01:47:49,190
Kwa sababu hiyo mfano server
bila kuwa 24/7.

2434
01:47:49,190 --> 01:47:51,954
Ina kuwa inapatikana kwa
mtu wa kujibu.

2435
01:47:51,954 --> 01:47:52,620
Naam nadhani nini?

2436
01:47:52,620 --> 01:47:55,410
S3 inapatikana 24/7.

2437
01:47:55,410 --> 01:47:57,100
S3 daima anajibu.

2438
01:47:57,100 --> 01:47:59,320
Na S3 ni sana, vizuri sana
katika kuwahudumia up vitu.

2439
01:47:59,320 --> 01:48:02,590
Wale vitu inaweza kuwa mafaili ya HTML, au
JavaScript mafaili, au chochote unataka.

2440
01:48:02,590 --> 01:48:07,430
Unaweza kuendesha maombi tajiri sana mtandao
nje ya S3 ndoo, na watu kufanya.

2441
01:48:07,430 --> 01:48:10,160
>> Na hivyo hiyo ni wazo hapa
ni kupata mbali na njia

2442
01:48:10,160 --> 01:48:11,270
sisi tukidhani kuhusu hilo.

2443
01:48:11,270 --> 01:48:14,270
Sote tukidhani katika
suala la watumishi na majeshi.

2444
01:48:14,270 --> 01:48:16,580
Siyo kuhusu kwamba tena.

2445
01:48:16,580 --> 01:48:19,310
Ni kuhusu miundombinu kama kanuni.

2446
01:48:19,310 --> 01:48:22,470
Kupeleka kificho kwa wingu na
basi wingu kukimbia kwa ajili yenu.

2447
01:48:22,470 --> 01:48:24,980
Na kwamba ni nini AWS ni kujaribu kufanya.

2448
01:48:24,980 --> 01:48:29,690
>> Watazamaji: Hivyo sanduku dhahabu yako katikati
ya API Gateway si server-kama,

2449
01:48:29,690 --> 01:48:30,576
lakini badala yake ni just--

2450
01:48:30,576 --> 01:48:32,850
>> RICK Houlihan: Unaweza kufikiri
yake kama server facade.

2451
01:48:32,850 --> 01:48:38,040
Wote ni ni itabidi kuchukua HTTP
kuomba na ramani yake kwa mchakato mwingine.

2452
01:48:38,040 --> 01:48:39,192
Hayo ni yote ni gani.

2453
01:48:39,192 --> 01:48:41,525
Na katika kesi hii, sisi ni kuchora ramani
kwa kazi Lambda.

2454
01:48:41,525 --> 01:48:44,119

2455
01:48:44,119 --> 01:48:45,410
Haki wote, hivyo kwamba wote I got.

2456
01:48:45,410 --> 01:48:46,190
Asante sana.

2457
01:48:46,190 --> 01:48:46,800
Nashukuru.

2458
01:48:46,800 --> 01:48:48,100
Najua tunataka kidogo baada ya muda.

2459
01:48:48,100 --> 01:48:49,980
Na pengine nyie got
kidogo ya maelezo

2460
01:48:49,980 --> 01:48:51,410
uweze kuchukua mbali leo.

2461
01:48:51,410 --> 01:48:53,520
Na mimi kuomba msamaha kama nilikwenda
juu ya baadhi ya vichwa vyenu,

2462
01:48:53,520 --> 01:48:56,697
lakini kuna mengi mazuri ya
msingi maarifa ya msingi

2463
01:48:56,697 --> 01:48:58,280
nadhani ni muhimu sana kwa ajili yenu.

2464
01:48:58,280 --> 01:48:59,825
Kwa hiyo asante kwa kuwa mimi.

2465
01:48:59,825 --> 01:49:00,325
[Makofi]

2466
01:49:00,325 --> 01:49:02,619
Watazamaji: [inaudible]
ni wakati walikuwa wakisema

2467
01:49:02,619 --> 01:49:05,160
alikuwa na kwenda kwa njia ya kitu
kuanzia mwanzo hadi mwisho

2468
01:49:05,160 --> 01:49:07,619
kupata maadili ya haki
au maadili huo huo,

2469
01:49:07,619 --> 01:49:09,410
jinsi gani maadili
kubadilika kama [inaudible].

2470
01:49:09,410 --> 01:49:10,480
>> RICK Houlihan: Oh, idempotent?

2471
01:49:10,480 --> 01:49:11,800
Jinsi gani maadili kubadilika?

2472
01:49:11,800 --> 01:49:15,180
Naam, kwa sababu kama mimi si kukimbia
ni njia yote hadi mwisho,

2473
01:49:15,180 --> 01:49:19,770
kisha sijui nini mabadiliko
yalifanywa katika maili ya mwisho.

2474
01:49:19,770 --> 01:49:22,144
Ni si kwenda kuwa
data huo kama nini nikaona.

2475
01:49:22,144 --> 01:49:24,560
Watazamaji: Oh, hivyo wewe tu
si wamezipata pembejeo nzima.

2476
01:49:24,560 --> 01:49:24,770
RICK Houlihan: Haki.

2477
01:49:24,770 --> 01:49:26,895
Una kwenda tangu mwanzo
hadi mwisho, na kisha ni

2478
01:49:26,895 --> 01:49:29,280
kwenda kuwa hali thabiti.

2479
01:49:29,280 --> 01:49:31,520
Baridi.

2480
01:49:31,520 --> 01:49:35,907
>> Watazamaji: Hivyo wewe alituonyesha DynamoDB
anaweza kufanya hati au ufunguo thamani.

2481
01:49:35,907 --> 01:49:38,740
Na sisi alitumia muda mwingi juu ya
thamani muhimu na hash na njia

2482
01:49:38,740 --> 01:49:40,005
flip ni kuzunguka.

2483
01:49:40,005 --> 01:49:43,255
Wakati inaonekana katika meza hizo, ni kwamba
kuacha nyuma mbinu hati?

2484
01:49:43,255 --> 01:49:44,600
>> RICK Houlihan: napenda
kusema kuiacha nyuma.

2485
01:49:44,600 --> 01:49:45,855
>> Watazamaji: Walikuwa kutengwa na the--

2486
01:49:45,855 --> 01:49:49,140
>> RICK Houlihan: Kwa hati
mbinu, aina hati katika DynamoDB

2487
01:49:49,140 --> 01:49:50,880
ni kufikiri tu ya kama sifa nyingine.

2488
01:49:50,880 --> 01:49:53,560
Ni sifa ambayo ina
kihierarkia data muundo.

2489
01:49:53,560 --> 01:49:56,980
Na kisha katika maswali,
unaweza kutumia mali

2490
01:49:56,980 --> 01:49:59,480
ya vitu wale kutumia Object nukuu.

2491
01:49:59,480 --> 01:50:03,562
Hivyo siwezi kuchuja juu ya nested
mali ya JSON hati.

2492
01:50:03,562 --> 01:50:05,520
Watazamaji: Hivyo yoyote mimi wakati
kufanya mbinu hati,

2493
01:50:05,520 --> 01:50:07,906
Siwezi aina ya kuwasili katika tabular--

2494
01:50:07,906 --> 01:50:08,780
Watazamaji: Kabisa.

2495
01:50:08,780 --> 01:50:09,800
Watazamaji: --indexes na
mambo tu kuongelea.

2496
01:50:09,800 --> 01:50:11,280
RICK Houlihan: Yeah,
bahati na yote hayo,

2497
01:50:11,280 --> 01:50:13,363
wakati unataka ripoti
mali ya JSON,

2498
01:50:13,363 --> 01:50:18,230
njia ambayo tunatarajia kuwa kufanya hivyo ni kama
kuingiza JSON kitu au hati

2499
01:50:18,230 --> 01:50:20,780
ndani ya Dynamo, ungependa kutumia mito.

2500
01:50:20,780 --> 01:50:22,400
Mito bila kusoma pembejeo.

2501
01:50:22,400 --> 01:50:24,340
Wewe Ningependa kupata kwamba JSON
kitu na wewe d kusema sawa,

2502
01:50:24,340 --> 01:50:26,030
nini mali nataka ripoti?

2503
01:50:26,030 --> 01:50:28,717
>> Wewe kujenga meza derivative.

2504
01:50:28,717 --> 01:50:30,300
Sasa hiyo ni njia ni kazi hivi sasa.

2505
01:50:30,300 --> 01:50:32,650
Hatuna kuruhusu ripoti
moja kwa moja wale mali.

2506
01:50:32,650 --> 01:50:33,520
>> Watazamaji: Tabularizing hati yako.

2507
01:50:33,520 --> 01:50:36,230
>> RICK Houlihan: Hasa, flattening
hivyo, tabularizing hilo, hasa.

2508
01:50:36,230 --> 01:50:37,415
Hiyo ni nini cha kufanya na hayo.

2509
01:50:37,415 --> 01:50:37,860
>> Watazamaji: Asante.

2510
01:50:37,860 --> 01:50:39,609
>> RICK Houlihan: Yep,
kabisa, asante.

2511
01:50:39,609 --> 01:50:42,240
Watazamaji: Hivyo ni aina ya
Mongo hukutana Redis classifers.

2512
01:50:42,240 --> 01:50:43,990
>> RICK Houlihan: Yeah,
ni mengi kama hayo.

2513
01:50:43,990 --> 01:50:45,940
Hiyo ni maelezo mazuri kwa ajili yake.

2514
01:50:45,940 --> 01:50:47,490
Baridi.

2515
01:50:47,490 --> 01:50:49,102