Hey there 馃憢, we're doing an informal survey to gauge the interest in this project and it would be very helpful if you could answer the following questions:
Thank you for your help in improving Dgraph!
How would you want us to answer this? I'm still more or less evaluating Dgraph and trying to get it to work with our own internal software/services, but leaving the answers to all of the above questions on a public issue does not seem ideal.
I'm evaluating dgraph for a startup right now. Currently using Neo4j but we have problems with scaling and intermittent issues.
Dgraph looks great. I've got a proof of concept up and running really quickly and loving the performance. The primary use case will be for calculating best paths between nodes and ABAC style access controls.
However, having features like ACL and backups behind such a high paywall are definitely a problem and may have us looking elsewhere.
We wanted to evaluated dgraph for our one of the microservices where we needed heavy lifting of graphs and tree structured data in Industrial materials management.
We have around 80K nodes on average in one tree and with this neo4j starts complaining on memory. (as you know its Java)
Dgraph was performant , intuitive , and reliable , however as the open soruce did not have multidb support so we went with using Neo4j.
If Dgraph brings this feature we are surely moving to dgraph. for all our materials management workloads.
I have used Dgraph in my business. it made us amazing.but there is some problems are bothering me.
because of the above major obstacles, it is hard for us to large-scale use dgraph in production.
Github issues have been deprecated.
This issue has been moved to discuss. You can follow the conversation there and also subscribe to updates by changing your notification preferences.

Most helpful comment
I'm evaluating dgraph for a startup right now. Currently using Neo4j but we have problems with scaling and intermittent issues.
Dgraph looks great. I've got a proof of concept up and running really quickly and loving the performance. The primary use case will be for calculating best paths between nodes and ABAC style access controls.
However, having features like ACL and backups behind such a high paywall are definitely a problem and may have us looking elsewhere.