[
https://issues.apache.org/jira/browse/SHINDIG-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Baxter updated SHINDIG-1911:
---------------------------------
Fix Version/s: (was: 2.5.2)
2.5.3
> Alternative Backend based on neo4j with high performance and additional
> features
> --------------------------------------------------------------------------------
>
> Key: SHINDIG-1911
> URL: https://issues.apache.org/jira/browse/SHINDIG-1911
> Project: Shindig
> Issue Type: Improvement
> Components: Java
> Affects Versions: 2.5.0-update1
> Environment: 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-common
> Reporter: René Peinl
> Labels: database
> Fix For: 2.5.3
>
> Attachments: websocket-backend.patch
>
> Original Estimate: 2,016h
> Remaining Estimate: 2,016h
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
