What tasks do graph databases solve?

Question

Database

I want to build a good DBMS, and I started looking for what and how, and came across graph databases, xs what it is and what it is eaten with, they don’t tell a damn thing on the wiki, but I would like to know for what tasks these databases can be taken and what they are different from the rest of all noSQL and RDBSD, it seems to be something like this.

Answer 1

For example , something like an introductory lecture on graph DBMS . As far as I understand, they are mainly intended for use directly by a person (that is, a person sits and pokes something in the database) and is needed for deep data analysis (data mining, if in our opinion, in a simple way).
And by the way graph DBMS is a special case of nosql. NoSQL is everything that is not SQL, and not just their trendy mongs and radishes. The telephone directory is also NoSQL for example.

Answer 2

Although an old question,
one of the main themes in graph databases is that the links between objects (vertices) are database-level objects. This means that when querying in runtime, time is not spent on calculating these links (while in rdbs, each join is a runtime calculation of such links)
As a result, in rdbs the processing time of such a request depends on the number of records, and in graph Hardly ever