Hello, I am evaluating Dgraph and just wanted to provide some feedback about the documentation.
As someone with experience in RDBMS and SQL, one of the first things I would like to know is how would I model my data differently in a graph database like Dgraph. What are the options/ways that I can model my data? What are the possible structures that can be used?
For example, in an RDBMS I can use tables with rows that have columns defined in a schema, and I can use foreign keys to create relations between tables.
What can I do with Dgraph?
I have glanced over the documentation and I have seen that there are (I think) Nodes, Edges, Facets, Predicates(?) and Schemas(?) and I don’t know what else. Problem is I don’t know what these are and how they relate to each other.
The documentation at:
Starts with “Get Started” which tells me how to install Dgraph, add some data and do some queries. But at this stage, as I am on Windows, I just want to evaluate without having to install anything.
Now again the “Tour” also requires me to install a local Dgraph in order to follow it. So I haven’t done it.
Then the next topic in the documentation is “Query Language” and then “Mutations”. At this point I want to know how I would design and define my data model before querying or mutating it or going into the details of the “Query Language”.
What I need is something that explains how you would (and how you can) model your data in Dgraph and what these basic concepts of Nodes, Edges, Predicates etc. actually mean starting at a high level before going into actual query language code.
Also a few simple but illustrative examples would be very helpful so people new to Dgraph can see how common patterns in typical RDBMS data models would (and should) be translated to Dgraph. Again, begin with a high level explaining the concepts of Nodes, Edges, Predicates and whatever needs to be understood etc. and display the design in clear diagram form, and only then show how it would translate to the query language.
I saw one of your talks (the one in Singapore) on Youtube, and it was very interesting. However, nowhere in the documentation can I find clear explanations of how one would design the data model. I think this is a very important topic and people who are coming from RDBMSs need to be given the correct picture as this is a completely new paradigm to them meaning old best practices are no longer valid and new ones must be learned.
I think the Tour might answer these questions, but it feels like having to go through an online course plus setting up a VM just to be able to get a basic idea of what Dgraph can do is a bit of a pain. A simple documentation page would easily answer them.