Details
-
Improvement
-
Status: Patch Available
-
Major
-
Resolution: Unresolved
-
2.5.0-update1
-
needs neo4j version 1.9.x, and neo4j server components available at github: https://github.com/iisys-hof/neo4j-websocket-server/ and https://github.com/iisys-hof/neo4j-websocket-common using the server routines https://github.com/iisys-hof/shindig-websocket-serverroutines which depend on https://github.com/iisys-hof/shindig-websocket-commonneeds neo4j version 1.9.x, and neo4j server components available at github: https://github.com/iisys-hof/neo4j-websocket-server/ and https://github.com/iisys-hof/neo4j-websocket-common using the server routines https://github.com/iisys-hof/shindig-websocket-serverroutines which depend on https://github.com/iisys-hof/shindig-websocket-common
Description
Shindig is operating on highly interconnected or networked data. However, it is currently using a dummy JSON or a low performance JPA-based relational backend.
We have built an alternative backend based on the open source graph database neo4j, that performed very well in our benchmarks compared to JPA with MySQL. It additionally offers the possibility to provide typical social networking functionality like friend-of-a-friend queries and recommendations for friends and group memberships at high performance.
We created a patch that introduces this backend as a Guice module similar to the JPA module.
Test data can be obtained from dropbox:
https://dl.dropboxusercontent.com/u/32445341/neo4j.zip
Zip file should be extracted to a new folder. Then point the neo4j server to this folder as its database folder.
