So now let's do a summary of Amazon Aura.
So Aura has a compatible API for two database engines
which are PostgreSQL and MySQL.
And Aura is a very special service
because storage and computes are separate.
So about storage, while the data is stored
in six replicas across three availability zones by default
and you cannot change this.
Therefore, Aura is highly available.
On top of it, in case there is any issue
with the storage, there's going to be
a self-healing process
behind the scenes happening.
And if you wanted to increase the storage, no problem.
There is auto scaling out of the box.
Now for the compute side,
this is the actual database instances.
They are clustered and they can be across
multiple availability zones, if you wanted to.
And then if you had Read Replicas,
you could autoscale them as well to increase the load,
to increase the capacity in case the load increases.
Now, because you have a cluster of database instances
then you need custom endpoint to know where to
write and read.
And therefore you have a writer endpoint
and a reader endpoint.
You have the same security monitoring
and maintenance features as RDS because, end of the day,
they used kind of the same engine.
And you need to know the backup
and restore options for Aura,
which cannot summarize here but I suggest
you go back to that lecture if you ever need to.
Now some extra features you need to know about Aura,
the first one is Aura Serverless.
This is when you have unpredictable and intermittent
workloads, but you don't need to do any capacity planning.
So it is quite helpful in that use case.
If you need to have continuous right fillers
because you want to have high right availability,
then you need to use Aura Multi Master
in which many database instances can write to the storage.
If you wanted to have a global database
you could use Aura Global.
And that gives you up to 16 database read instances
in each region where your database is replicated.
And the storage replication happens
in less than one second, usually across regions,
which is something you have to look out for at the exam.
And in case you have a problem in your primary region,
you can promote a secondary region to
become your new primary.
If you wanted to perform machine learning on top of Aura,
you could use the Aura Machine Learning module to
use SageMaker and Comprehend.
If you wanted to use a testing database
or a staging database
out of your production database, for example,
you could use the Aura Database Cloning feature
to create a new Aura cluster out of the existing one.
And it is much faster
than doing a snapshot and restoring it.
So the use cases for Aura are the same as RDS,
but you have less maintenance, more flexibility,
more performance, and more features out of the box
which makes Aura a great choice.
Okay. That's it.
I hope you liked it.
And I will see you in the next lecture.