Databases on AWS Explained RDS vs DynamoDB SQL vs NoSQL AWS Cloud Practitioner Day 13 — Transcript

Full transcript

1. 0:00Welcome back cloud builders. Day 13 is
2. 0:02here. All right, today we are tackling
3. 0:05databases. And let's be honest, if you
4. 0:06are brand new to tech, the world
5. 0:07database sounds pretty boring. But
6. 0:09here's the thing. Data is literally the
7. 0:11lifeblood of everything we do. Every app
8. 0:14you use, every game you play, every
9. 0:15purchase you make, it all lives in the
10. 0:17database somewhere. When you look at AWS
11. 0:20though, it gets confusing fast. You
12. 0:21would think they would just give us one
13. 0:23AWS database and call it a day. Nope.
14. 0:27They have over 15 different database
15. 0:29services. Why? Because you wouldn't use
16. 0:32a sports car to haul a load of bricks,
17. 0:34right? AWS gives you different engines
18. 0:37for different type of jobs.
19. 0:39Today we are going to cut through all
20. 0:41the jargon. By the end of this video,
21. 0:43you won't just know what NoSQL or ACID
22. 0:45means. You will know exactly which AWS
23. 0:47database to pick for your exam
24. 0:48scenarios. So, let's get into it.
25. 0:52Here's the game plan for today.
26. 0:54First we are going to settle the oldest
27. 0:56argument in the tech that is SQL versus
28. 0:58NoSQL. What do those weird acronyms
29. 1:00actually mean and how do they store your
30. 1:02data. Then we will look at Amazon RDS.
31. 1:06I'm going to show you the biggest trick
32. 1:08question of the cloud practitioner exam.
33. 1:10It involves two things called
34. 1:11multi-agents and read replicas. AWS
35. 1:15loves trying to trip you up on them.
36. 1:17After that we will talk about Dynamob
37. 1:19which is AWS golden child for serverless
38. 1:22apps. We will hit a few specialized
39. 1:24tools like red shift and elastic catch
40. 1:26and finally we'll jump into AWS console
41. 1:28to spin up a real database. Stick around
42. 1:30to the end because we are doing a live
43. 1:32pop quiz today.
44. 1:34Okay, let's start with the basics. In
45. 1:37the cloud world, you basically have two
46. 1:39flavors of databases.
47. 1:41One is relational which we call SQL and
48. 1:44the another one is non relational which
49. 1:48we call NoSQL.
50. 1:50Let's look at relational that is SQL.
51. 1:53Honestly, just picture a massive super
52. 1:55strict Microsoft Excel sheet. It has
53. 1:58rows, it has columns. If your users
54. 2:00table has columns for first name, last
55. 2:02name, and email, and you try to add a
56. 2:04user but accidentally type their
57. 2:06favorite color instead of an email, the
58. 2:09database will literally throw an error
59. 2:10and say no. It is incredibly strict. And
60. 2:14you will see the word acid on the exam.
61. 2:16Asset is just a fancy acronym that means
62. 2:19guaranteed reliability. Think about
63. 2:21transferring $100 to a friend and you
64. 2:23want an absolute guarantee that $100
65. 2:25leaves your bank account and arrives in
66. 2:27there. If your Wi-Fi cuts halfway
67. 2:29through, an acid database cancels the
68. 2:32whole thing. No missing money on AWS.
69. 2:34Your go-to services here are Amazon RDS
70. 2:37and Amazon Aurora.
71. 2:39Now, what about NoSQL? Toss the
72. 2:42spreadsheet out the window. NoSQL
73. 2:44databases are all about flexibility and
74. 2:46speed. You will hear the term key value.
75. 2:50What does that mean? Imagine going to a
76. 2:53restaurant and checking your winter
77. 2:54coat. The host give you a ticket with a
78. 2:56number 42. That is your key. When you
79. 3:00leave, you hand them the key and they
80. 3:02hand you you a code. That is the value.
81. 3:04The database doesn't care if your code
82. 3:06is a red jacket or a blue sweater or a
83. 3:08scarf, anything. It just links a key to
84. 3:10a value and it is incredibly simple and
85. 3:13fast. Talking about when to use NoSQL.
86. 3:17So when you have a massive scale and you
87. 3:19don't want strict roles, think of a
88. 3:21gaming leaderboard or an IoT thermometer
89. 3:23sending data every second. On AWS, your
90. 3:26main NoSQL service is Amazon Dynamob.
91. 3:30Even the platform you are using now is
92. 3:31using Dynamo DB.
93. 3:34Now grab a highlighter because this is
94. 3:36the biggest trap on the exam. When you
95. 3:38use Amazon RDS, there are two features
96. 3:40that sound kind of similar. Multi-AZ and
97. 3:43read replicas.
98. 3:46Let's start with multiple AZ. This
99. 3:49stands for multiple availability jones.
100. 3:53Think of it exactly like a backup
101. 3:54generator at a hospital. It maintains a
102. 3:56synchronous copy of your database in
103. 3:58another building. Synchronous simply
104. 4:00means that your data saves in both the
105. 4:02buildings at the exact same millisecond.
106. 4:05But here's the catch. That backup
107. 4:07generator does nothing under the normal
108. 4:09conditions. It just sits there waiting.
109. 4:12If your main database catches on fire,
110. 4:14AWS automatically flips the switch to
111. 4:16the backup so that your application
112. 4:18doesn't go offline.
113. 4:20Remember this multiple AZ is strictly
114. 4:23for high availability and disaster
115. 4:25recovery.
116. 4:27Now read replicas. Imagine your database
117. 4:30is a famous author and millions of
118. 4:32people are asking them to read their old
119. 4:34books. The author gets overwhelmed and
120. 4:37so you create a synchronous clones of
121. 4:39the author. A synchronous means there
122. 4:41might be a split-second delay in copying
123. 4:43the data but now those clones can handle
124. 4:46all the readers. Your main database is
125. 4:48freed up to just write new data.
126. 4:52Remember this read replicas are strictly
127. 4:54for read performance.
128. 4:57If the AWS ask you how to survive a
129. 4:59failure, pick multi- aents.
130. 5:03And if they ask how to speed up a
131. 5:05database crushed by real traffic, pick
132. 5:08read replica.
133. 5:09All right. Now, let's take a quick look
134. 5:11at Amazon Aurora that is the Ferrari. Uh
135. 5:15Aurora is AWS customuilt relational
136. 5:17database. If RDS is reliable Toyota,
137. 5:20Aurora is a Formula 1 race car. It is up
138. 5:23to five times faster than the standard
139. 5:25MySQL. If an exam question asks for the
140. 5:28highest performance manage MySQL
141. 5:29database, they want you to pick Aurora.
142. 5:33All right, you can read this. And now
143. 5:37let's talk about the NoSQL king that is
144. 5:39Amazon Dynamo DB. I personally love this
145. 5:43service as well. Dynamob is fully
146. 5:46serverless. You don't manage any EC2
147. 5:47instances. You don't install updates or
148. 5:50you don't have to buy hard drives. You
149. 5:52just say create table and you are ready
150. 5:54to go.
151. 5:56Its biggest flex is speed. It gives you
152. 5:59singledigit millisecond latency. It
153. 6:02doesn't matter if you have 10 users or
154. 6:04if you are using Netflix handling
155. 6:05millions of users on Friday night. It
156. 6:08responds in milliseconds. Watch out for
157. 6:10these two Dynamob subtopics.
158. 6:13DAX and pricing models.
159. 6:16What if milliseconds are too slow for
160. 6:18your app? You need microsconds.
161. 6:21Then you use Dex Dynamo DB accelerator.
162. 6:26It's an inmemory cache that basically
163. 6:28preloads the answer to the common
164. 6:30question so that Dynamo DB doesn't even
165. 6:32have to think. The another one is
166. 6:34pricing modes. How do we pay for it? You
167. 6:38used provisioned capacity if your
168. 6:39traffic is steady and predictable. You
169. 6:42tell AWS give me 100 reads per second.
170. 6:46We have on demand capacity as well. and
171. 6:48you use on demand capacity if your app
172. 6:51might randomly go viral overnight and
173. 6:53you just want to pay per click.
174. 6:56AWS has few specialized databases for
175. 6:59the practitioner exam. You really just
176. 7:00need to play a matching game with the
177. 7:02buzzwords.
178. 7:03Amazon Red Shift. This is a data
179. 7:06warehouse. You don't use this to process
180. 7:08a single coffee purchase. You use this
181. 7:10to analyze 10 years of coffee purchases
182. 7:12across the entire world to see what
183. 7:14flavor is trending. It handles pabytes
184. 7:16of data.
185. 7:18Watch out for the red shift spectrum.
186. 7:20It's a magic feature that lets you
187. 7:22analyze data sitting in an S3 bucket
188. 7:24without even loading it into the red
189. 7:26shift first. The next we have Amazon
190. 7:29elastic catch. From the name itself, it
191. 7:33is clear this is an in-memory catch. It
192. 7:36takes the strain of your main database.
193. 7:38The exam might ask you to choose between
194. 7:40its two engines radius and memcatched.
195. 7:44Memc is super simple and radius is the
196. 7:46advanced one. It supports complex data
197. 7:49types and can save its state.
198. 7:52The next database service is Amazon
199. 7:54Neptune. Think of the Roman god of the
200. 7:56sea. Neptune is a graph database. It's
201. 7:59all about relationships. If an exam
202. 8:02question mentions social networks,
203. 8:04friends of friends, or fraud detection,
204. 8:06it's Neptune.
205. 8:09The next one is Amazon document DB. Very
206. 8:12simple. If a company uses MongoDB on
207. 8:14premise and wants to move to AWS, they
208. 8:17use document DB.
209. 8:19Okay, let's log this in. Take a
210. 8:21screenshot of this cheat sheet. Let's
211. 8:23see. Traditional application, SQL
212. 8:25application with asset transactions and
213. 8:27complex joins. The service is RDS.
214. 8:32Crazy fast enterprise MySQL. What is
215. 8:35that? Aurora.
216. 8:37We have millisecond latency, serverless,
217. 8:39flexible schema and massive scale.
218. 8:42Dynamo DB
219. 8:45analytics and pabytes of history. We use
220. 8:48red shift speed up read heavy workloads.
221. 8:51Reduce database query load. Radius or
222. 8:54mecatch catching elastic catch.
223. 8:57Graphing a social network that is social
224. 8:59network graph reversal, fraud detection,
225. 9:01relationship queries that is Neptune.
226. 9:05All right.
227. 9:07All right, it's time for our hands-on
228. 9:09lab. But before we open the AWS console
229. 9:12and start clicking buttons, we need to
230. 9:13understand what we are actually
231. 9:14building.
232. 9:16Think about it. Where does Instagram
233. 9:19store your username and password? A
234. 9:20database. Where does your Amazon store
235. 9:23your order history? That's also
236. 9:25database.
237. 9:27So literally everything you interact
238. 9:29with on the internet uses a database.
239. 9:31Today we are going to build a live MySQL
240. 9:33database in AWS. But why use AWS for
241. 9:36this?
242. 9:37See here, like in traditional IT world,
243. 9:40if you want a database, it was a
244. 9:43nightmare.
245. 9:44You had to buy physical server
246. 9:47then install Linux operating system
247. 9:51manually install the SQL software
248. 9:56figure out how to do uh own backups own
249. 9:58daily backups
250. 10:01install security updates at 2 a.m. on
251. 10:03the Sunday and somehow figure out how to
252. 10:05add more hard drive space without
253. 10:06breaking everything. It took weeks of
254. 10:09planning.
255. 10:11See on the right side we have Amazon
256. 10:12RDS. Here comes Amazon RDS that is
257. 10:15relational database service. With RDS
258. 10:18you literally just click create and AWS
259. 10:20handles the operating system the
260. 10:22installation the backups and the
261. 10:23security patches and also the hardware.
262. 10:26You just get an endpoint that is a
263. 10:28connection string and you start writing
264. 10:29data. It is magical. So let's go build
265. 10:32one.
266. 10:33All right. I am here in the AWS console.
267. 10:36Simply I will go in the search bar and
268. 10:38search for RDS. You can see I will open
269. 10:41it and yeah now click on this uh big
270. 10:45orange create database button and yeah
271. 10:47you can select full configuration. So we
272. 10:50will be using this uh full configuration
273. 10:53because for learning for job interviews
274. 10:54and for your cloud practitioner exams
275. 10:56not only cloud practitioner but
276. 10:58certification exams we always we always
277. 11:00use this full configuration. All right
278. 11:03and now we can see that we have engine
279. 11:05options. This is where we pick our
280. 11:08database engine. Let's slow down here
281. 11:10because this is where most tutorials
282. 11:12just say pick MySQL and move on. I want
283. 11:14you to actually understand your choices.
284. 11:17We have MySQL. This is probably the
285. 11:19world's most popular opensource
286. 11:21database. It is used by WordPress,
287. 11:23Shopify and millions of businesses. So
288. 11:25for today's lab, we will select this one
289. 11:27only. And we have Postgra SQL that is
290. 11:29think of it like MySQL smarter cousin.
291. 11:32It is more advanced and it has better
292. 11:34complex analytics. also has very uh
293. 11:37heavy enterprise features. Talking about
294. 11:40Mariab, this is the basically
295. 11:41communitydriven fork of MySQL and they
296. 11:44are incredibly similar.
297. 11:46The next we have Oracle, Microsoft SQL
298. 11:48Server, IBM DV2. You will see these
299. 11:51three massive enterprise giants here. If
300. 11:53a huge legacy bank or government agency
301. 11:55is migrating to the cloud, they use
302. 11:57these. They are incredibly powerful but
303. 11:59very expensive. And finally, we have
304. 12:02Amazon Aurora. This is MySQL compatible
305. 12:05as well as Postcreensql compatible.
306. 12:07Aurora deserves a massive spotlight. It
307. 12:09isn't completely different coding
308. 12:11language. AWS basically took the code
309. 12:13for MySQL and PostgreSQL, ribbed it
310. 12:15apart and rebuilt it specifically for
311. 12:17the cloud. So it runs up to the five
312. 12:19times faster.
313. 12:22And if the exam ask you like which is
314. 12:24the highest performance managed MySQL
315. 12:26database, the answer is always Aurora.
316. 12:29For today's lab, make sure MySQL is
317. 12:31selected.
318. 12:33So for database creation method we will
319. 12:35select full configuration and then uh we
320. 12:38have templates
321. 12:40there are three templates that
322. 12:42production dev test and free tier.
323. 12:44Production gives you the highest
324. 12:46availability the best performance and
325. 12:47the highest cost as well. The dev test
326. 12:50is cheaper with less redundancy used by
327. 12:53programmers to safely test code. and the
328. 12:56free tier. Yes, it is absolute that it
329. 12:58is it will give you the smallest
330. 12:59database designed purely for learning
331. 13:01and hands-on experience. So let's click
332. 13:03on free tier for now. Watch what
333. 13:06happened right below when we clicked
334. 13:07free tier. The availability and
335. 13:09durability section is now locked to the
336. 13:11single a DB instance. Normally in
337. 13:13production you would choose a multi-AZ
338. 13:15deployment. Remember our lesson multi- A
339. 13:18means AWS spins up a second synchronous
340. 13:21backup server in another building to
341. 13:23save you if the data center goes down.
342. 13:25But AWS is generous, not crazy. Uh they
343. 13:28aren't going to give you two servers
344. 13:29running 24x7 for free. So the free tier
345. 13:32locks us into the single AZ only. For
346. 13:35the engine version, uh let us use the
347. 13:37default that is MySQL 8.4.8
348. 13:40currently and move on. Now we have DB
349. 13:43instance identifier. By default, it says
350. 13:46database 1. Don't get confused. This is
351. 13:48not the name of your actual database
352. 13:50tables. This is just the name of the
353. 13:52server holding it. So let's change this
354. 13:54to something meaningful like student DB
355. 13:59and then uh we have credential setting.
356. 14:03This is the administrator account for
357. 14:05your database exactly like the root user
358. 14:06on the Linux computer. Type in admin as
359. 14:09the master name that is master username.
360. 14:12And now AWS ask for credentials manager.
361. 14:15This is the cool new feature. Do you
362. 14:17want it like managed in AWS secret
363. 14:20manager or self-manage? Secrets manager
364. 14:23is amazing for big companies because it
365. 14:25automatically rotates the password so
366. 14:26hackers can't guess them but it's cost
367. 14:29extra money.
368. 14:31Since this is a free lab, select
369. 14:32self-managed, uncheck autogenerate
370. 14:34password and type in a secure password
371. 14:36yourself. Write this password down
372. 14:38because uh AWS also cannot recover it
373. 14:40once you forget it. And the next uh you
374. 14:44can select addential credential setting
375. 14:45as password authentication. Okay. And
376. 14:48then we have instance configuration.
377. 14:51In instance class notice AWS has
378. 14:53selected bust table classes that
379. 14:55includes T classes and it has selected
380. 14:57me DBT4G
381. 14:59domicro for now. This is exactly like
382. 15:02the EC2 instance type we learned about
383. 15:03it. It dictates how much CPU and the RAM
384. 15:06your database gets. A micro instance
385. 15:08gives us 2 vCPUs and 1 GB of RAM. And by
386. 15:12the way, do you know that the G in T4G
387. 15:14stands for Graviton? Graviton is AWS
388. 15:16custom super efficient processors
389. 15:19because we picked free tier. AWS locks
390. 15:21us into this micro size so we don't
391. 15:24accidentally run up a massive bill.
392. 15:26So for now storage type let us select
393. 15:29general purpose SSD that is GP2 and the
394. 15:33allocated storage is at 2 GB. All right
395. 15:37let's let us uh keep it default. Now
396. 15:39look right below the storage
397. 15:41autoscaling. Imagine you write some bad
398. 15:43code and your app accidentally creates
399. 15:45millions of junk records. Your 20 GB
400. 15:48fills up. Without autoscaling, your
401. 15:49database will crash. And with
402. 15:51autoscaling enabled, AWS says, "Oh, your
403. 15:54hard drive is full. Let me automatically
404. 15:55buy you a more space up to that maximum
405. 15:58threshold of that." Let's say I have
406. 16:00kept 1,000 GB. So it will uh scale up to
407. 16:03the,000 GB so you don't crash. It is an
408. 16:06amazing feature for a production
409. 16:07company, but for our free tier, it's a
410. 16:09trap. If a bug triggers autoscaling, AWS
411. 16:12will charge your credit card for that
412. 16:13extra space. So, uncheck this enable
413. 16:16storage autoscaling. And we have
414. 16:18connectivity section. For uh this uh see
415. 16:22AWS ask whether to connect to an EC2
416. 16:24computer source or not connect. For now,
417. 16:27we will select do not connect to ENC2
418. 16:30instance. This is a wizard feature that
419. 16:32automatically links a web server to your
420. 16:34database. But we want to understand how
421. 16:36our architecture works. So let's keep uh
422. 16:39don't connect checked. And then we have
423. 16:41VPC. Uh also we have DB subnet group.
424. 16:45This is exactly what we learned
425. 16:46yesterday in day 12. We will just leave
426. 16:48it on our default VPC. Pay extremely
427. 16:51close attention to public access. It
428. 16:52gives you choice yes or no. So let me
429. 16:55know what do you think about it. Should
430. 16:56a database ever be directly accessible
431. 16:58from the public internet? No. See hacker
432. 17:03is an automated bot that scan public IP
433. 17:05addresses all day long looking for open
434. 17:07databases. Your architecture should
435. 17:09always be the internet talks to a web
436. 17:12server in a public subnet and your web
437. 17:14server talks to a database in a private
438. 17:16subnet. Let me draw this. See you this
439. 17:19is your internet and this is your web
440. 17:21server and you have database.
441. 17:24So uh the internet talks to your web
442. 17:26server and your web server talks to the
443. 17:28database and this is in the private
444. 17:30subnet. The internet should never talk
445. 17:33directly to your database. So we must
446. 17:35leave this public access as no. For the
447. 17:38VPC security group we just choose
448. 17:41existing and leave it on default.
449. 17:44And scroll past RDS proxy and
450. 17:47certificate authority. Leave them as
451. 17:48default. They are advanced enterprise
452. 17:50features. And under monitoring AWS
453. 17:54offers database insights. Keep it on
454. 17:57standard
455. 17:58also expand this additional monitoring
456. 18:00setting. And yeah you can see that make
457. 18:03sure this enabled enhanced monitoring is
458. 18:05unchecked so we stay safely inside the
459. 18:07free tier. Now at the very bottom you
460. 18:10have this additional configuration tab.
461. 18:12Expand this and you will see backup.
462. 18:16You can choose uh anything like how much
463. 18:18days do you want the retention period
464. 18:20you want to enable automated backup or
465. 18:22not. You can choose the backup window as
466. 18:25well like the daily time range uh in
467. 18:27which the RDS takes automatic backup. So
468. 18:29with this backup what AWS does is it
469. 18:32takes point in time snapshot of your
470. 18:34data every single day without you
471. 18:36lifting a finger. Scroll down to
472. 18:38maintenance section you will see enable
473. 18:40auto minor version upgrade. checked. And
474. 18:43this is great because if MySQL release a
475. 18:45tiny security patch, AWS install it
476. 18:47automatically for you during the
477. 18:49maintenance window. But look at the very
478. 18:51last check box, enable deletion
479. 18:53protection. Make sure this is unchecked.
480. 18:56If you check this, AWS literally blocks
481. 18:58you from deleting the database. It's a
482. 19:01fantastic safety net for a real company,
483. 19:02but terrible for our lab like where we
484. 19:05need to clean up resource and stop our
485. 19:06billing later. Now I will click on
486. 19:09create database. Do not skip or stop the
487. 19:12video. Look at the status. It says
488. 19:13creating. What is actually happening in
489. 19:15the cloud right now? Behind the scenes,
490. 19:17AWS is finding a physical server rack,
491. 19:20allocating a virtual machine, then
492. 19:22attaching a 20 GB SSD hard drive to it,
493. 19:25and installing a Linux operating system,
494. 19:27downloading MySQL in it, and configuring
495. 19:29your admin password as well. Then it set
496. 19:32up uh your network security groups, and
497. 19:34it generates a web address for you to
498. 19:36connect to. If you did this manually, it
499. 19:38would take a whole weekend. AWS does it
500. 19:40in 5 to 10 minutes
501. 19:43and we are back. The status now says
502. 19:45available. If we click on our database
503. 19:48name and look right here under
504. 19:49connectivity and security, AWS has given
505. 19:52us an endpoint. This long URL string is
506. 19:55the exact address you will paste into
507. 19:57your application code so your app knows
508. 19:58where to send your data. We have a fully
509. 20:01functioning enterprisegrade MySQL
510. 20:03database server running in the cloud and
511. 20:05we didn't type a single line of
512. 20:06installation code.
513. 20:09Now for the absolute most important part
514. 20:11of the lab that is cleanup. See RDS
515. 20:14databases cost real money and they are
516. 20:16charged by the hour. Never leave a lab
517. 20:19database running. And if you have any
518. 20:21older resources like you have EC2
519. 20:23instances created or you have Lambda
520. 20:25functions, S3 buckets or anything that
521. 20:27is created. You can clean them up. And
522. 20:30now we have this action menu at the top.
523. 20:32Click on that. You have two options. You
524. 20:34can click stop temporary. This stops the
525. 20:38server and it stop your hourly billing
526. 20:40as well. It is just like turning off
527. 20:41your server. AWS will automatically turn
528. 20:44it back on after 7 days to perform
529. 20:45required maintenance. Since we are
530. 20:47totally done with this lab, we will
531. 20:48click on delete. It will ask if you want
532. 20:51to create a final snapshot. Uncheck that
533. 20:53box and type delete me. Okay. And uh
534. 20:57yeah, so let's get rid of it
535. 20:59permanently. And just like that, you
536. 21:01didn't just blindly build a database.
537. 21:03You now actually understand why you
538. 21:05selected every single option from
539. 21:07storage autoscaling down to the public
540. 21:09access firewalls. Now let's see if this
541. 21:12is sticking. I've got three real world
542. 21:14exam questions for you. Let's break them
543. 21:16down. The first question is your
544. 21:18relational database is getting
545. 21:20completely overwhelmed by read traffic
546. 21:22from an internal reporting tool. It is
547. 21:25slowing down normal customer purchases.
548. 21:27Which RDS feature should you use? The
549. 21:30options are multiple aetss, automated
550. 21:32backups, read replicas or DAX. Think
551. 21:36about it.
552. 21:38The pain point is read traffic. Multiple
553. 21:40agents is for surviving the crash. So
554. 21:43that's wrong. DAX is a catch but it's
555. 21:46only for Dynamo DB and the question says
556. 21:50relational database. So the answer is
557. 21:53read replicas.
558. 21:55The next question we have here is which
559. 21:57AWS service is a pabyte scale data
560. 22:00warehouse designed for analytics and
561. 22:02business intelligence. We have Amazon
562. 22:05Aurora, Amazon Red Shift, Amazon Elastic
563. 22:08Catch and Amazon Neptune. See here the
564. 22:11data warehouse and analytics are the
565. 22:13massive trigger words. Aurora is for
566. 22:16live transactions. Neptune is for social
567. 22:19graphs. the data warehouse. The data
568. 22:21warehouse is always Amazon red shift we
569. 22:25have this elastic catch as well. It is
570. 22:26fully managed uh inmemory data store and
571. 22:29catching service. So it's built for a
572. 22:31speed. It's not built for heavy
573. 22:32analytics or reporting. The next
574. 22:34question we have is a gaming startup
575. 22:36needs a database that guarantees
576. 22:38singledigit millisecond latency for
577. 22:40millions of players. They need flexible
578. 22:43key value data structure. Which service
579. 22:45fits best? So we have Amazon RDS, Amazon
580. 22:49Dynamob DB, Amazon Document DB, Amazon
581. 22:52S3. Pause here, read the question again
582. 22:55and think about it. What should be the
583. 22:56answer?
584. 22:58S3 is for files, not a database. RDS is
585. 23:02relational, so it's not flexible.
586. 23:05Key value and millisecond latency points
587. 23:07directly to our serverless champion that
588. 23:09is Amazon Dynamo DB. So this is the
589. 23:12correct answer.
590. 23:14All right, you absolutely crushed it
591. 23:16today. Database terminology sounds scary
592. 23:18at first, but once you know that key
593. 23:20value is just a code check and
594. 23:22multi-agent is just a backup generator,
595. 23:24it all makes sense. Your homework
596. 23:27tonight, go to your practice portal and
597. 23:28knock down 10 database questions.
598. 23:31Tomorrow is use day 14 is milestone 2.
599. 23:33We are doing 35 question midterm review
600. 23:35covering everything we have learned in
601. 23:37week 1 and week two. So brush up on EC2,
602. 23:39S3, networking and today's databases. So
603. 23:42brush up for tomorrow's test and keep
604. 23:44building. I will see you in day 14.