 So, in this module, I will talk about three very important things. As a matter of fact, 3 into 10, there are 30 about NoSQL. So, there is something called as three tens. So, what are those three tens? Those three tens are why and what and the misconceptions about MySQL. Say for example, 10 advantage of NoSQL. As you can see on the screen, there are quite a few, the long list of 10 advantages. I will not be discussing all of those 10 advantages in this module, because when we go into the details of these 10 advantages, I will talk in more detail about those 10 advantages. Followed by these 10 advantages, I will talk about what are the 10 misconceptions about NoSQL. And after that, I will briefly talk about why developers, the 10 reasons why developers love MySQL. So, that will be covered in this module. So, very, very briefly, I will talk about the first thing is less need for ETL. Less need for ETL. ETL stands for Extract Transform Load. And in a data warehouse environment specially, that takes a significant amount of effort. Even in this database environment, it will take a significant amount of effort to extract the data, transform it and to load it. The good thing in the context of NoSQL is that it has what you call the data has been stored and it could be in the form of columnar, it could be triples, it could be text and this is all native to NoSQL. This is all native to NoSQL. It means that there is no transformation required. So, as the data becomes available in those four forms or in those forms which are supported by NoSQL, that data can be directly loaded into the NoSQL database. So, that is one of the 10 advantages. One is the breadth of this functionality. The breadth of the functionality is that the NoSQL is, let's look at some relational databases. I would not like to take the names, but there are certain leaders of database community, certain products and they are not very, very different. They are somewhat different in certain aspects, but they are all relational. When we talk of NoSQL, there are four different types of databases which are supported by NoSQL. And that's the biggest advantage. As I said in the previous module also, so it means that because of this breadth and diverse nature of the functionality of NoSQL, you are bound to find an implementation or the type of NoSQL database which is going to meet your requirements. I believe you understand. No legacy code. NoSQL has not been around for decades, five or six decades. It has been around for a shorter time, right? It means that the code which needs to be transformed, which needs to be converted so that it can be loaded and worked on in a MySQL database is very little or it is hardly any such code. But it means you can move very, very fast. Let's look at the misconceptions. So what is a misconception? Misconception is kind of a misunderstanding or it means that the people have the wrong idea about the right thing. So that's a misconception. So I'll talk about the asset compliance. Asset is the gold standard. Asset is the gold standard. It means that the operation is atomic. C is consistency. When the transaction takes place, it does not interferes and it is durable, right? So people have a misconception that maybe MySQL or basically we are talking about NoSQL over here that may have been non-acid compliant. That is not the case. There are many flavors of NoSQL which are serializable or they are asset compliant to a certain aspect. Clusters are asset compliant, okay? And then there are features. There are facilities in which you can set the level of asset compliance for this implementation for this type of NoSQL database. You can do this selectively. So that's a big misconception. Now let's look at some of the reasons why developers love NoSQL. No need to write SQL. They're writing SQL, good SQL, okay? That is not a science. That is an art. And there are people who have spent their lifetimes perfecting that art, okay? And of course the database changes with time also. And when the database changes, the code has to change, okay? The SQL code has to change and that is a project in itself to change that code, right? And there are, the developers have developed those hibernate techniques also to change the code to make it kind of automated to take the SQL part out of it. But still you have to go and use SQL. So for the databases of NoSQL, there are non-relational databases also. And if you still have to use, you are kind of associated with or kind of in love with SQL, then you can create an interface and do SQL, right, on a non-relational NoSQL, right or not. So these are some of the reasons why developers love NoSQL. And when we go into details, I will discuss all of them, all 10 of them, okay, in detail with you. So that's about for this module.