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

Docs? #114

Open
techdragon opened this issue Jul 14, 2014 · 2 comments
Open

Docs? #114

techdragon opened this issue Jul 14, 2014 · 2 comments

Comments

@techdragon
Copy link

Would be good to have some documentation that gives at least more usage driven examples, and maybe even some kind of comparison between kaiso and some of the other other python neo4j tools such as py2neo, neomodel, and neo4django

@junkafarian
Copy link

Hi Sam, thanks for expressing an interest. We'll be sure to put together some more narrative docs describing the problem area that kaiso is aiming to tackle and get them up on rtfd

@technige
Copy link
Contributor

Each of the projects you name fulfils a different purpose or abstracts the graph at a different level (more or less). As a very quick summary:

  • kaiso - provides a managed type system for modelling objects with well-defined structure; is built on top of py2neo
  • py2neo - generic REST driver and toolkit for Neo4j; some plugins are provided (OGM, calendar, etc) but is not as specialist as kaiso
  • neomodel - "ORM" layer, also built on top of py2neo, designed specifically to fit into Django projects and work in a similar way to Django's built-in ORM
  • neo4django - similar to neomodel but built on top of neo4jrestclient instead of py2neo

Hope this helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants