6 ms·

Serious question: what are some practical examples of graph-database backed features providing significant value to “common” software applications (e-commerce,

Serious question: what are some practical examples of graph-database backed features providing significant value to “common” software applications (e-commerce, CRUD, CMS, CRM, etc.)? I lack a strong understanding of graph databases and their usecase and tend to learn best by seeing them in use in domains that I do understand.

rficcaglia 7y ago
Using neo4j in a commercial app for healthcare data as a primary store, using cypher and graphql
- johnymontana 7y ago
  Do you use the Neo4j GraphQL integration? [1] Or some other approach for building your GraphQL layer on top of Neo4j? [1] https://grandstack.io/docs/neo4j-graphql-js-quickstart.html https://grandstack.io/docs/neo4j-graphql-js-quickstart.html
- campoy 7y ago
  I would love to chat with you about your needs and requirements in the healthcare field! If you're willing to share some info, my email is francesc@dgraph.io!
dalaidunc 7y ago
The highest value use-cases of graph databases tend to not be customer-facing applications. Think about things which don't have a simple question and answer, but instead require deeper investigation into the connections of things. Things like: customer/employee 360, intelligence (business and government), compliance / reg tech, anti-fraud, anti-money laundering. In terms of customer-facing applications, then I guess recommendation engines is the main one.
mrjn 7y ago
For e-commerce, a big one is recommendations. But graphs are already known for that. 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/ https://blog.dgraph.io/post/how-dgraph-labs-raised-series-a/
motohagiography 7y ago
I'm using a graph for a collaboration platform where the back end benefits from the idea of dynamic relationships between objects where someone "owns," "shares," and things "comprise," etc. 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.
istorical 7y ago
In addition to e-commerce as mentioned above, any sort of 'related content' discovery engine to surface additional content to a user based on what they are viewing. A la YouTube related videos.

rficcaglia 7y ago

Using neo4j in a commercial app for healthcare data as a primary store, using cypher and graphql

johnymontana 7y ago
Do you use the Neo4j GraphQL integration? [1] Or some other approach for building your GraphQL layer on top of Neo4j? [1] https://grandstack.io/docs/neo4j-graphql-js-quickstart.html https://grandstack.io/docs/neo4j-graphql-js-quickstart.html
campoy 7y ago
I would love to chat with you about your needs and requirements in the healthcare field! If you're willing to share some info, my email is francesc@dgraph.io!

dalaidunc 7y ago

The highest value use-cases of graph databases tend to not be customer-facing applications. Think about things which don't have a simple question and answer, but instead require deeper investigation into the connections of things. Things like: customer/employee 360, intelligence (business and government), compliance / reg tech, anti-fraud, anti-money laundering. In terms of customer-facing applications, then I guess recommendation engines is the main one.

mrjn 7y ago

For e-commerce, a big one is recommendations. But graphs are already known for that. 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/ https://blog.dgraph.io/post/how-dgraph-labs-raised-series-a/

motohagiography 7y ago

I'm using a graph for a collaboration platform where the back end benefits from the idea of dynamic relationships between objects where someone "owns," "shares," and things "comprise," etc. 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.

istorical 7y ago

In addition to e-commerce as mentioned above, any sort of 'related content' discovery engine to surface additional content to a user based on what they are viewing. A la YouTube related videos.