Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Share nodes & rels across db URLs #89

Closed
aseemk opened this issue Oct 2, 2013 · 2 comments
Closed

Share nodes & rels across db URLs #89

aseemk opened this issue Oct 2, 2013 · 2 comments

Comments

@aseemk
Copy link
Member

aseemk commented Oct 2, 2013

We at @fiftythree use a clustered Neo4j setup, and for scalability/performance, we see ourselves wanting to split our queries between the master and the slaves depending on whether they need to be immediately consistent or can be eventually consistent.

To do that, we'd currently need two different GraphDatabase instances (pointing to different URLs), but there isn't currently a way to share Node or Relationship instances between the separate db instances. E.g. make a read query against a slave db, get back nodes/rels, and perform a write query from them to the master db.

We'll probably need to rethink the API to support this scenario...

@aseemk
Copy link
Member Author

aseemk commented Nov 11, 2013

Another use case: cache sharding. E.g. sending user lookups to instance A or B depending on country.

@aseemk
Copy link
Member Author

aseemk commented Nov 7, 2014

The currently ongoing v2 redesign will change this driver to no longer be hypermedia-driven (and generally be functional/stateless), so these should no longer be a problem.

Issue: #143 / PR: #145
WIP docs: https://github.com/thingdom/node-neo4j/blob/v2/API_v2.md

Closing this as "won't fix" accordingly.

@aseemk aseemk closed this as completed Nov 7, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant