 So student in this course we have come across the word SQL a number of times such as we have talked about SQL SQL and MySQL and NoSQL and we will also talk about new SQL so how do they compare SQL SQL is the structured query language which was developed to query relational databases okay now MySQL and NoSQL are something which are very different so in this module I will talk about those differences historically MySQL AG was a Swedish company which was I believe established in 1995 and then it was acquired by Sun Microsystems and then it was purchased or acquired by Oracle Corporation so MySQL is currently owned by Oracle Corporation let's go ahead so what this module will cover is MySQL then NoSQL and a comparison a tabular comparison and a brief conclusion with reference to these comparisons and visa ways NoSQL so what is MySQL the benefit of MySQL MySQL is a relational database system it supports the relational model okay and it is available in public domain it is public domain it is public usage license proprietary license it is all there it is relational relational means that it has the primary key and the foreign key and how those tables are linked together it is fast it is powerful it is used by large organizations and of course it became popular I will tell you how it became popular and what leads to its popularity and it uses SQL it is supported by many operating systems and you can make connections using the kind of standard programming languages also so it is it is well established okay for these reasons then NoSQL it has varied and different databases okay it has actually four types of different databases it's it supports the columnar it supports a triples it supports you know key based and the document based also so it has four different types of so called databases or data structures as opposed to a single one in the relational which is the MySQL which we were talking about and it is popular hugely popular for big data and this popularity was triggered by Facebook by Amazon by Google and so these are huge huge setups and NoSQL is supporting those applications which are run at these huge setups so that's why it has become very popular then there is something which is the eventual consistency when the changes are made it is not certain versions are not fully acid compliant which we have already discussed and we will maybe discuss more also so ultimately in milliseconds the read the change is reflected for read operation in milliseconds not immediately in milliseconds right and that is a stale read stale read okay which I have written over here still read so this this is fine if I make a Facebook posting and my friends see it after a few seconds or maybe a few minutes or maybe a minute but it doesn't work in a financial system it will not work it will be disaster implementation is different the document coding but it follows the standard format follows so there is certain standardization and it has it supports the key based lookup so I have a key and based upon that key I can retrieve what I am looking for the key is linked the key is linked with what I'm looking for so what is the advantage of course advantage is quick search and then of course there are APIs to perform to query that database so let's look at those some of this comparisons over here so my SQL is relational and no SQL is non-relational over here the concept of table over here we have a concept of document and we have triple also triple stores also and it is relational okay it is good for it is good for big data big data detailed model need to be in place okay this is you have discussed agnostic okay the need has vast and expert community this is growing is it growing we don't have a lot of people who are using and help you out it follows SQL it is mentioned you can use the API is also okay same a schema is rigid okay if the schema is not rigid I mentioned over here also okay variety of reporting tools lacks those tools over here so the point this what this slide is telling is that of course my SQL is more mature as compared to no SQL in a nutshell in a conclusion there are multiple advantage of no SQL which are scalability which is performance which is open source which is cost and the list goes on so these are the advantages of no SQL but it is not as much standardized as the relational model okay there are many versions as I will discuss more in the subsequent modules and I have already discussed in the prior modules also this is the last module on no SQL is that the no SQL is whenever the people the programmers came across a problem and they could not find a no SQL solution or a model they developed their own model their own solution and published it made it public okay so that's why it is not so standardized the CIO chief information officer need to look at and where the options what functionality is needed how much it's needed how critical it is and based upon those needs needs to identify okay which kind of model suits them and finally business needs and the data volume no SQL is good for big data so that's all I have for this module thank you for your time