shindig-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From René Peinl (JIRA) <j...@apache.org>
Subject [jira] [Updated] (SHINDIG-1911) Alternative Backend based on neo4j with high performance and additional features
Date Wed, 08 Jan 2014 13:39:50 GMT

     [ https://issues.apache.org/jira/browse/SHINDIG-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

René Peinl updated SHINDIG-1911:
--------------------------------

    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.

  was:
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.


> 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.1
>
>         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.1.5#6160)

Mime
View raw message