Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
The module attempts to connect Drupal with the Neo4J database. It is a concept module, the end goal is not yet finalized.
The problem
Drupal mostly relies on traditional databases, which performs badly at certain conditions. Imagine you have lot's of references. Your interest is to know (let's say) which node has a certain field value that is connected to another node - no matter how deep is the connection. Or another example, you're on a node interested in which other nodes has similar characteristics (by having similar field values or connect to the same contents). There queries are hard to describe with a relational - or even with a traditional no-sql database. That's where Neo4J and the graph database plays an important role.
The solution
This module doesn't intend to change the backend to a graph database, it doesn't serve Drupal as a whole. In fact it's an overlay. It maintains all entities with certain properties which you can select as well as their field data. Then you can create queries against the graph database (directly to the graph db engine or through views) and filter your content. So you only query it when you need graph query, then retain the content IDs and use that to present content or feed Views with it.
To make COD better for Drupalcon, Drupalcamps and for generic use. This will take what has been heard from the Drupal community summit and integrate from the start. The architecture will include various social media plugs and allow for integration with Joind.in, Lanyrd and Eventbrite to name a few. Once this has reached a satisfying status and is being used it will be converted hopefully back to COD.