1 00:00:00,360 --> 00:00:03,330 So now let's do a summary of Amazon Aura. 2 00:00:03,330 --> 00:00:06,360 So Aura has a compatible API for two database engines 3 00:00:06,360 --> 00:00:08,760 which are PostgreSQL and MySQL. 4 00:00:08,760 --> 00:00:10,740 And Aura is a very special service 5 00:00:10,740 --> 00:00:13,770 because storage and computes are separate. 6 00:00:13,770 --> 00:00:16,440 So about storage, while the data is stored 7 00:00:16,440 --> 00:00:19,980 in six replicas across three availability zones by default 8 00:00:19,980 --> 00:00:21,420 and you cannot change this. 9 00:00:21,420 --> 00:00:23,820 Therefore, Aura is highly available. 10 00:00:23,820 --> 00:00:25,860 On top of it, in case there is any issue 11 00:00:25,860 --> 00:00:27,450 with the storage, there's going to be 12 00:00:27,450 --> 00:00:28,620 a self-healing process 13 00:00:28,620 --> 00:00:30,030 behind the scenes happening. 14 00:00:30,030 --> 00:00:33,450 And if you wanted to increase the storage, no problem. 15 00:00:33,450 --> 00:00:35,790 There is auto scaling out of the box. 16 00:00:35,790 --> 00:00:36,810 Now for the compute side, 17 00:00:36,810 --> 00:00:39,630 this is the actual database instances. 18 00:00:39,630 --> 00:00:41,880 They are clustered and they can be across 19 00:00:41,880 --> 00:00:44,125 multiple availability zones, if you wanted to. 20 00:00:44,125 --> 00:00:45,930 And then if you had Read Replicas, 21 00:00:45,930 --> 00:00:49,560 you could autoscale them as well to increase the load, 22 00:00:49,560 --> 00:00:52,470 to increase the capacity in case the load increases. 23 00:00:52,470 --> 00:00:56,280 Now, because you have a cluster of database instances 24 00:00:56,280 --> 00:00:59,040 then you need custom endpoint to know where to 25 00:00:59,040 --> 00:00:59,873 write and read. 26 00:00:59,873 --> 00:01:01,920 And therefore you have a writer endpoint 27 00:01:01,920 --> 00:01:03,870 and a reader endpoint. 28 00:01:03,870 --> 00:01:06,420 You have the same security monitoring 29 00:01:06,420 --> 00:01:09,360 and maintenance features as RDS because, end of the day, 30 00:01:09,360 --> 00:01:11,310 they used kind of the same engine. 31 00:01:11,310 --> 00:01:13,110 And you need to know the backup 32 00:01:13,110 --> 00:01:14,910 and restore options for Aura, 33 00:01:14,910 --> 00:01:16,680 which cannot summarize here but I suggest 34 00:01:16,680 --> 00:01:19,495 you go back to that lecture if you ever need to. 35 00:01:19,495 --> 00:01:22,920 Now some extra features you need to know about Aura, 36 00:01:22,920 --> 00:01:24,930 the first one is Aura Serverless. 37 00:01:24,930 --> 00:01:28,020 This is when you have unpredictable and intermittent 38 00:01:28,020 --> 00:01:31,170 workloads, but you don't need to do any capacity planning. 39 00:01:31,170 --> 00:01:33,720 So it is quite helpful in that use case. 40 00:01:33,720 --> 00:01:35,657 If you need to have continuous right fillers 41 00:01:35,657 --> 00:01:39,240 because you want to have high right availability, 42 00:01:39,240 --> 00:01:41,730 then you need to use Aura Multi Master 43 00:01:41,730 --> 00:01:46,730 in which many database instances can write to the storage. 44 00:01:47,160 --> 00:01:50,010 If you wanted to have a global database 45 00:01:50,010 --> 00:01:51,990 you could use Aura Global. 46 00:01:51,990 --> 00:01:55,890 And that gives you up to 16 database read instances 47 00:01:55,890 --> 00:01:59,280 in each region where your database is replicated. 48 00:01:59,280 --> 00:02:02,610 And the storage replication happens 49 00:02:02,610 --> 00:02:05,160 in less than one second, usually across regions, 50 00:02:05,160 --> 00:02:08,580 which is something you have to look out for at the exam. 51 00:02:08,580 --> 00:02:11,370 And in case you have a problem in your primary region, 52 00:02:11,370 --> 00:02:13,380 you can promote a secondary region to 53 00:02:13,380 --> 00:02:15,240 become your new primary. 54 00:02:15,240 --> 00:02:17,400 If you wanted to perform machine learning on top of Aura, 55 00:02:17,400 --> 00:02:19,740 you could use the Aura Machine Learning module to 56 00:02:19,740 --> 00:02:22,170 use SageMaker and Comprehend. 57 00:02:22,170 --> 00:02:25,530 If you wanted to use a testing database 58 00:02:25,530 --> 00:02:26,910 or a staging database 59 00:02:26,910 --> 00:02:29,040 out of your production database, for example, 60 00:02:29,040 --> 00:02:31,625 you could use the Aura Database Cloning feature 61 00:02:31,625 --> 00:02:35,730 to create a new Aura cluster out of the existing one. 62 00:02:35,730 --> 00:02:36,960 And it is much faster 63 00:02:36,960 --> 00:02:40,080 than doing a snapshot and restoring it. 64 00:02:40,080 --> 00:02:43,140 So the use cases for Aura are the same as RDS, 65 00:02:43,140 --> 00:02:46,200 but you have less maintenance, more flexibility, 66 00:02:46,200 --> 00:02:48,720 more performance, and more features out of the box 67 00:02:48,720 --> 00:02:50,760 which makes Aura a great choice. 68 00:02:50,760 --> 00:02:51,593 Okay. That's it. 69 00:02:51,593 --> 00:02:52,426 I hope you liked it. 70 00:02:52,426 --> 00:02:54,360 And I will see you in the next lecture.