In which cases is it better to use NoSQL, and in which SQL?

Question

SQL

I used NoSQL and SQL, I felt the difference, but I still can’t understand which database is better to use in which projects.
I would be grateful for a link to an article or a detailed answer, so that in the future I could immediately decide on the choice of a database when designing a project.

Answer 1

* if in demagogy *
NoSQL is suitable for storage, where the logic of relationships between objects is set by a programmer at a higher level, SQL, on the contrary, obliges to describe the storage logic at the database level.
Both approaches have the right to life and can be more productive than one another, depending on the situation.
The fashion trend in many aspects of NoSQL development comes from the fact that most frameworks (and the development industry as a whole) are ripe for the transition to this paradigm.
*if in practice*
NoSQL is most often key:value storage, i.e. you can write and read paired values ​​​​very quickly, you can quickly replicate them, distribute them, you can scale this design, all you need in this approach, duck is on top, above the level of abstraction, describe the logic of relationships between these records \ tables.
In such storage, at the database level, you will not be able to say that field A in table Aa should be filled with a value from table Bb and field B, you will have to write code that will determine this logic itself.
Of course, you will also have to write the logic for all data queries, all the joins, and so on (although some frameworks make it easier or level it).

Answer 2

Here is an extended answer for you.
You could not use NoSQL, you used some specific data model and a specific DBMS.
NoSQL or SQL is neither a database nor a DBMS.
In the "answer on the Toaster" format, it is impossible to compare existing data models and even more so to give advice on choosing a DBMS. Start with something else: leave the historical marketing term "NoSQL" aside and start by looking at real data models and their popular implementations:
- columnar DBMS ;
- "key-value" storage ;
- document-oriented database ;
- graph database ;

Answer 3

NoSql is just some logs to store, everything else for the web usually has a relation.

Answer 4

Use postgres PostgreSQL
- a free object-relational database management system (DBMS)
And do not fool us .
the project will be overwhelmed

Answer 5

NoSql can cache pages or something ready