1

00:00:01,680 --> 00:00:07,020

Thank you for enrolling for this cause, and in this course, we are going to do 90 percent of hands



2

00:00:07,030 --> 00:00:14,070

on and there's going to be only 10 percent of a theoretical, because what I believe is that doing hands



3

00:00:14,070 --> 00:00:17,240

on is the best way of learning any tools and technology.



4

00:00:17,250 --> 00:00:21,100

So is also if you are doing Hands-On, things are going to be very simple.



5

00:00:21,660 --> 00:00:26,400

However, in this session, we are going to discuss about frequently asked questions, or you can say



6

00:00:26,400 --> 00:00:33,000

this is an overview of it, because whenever you start talking about or whenever you start learning



7

00:00:33,000 --> 00:00:40,140

a new technology, it is very important to understand some of the fundamentals of the tools or any technology



8

00:00:40,140 --> 00:00:42,610

before we move ahead any further.



9

00:00:42,930 --> 00:00:48,210

So let's talk about what this is and then we are going to understand or then we are going to do hands



10

00:00:48,210 --> 00:00:49,780

on in our upcoming sessions.



11

00:00:50,130 --> 00:00:51,270

So what is it?



12

00:00:51,270 --> 00:00:53,810

Is it is is an in-memory database.



13

00:00:53,820 --> 00:01:00,460

So by in-memory database, what I mean is whatever data you stored, it is going to be stored in memory.



14

00:01:00,870 --> 00:01:07,680

OK, and that's what is and what makes it is very, very fast because you have the data in memory and



15

00:01:07,830 --> 00:01:10,860

you are going to perform, know reappropriation or right.



16

00:01:10,860 --> 00:01:17,250

Operation, and all of those operations are going to be performed by just accessing the data from memory.



17

00:01:18,180 --> 00:01:25,080

And you know that reading from memory is probably 100000 times faster than reading from this.



18

00:01:25,350 --> 00:01:27,170

And that's really huge.



19

00:01:27,360 --> 00:01:32,790

You know, makes a huge difference when you talk about this and when you talk about any other databases.



20

00:01:33,180 --> 00:01:38,810

And in fact, when you compare that with even in-memory databases, that is still way faster.



21

00:01:38,830 --> 00:01:45,000

And the reason behind that is that there is has been written and implemented in C language, and C language



22

00:01:45,000 --> 00:01:51,610

is like closest language, which understands or which is easily understood by a machine, which is computer.



23

00:01:52,020 --> 00:01:57,130

So that's all about and it is being in-memory and is being fast.



24

00:01:57,420 --> 00:02:02,790

Now the other important thing or the other thing which I would say which makes this very popular, is



25

00:02:03,120 --> 00:02:07,500

that it's being an open source so that this is an open source.



26

00:02:07,530 --> 00:02:14,400

What that means is if you have a use case that you want to have a very fast database or very fast in-memory



27

00:02:14,400 --> 00:02:21,690

database, you can just look no further than that is because this is not going to cost you extra money.



28

00:02:22,050 --> 00:02:28,950

So whatever project you have, if you implement this in that project, your project cost is not going



29

00:02:28,950 --> 00:02:34,110

to increase because this is open source and you can use it and implement in your project.



30

00:02:35,620 --> 00:02:41,320

Now, the next thing about this is that this is a key value datastore, so by key value, what I mean



31

00:02:41,320 --> 00:02:46,300

is that whatever data you stored in that is, it has to be a key value pair.



32

00:02:46,330 --> 00:02:47,860

So it's more like a dictionary.



33

00:02:47,860 --> 00:02:49,990

Or if you know about Python, it's more like Python.



34

00:02:50,830 --> 00:02:56,860

OK, so for example, let's say I have an employee ID and I want to store all the data about that employee.



35

00:02:56,860 --> 00:03:03,040

So employer is going to be a key and all the remaining information can be considered as a value and



36

00:03:03,040 --> 00:03:05,560

this key value pair can be stored in these.



37

00:03:07,080 --> 00:03:12,930

And we will talk about more about this and how the data is being stored in that is in our upcoming sessions.



38

00:03:12,990 --> 00:03:17,880

But for now, it's enough for you to understand that this is a key value data stored.



39

00:03:18,360 --> 00:03:24,060

Now, whenever we say that restores everything in memory, you might be wondering that what happens



40

00:03:24,060 --> 00:03:28,360

when let's say when power goes off, how are you going to lose all the data?



41

00:03:28,380 --> 00:03:33,570

So the answer is no, you are not going to lose any of the data because along with storing the data



42

00:03:33,570 --> 00:03:38,280

in memory, it is also gave you the ability to keep the data persistence.



43

00:03:38,610 --> 00:03:45,020

So what that means is that all the data which is there in memory can also be stored on disk.



44

00:03:45,360 --> 00:03:51,900

So whenever these laws that this is going to read all the data from the disk and going to keep in memory



45

00:03:51,900 --> 00:03:57,660

and then all the time it is just going to perform all operations from memory only when the new data



46

00:03:57,660 --> 00:04:02,790

is coming and new data, you want to make the new data also persistent that time only it is going to



47

00:04:02,790 --> 00:04:06,470

perform right operations of keeping the data on this.



48

00:04:06,720 --> 00:04:08,810

Otherwise it's just going to perform reading.



49

00:04:08,830 --> 00:04:13,440

Right and all the operations by just reading the data in memory.



50

00:04:13,920 --> 00:04:19,950

OK, so yes, from the durability point of view, data is durable because you are able to persist the



51

00:04:19,950 --> 00:04:23,570

data on this and you are not going to lose any of the data.



52

00:04:24,060 --> 00:04:30,870

And now the other thing about about this is that this gives you the option of high availability so you



53

00:04:30,870 --> 00:04:35,810

can set up alleles in in many different ways, which can give you a high availability.



54

00:04:35,820 --> 00:04:42,150

So you if you have, let's say, three servers, you can set up the radius in such a way that if one



55

00:04:42,150 --> 00:04:47,430

of your server goes down there, it is still going to be fully functional and your application is not



56

00:04:47,430 --> 00:04:51,150

going to get impacted from that is being not available.



57

00:04:52,240 --> 00:04:59,260

And now if I talk about a scalability that this gives you an option to scale any number of nodes.



58

00:04:59,590 --> 00:05:04,780

So, for example, let's say if you set up a radius cluster with six servers and in future you want



59

00:05:04,780 --> 00:05:09,570

to increase the number of servers to be in more out of radius, you can do that.



60

00:05:09,580 --> 00:05:11,150

All those options are available.



61

00:05:11,170 --> 00:05:13,920

You can install various, you know, distributed that way.



62

00:05:14,290 --> 00:05:17,550

And this is just going to scale up OK.



63

00:05:17,830 --> 00:05:24,310

And the good thing is that configuring all of those things are very easy if you want to do the same



64

00:05:24,310 --> 00:05:27,890

thing using any other other datastore technology.



65

00:05:28,150 --> 00:05:33,790

I will say things are not as easy as it is in the case of rallies, but it is is really simple.



66

00:05:33,790 --> 00:05:36,000

And that's the whole idea about using these.



67

00:05:37,330 --> 00:05:42,970

Now, let's understand some of the things in more detail, so when we said that this is in memory,



68

00:05:43,420 --> 00:05:49,180

so you already know about fundamentals of all the benefits of being an in-memory database or being a



69

00:05:49,180 --> 00:05:51,510

database which lives and lives from this.



70

00:05:51,820 --> 00:05:54,370

So I'm not going to discuss about this again.



71

00:05:54,610 --> 00:05:58,840

But this is you can bookmark this and you can keep it as your Naude.



72

00:05:59,680 --> 00:06:07,060

And about open source, there are lots and lots of features which has been listed about Reles on w w



73

00:06:07,060 --> 00:06:15,020

w dot dot IO and there is a company called Radislav which also provides you enterprise level support.



74

00:06:15,040 --> 00:06:20,650

So let's say if you want or your organization wants to have someone who can help you and there is a



75

00:06:20,650 --> 00:06:24,040

production issue, then you can get in touch with these lives.



76

00:06:24,220 --> 00:06:30,280

And their lives in that case is going to provide you an enterprise level of support and that is going



77

00:06:30,280 --> 00:06:31,470

to be a paid service.



78

00:06:31,480 --> 00:06:39,070

You can read more about that from w w w o and when you get this Lib's support, you also get some of



79

00:06:39,070 --> 00:06:40,180

the additional features.



80

00:06:40,210 --> 00:06:43,900

So all of those additional features are also listed on their website.



81

00:06:44,170 --> 00:06:45,340

You can read about those.



82

00:06:45,520 --> 00:06:50,320

However, in this set, in this course, we are just going to talk about all the opensource features



83

00:06:50,320 --> 00:06:51,520

which that this brings in.



84

00:06:52,390 --> 00:06:56,790

I must say that it is open source itself is a complete package.



85

00:06:56,840 --> 00:07:00,100

There's nothing you are going to miss out if you don't go forward.



86

00:07:00,310 --> 00:07:02,410

That is licensed version.



87

00:07:04,640 --> 00:07:08,520

About DataStore, you can literally keep any type of data.



88

00:07:08,540 --> 00:07:13,840

So when traditionally we think about data storage, we think about one key and one value.



89

00:07:14,210 --> 00:07:15,270

But that's not true.



90

00:07:15,290 --> 00:07:18,260

You can keep all sorts of data.



91

00:07:18,290 --> 00:07:25,760

So here is an example of storing string's, storing, bitmap, storing Bellfield hashes, lists, sex



92

00:07:26,120 --> 00:07:27,190

sorted tests.



93

00:07:27,440 --> 00:07:33,530

So almost all type of data you can stored in rallies and release knows how to deal with all of those



94

00:07:33,530 --> 00:07:40,650

data and how to access those data on how to write those data in the fastest possible way.



95

00:07:41,550 --> 00:07:46,890

So that's all about this, and hopefully it would have given you some idea about what this is, and



96

00:07:46,890 --> 00:07:51,960

if you have any questions, please feel free to write or ask me in the Q&A session, and I would be



97

00:07:51,960 --> 00:07:53,970

more than happy to answer any question.