Haroon and welcome back.
Now in today's deal, we'll be discussing about the Aurora global database.
Now, Aurora global database allows a single Aurora database spread across multiple eatables regions.
So if I have to give you an overview about the Aurora global database in one sentence, it is nothing
but a good reading bried replicas specifically.
This would be better understood if we had more great ideas.
Now the Aurora global database replicates the data with no impact on the database performance.
It also enables fast local reads, the low latency in each region, and also provides the disaster recovery
from a region wide outages.
So this can be better examined with this diagram here where you have your Aurora master and in different
region, you have read replicas that are available.
So if you have a global application, then you can perform the read directly from the 3D replicas.
Now, in case due to some reason in the Master Ghost Dome, then you can easily promote the 3D replica
to be the new master.
So that's the overall concept behind the Aurora Global Database.
Now, if you're looking to the architecture of a global database at a very high level worldview, this
can be explained with this diagram.
Then you have the Aurora in a primary region, Aurora in a secondary region.
Now, between them at the storage level, there is a asynchronicity application that is happening.
So data is replicated based on asynchronous replication between those two regions in order to region.
Now, one important part to remember here is that since the order of storage is separated from the instance
itself at the primary region, you will see that you have.
Right that that happening from the primary instance to the storage earlier.
However, in this activity region, you only have leads that that happening from the Aurora instance
to the storage area.
So that's the high level of what have you.
So let's do one thing.
Let's jump to the practical so that we understand the steps that are involved in setting up the global
database.
So currently for today's demo, we will need to read into all year.
The fourth reading that we'll be using is not California.
And the second reason that we'll be using is Singapore.
So let's go ahead and create an Aurora database.
So I'll click on create a database.
We'll use the engine of Amazon, Aurora.
Now, within the ABC, let's leave it to be the my sequel by NOIA.
And the next important point here is the database location.
So let's go ahead and select the global venue now for testing bubblers.
We'll be using the dev disk.
Let's quickly generate the password.
Let's go big down.
We do not really want the encryption for the time being.
We'll save some cost now for the DB instances.
You'll see that there are certain limited instances that are available.
You do not really have to do not micro and so on.
So that is one of the limitations here.
So essentially what will happen is you will have to pay for this.
So that is one of the limitations as far as the practical is concerned, if in case you want to do it.
So let's go ahead and also select them.
Lindsy Diplomate.
So you will select them.
Medici Diplomate.
We leave it to be the password with authentication within their database options.
We leave.
Everything is default.
Let's remove the performance in sightseer and also remove the enhanced monitoring.
So that's the high level of you.
Let's go ahead and create a global database.
So currently within a global database, you see that the instances are still within the creating stage.
Let's quickly wait for a moment for them to be created.
All right.
So it took a few minutes and our database is now available.
Now, if you look into the role of our database, in fact, let's maximizer.
The role is globally with.
I didn't know this this step.
You do not really have a global database.
So, for example, all we have time to now is if you have created this master database, which has a
rule of blobbing, now in order to create these 3D replicas, you have to add at least an option.
So if you go to action field, you have to click on ADD region.
So you have to specify the secondary region for the global database.
Now, not all the regions are supported here.
So that is an important part to remember.
So these are the regions that are supporting let's select Singapore for secondary region.
So we didn't Singapore added the replica would be created.
Now, same thing goes as far as the instant size is concerned.
You.
Do not really have any flexibility related to the amount of memory that is endangered, or you'll see
that the amount of memory starts from around fifteen point twenty five to 16 DB.
You do not really have the key to look smartie GURD Micro.
So anyways, even if you do a previous generation instance class or you, you will see that you have
three Dawna's which has a similar memory capacity.
Any need for it will use the idea fade Earthlight.
Let's not select three replicas.
No, and that's the overview configuration.
Yet all you have to do is you have to click on ADD Preachin.
Great.
So it is creating a global database.
Now, if you look into the role associated with that, so it has the role of secondary.
Now, if you go to the Singapore region, so within the Singapore region also, you see that we have
a global database.
So if you minimize this, you have a single global database.
This has two clusters that are but the region is two.
Now, if you will see that these two instances, the other writing prebid event as part of the US,
they secure this is because we had selected them, might be the option for the US list.
And then you have a second one where you just have one primary reader instance.
So Carib is still in the early evening stage, later gained weight, primarily because they wanted to
show you on how we can promote this to be done on Mastella.
So let's quickly read for a moment here.
Alright, so it has been few minutes, and currently you would see that would either global as well
as the secondary database available now, or do remember that under a global year when the role is the
primary one and second one is the secondary one.
All right.
So this is one important part to remember.
No.
If you go to action, Soyer, you can also add a Reeb replica to the secondary database that is available.
And you can also remove this secondary database from the global one.
So let's assume that due to some reason, this global database that has a ruler primary is not working.
There are some issues.
So as part of the final word, you can promote the secondary one to detach from the Blumen and become
the new primary.
So let's go ahead and look into that.
So I go to actions.
You can click on Remove Globin.
And now there are two things that will happen the way your first one is that it will remove itself from
the global database and then it will automatically promote itself.
So this will become the new primary standalone cluster all together.
So let's go ahead and look into that.
So what I do.
Let's click on and remove and promote.
All right.
So it has been a few minutes and you see a message which states that successfully removed Hadramout
in the secondary global database all year.
Now, if you look into the secondary global database, which is based on the AP Southeastward, this
has the role of region and the instance it within Europe has the role of writer.
So this has become its own independent database.
And from here, if you go to actions, then you can add.
But the then you can have it all Broeder and so on.
So this is our independent database.
Now, one important part to remember is that once you do the promotion, you have to change the application
you ordered so that it can point to this.
Now, this specifically applies when it comes to the failover scenarios.
So let's switch back to the California attorney general.
You're so within the California region, you'd only see the instances that that a part of the US to
one region and southeast one related replicas are no longer visible a.
So now that's the high level overview about the global database now.
Well, an important part to remember here is that once you have completed a packet will go ahead and
delete all the things that we had created, primarily because we are using that.
If I don't like instance, and if you keep it running for a longer time, you'll have a good amount
of aid available at the end of the month so you can go ahead and delete the Aurora instance that you
have created everywhere.
So you can just do or delete me.
And this will initiate a deletion operation.
And same thing you can do for the added resources that you have created as part of the Aurora cluster.
Now, before we can do that, a few important point is that we need to remember.
First one is that a global database does not support automated failover to the secondary region.
So this step, this manual, sakin, is not only in certain states are supported.
So you cannot make use of de de de de de de de de three instanced glasses.
This is something that we have already seen.
Third thing is that if you're planning to make use of Uttara Global database, there are certain features
that are not of.
One of the primary one is that you cannot have a backpack feature that is supported.
And also stopping and starting their baby clusters within a global database is not supported.
So that's the Heilmann worldview about the Aurora global database.
I hope this video has been informative for you, and I look forward to seeing the next video.