So far, I never had to use NoSQL for my projects. My projects don’t require me to read or write a lot of information from/to databases, so MySQL — which is an RDBMS that I am most familiar with — has been sufficient.
But for one of my projects, I had to check whether a specific set of users was active. And in order to implement that, I decided to use Firebase Firestore
And one of the nice things about using Firestorewas that I could change akey of my json data without changing the table. For instance, I first created a table with a key called status and I used strings such as online and offline as its value. But I wanted to change the data type to boolean in order to avoid using === the operator in JavaScript.
In order for me to do that using MySQL, I would have to ALTER TABLE . However, with NoSQL, I didn’t have to do that. I just changed the key-value without changing a database setting, and it worked perfectly fine without throwing any error. And I got my job done
so I decided to look into NoSQL and see what it is.
Document
Key-Value
Graph
The difference between the three is very well explained in the neo4j document.