Instead of tacking an RBAC system onto a flat document management system, I just designed my data model as a set of objects and different types of relationships. Saves me the trouble of metadata, normalization, and access control just becomes a traversal instead of having to manage a separate policy store.
Anything that requires collaboration, sharing, user profiles, consent, etc.
We see a lot of usage of Dgraph among developers who are building apps with social data. Or, platforms where they need to unite multiple different data sources from multiple relational DB silos.
To debunk the myth that Graph DBs are special-purpose, we've built two projects ourselves (open source) which put Stack Overflow and Twitter data on Dgraph and serve it. The links are in the blog post under Use cases.
https://blog.dgraph.io/post/how-dgraph-labs-raised-series-a/
Or some other approach for building your GraphQL layer on top of Neo4j?
[1] https://grandstack.io/docs/neo4j-graphql-js-quickstart.html
If you're willing to share some info, my email is francesc@dgraph.io!