This is not really a question on dgraph. We currently have a system with ELK for storage. We have felt that some of our data access patterns could be better served from a graph database instead of ELK. So we are trying to evaluate how good graph-databases will be for our use-cases.
I have come across Dgraph in my tech feeds so often that I want to try this along with redisgraph as the first option. But I want to know some of the basics of modelling our data for a graph-based database, choosing a right querying mechanism (graphql vs cypher etc.). So I am basically looking for some good introductory material which people have come across / recommend wrt graph databases, modelling our data for graphs (Should we create an edge or should we store it as a node property ? etc.).
The reason why we want to move away from ELK is primarily because it scales poorly when we have multiple GBs of data and we try to do a temporal query. Our setup and usecase is somewhat documented at https://psankar.blogspot.com/2020/05/what-database-solution-would-you-pick.html if you are curios.