Hi, everyone, and welcome back.
Now in today's video, we are going to discuss about the Dynamo DB accelerator, also referred to as
DAX.
Now when we discuss about the Dynamo DB, in most of the cases, the oral response time can be measured
within single digit milliseconds and this is quite fast.
However, some organizations have used cases where the require response time within microseconds, and
this is one of the reasons why it has released a new feature associated with the Dynamo DB accelerator
that provides much, much more faster response times for accessing the eventually consistent data.
So at a high level overview, the Dynamo DB accelerator is a fully managed, highly available in memory
cache for the Dynamo DB that delivers up to ten times the performance improvement.
So this can be understood with the diagram where you have a Dynamo DB table on the right, you have
your application on the left and you have your DAX cluster over here.
This DAX cluster can consist of the frequently accessed data.
Many times same set of data are being accessed for you can see thousands or tens of thousands of times
by different customers across the world.
So you do not really want your application to go ahead and send thousands of requests to Dynamo DB Table.
Instead, those frequently accessed data can be stored at the DAX cluster level and it can be fetched
directly by your application so that you do not really have to pay for the Dynamo DB table by increasing
the overall throughput.
So that's the high level overview.
Let's quickly look into it now within the Dynamo DB console, along with the various options related
to creating a table and so on, you have a dedicated option for Dynamo DB Accelerator.
So let's go ahead and quickly open this up.
And within you can go ahead and create a cluster.
Let me go ahead and do that.
I'll say Demo Dak's cluster within the Node families.
For this demo purpose, I'll be using the DT type family.
We'll be using the smallest instance available.
You can again define the set of nodes.
I'll just use one for the time being.
I'll do a next.
Within the subnet group.
You can just add a subnet group as a demo.
Dak's Subnet Group Let's go back down and we'll be selecting one of the subnets for our purpose.
You can also go ahead and define the security group rule.
Let's do a next within here you have the iam permissions.
You can just give a name.
I'll say dak's iam.
Let's go a bit down.
You can specify encryption related configuration in case if you'd like.
And you have one more important option related to accessing the Dynamo DB table where you can either
select all the tables which allows your tax cluster to access all of your Dynamo DB tables in the region.
Or you can also specify a specific table or area.
So in this case, I have two tables in this region, so I can select one of the tables here you can
click on next.
We'll leave this as default.
I'll click on next in the review screen.
You can go ahead and verify and you can create a cluster.
All right.
So Eric Lester is in the creating stage and it takes a little amount of time.
So let's quickly go ahead and discuss about another point before we look into it.
Now, let's quickly look into some of the use cases where DAX can be useful.
First one is that it is useful for applications that require the fastest possible response time for
read related operations.
So some examples includes real time bidding, trading applications and so on.
Second is DAX is useful for applications that reads a small number of items more frequently than others,
and also for the applications that are read intensive but are also cost sensitive.
Now let's also look into the scenarios where DAX is not suitable for first when it is for the applications
that requires the strongly consistent reads.
Second is applications that do not require the microsecond response time for reads, or they do not
need to offload the repeated activity from the underlying tables.
And third is applications that are right intensive or that do not perform much of a read activity.
In such cases, DAX is not really proved to be useful now.
Sometimes in exams they might give you an application with a scenario and you'll have to select whether
DAX will be useful or not.
So this is where the use case and the second last slide proves to be quite useful.
So on a refresh our cluster is finally available.
It took around a few minutes for it to be created.
Now one important thing I wanted to show you your and this is why we were creating the cluster is this
end point over here the Dynamo DB cluster has its own set of endpoints and if you want your application
to take the benefits of the cache, then you will have to point it to this specific cluster.
As we already know that a specific DEX cluster can be connected to the set of Dynamo DB tables that
we had selected as part of the oral configuration.
So make sure that you go ahead and use the appropriate cluster endpoint again in case if you have created
it, make sure that you also delete it so that you don't really have to pay for the overall infrastructure
required.
So that's the high level overview.
And with this will conclude today's video.