Performance advise on graph/schema design

Thank you for the quick replies!

@abhijit-kar I am intrigued to see how Dgraph will perform once we have everything in place. I think we will try out a few data sources and see as we go.

@abhimanyusinghgaur We are using Dgraph and GraphQL± for a different service that holds our behavior change programs. This is fairly striaght-forward by using the types Program (bound to a user) and Messages (unique ones) that can be linked to a Program. We use facets to determine when a person should receive a message. The schema we are describing in the post is new for us; we are currently storing this in MongoDB but are looking to migrate to Dgraph. At the moment I cannot share any queries or experience on the matter at hand because we still need to implement it. Our mobile clients would most often pull a subset of the user’s (summary) data but our research interface would query population-wide data. The analysis are (atm) user-based but we query more granular data (like GPS) then with the mobile app.

If you are interested, I can DM you with some common queries we do for the existing service running with Dgraph? We are running into a few restrictions (in knowledge probably) for some “more advanced” queries from our perspective that the docs haven’t been able to shed light on. At the moment we take care of additional steps after having pulled it on a client, but I assume it can be done with the variables blocks as well by Dgraph.