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

Explain Use Cases #97

Closed
robert-zaremba opened this issue Aug 4, 2014 · 5 comments
Closed

Explain Use Cases #97

robert-zaremba opened this issue Aug 4, 2014 · 5 comments

Comments

@robert-zaremba
Copy link

Can you explain use cases for this DB? Is Cayley mean to be the universal DB of a project (substituting eg posgresql)? Or it's meant only for some not real time access.
Also some links for Client API are missing (eg how to access it from Go).

@barakmich
Copy link
Member

The Go API is being discussed in #64, but it is possible to jump in now if there's something you want to do.

As for explaining use cases; that's a fair question, and may be a good starting point for a talk.

The other short answers being, it can definitely be used for real-time access, and the data can be universal, but given that it's still early and Postgres has been around for decades, that's up to you.

@jonathanmarvens
Copy link

Hey, guys.

@barakmich First of all, I just wanna apologize because I made some promises I haven't been able to push up due to work ... I've been so busy with work stuff, man 😞.

However, I think this question is important, so I just wanted to pitch in real quick and give my thoughts, since we've been using Cayley at my startup since day 3 or 4 of the project being open-sourced.

At my startup, we doing some interesting things in the photo space at the intersection of graph theory, network science, and deep learning. This requires processing LOTS of graph data (hundreds of millions of edges) and trying to learn something from every node and edge. While we've built our own graph processing tool (it can be used as a graph database, but that's not how we use it), using Cayley has helped GREATLY for playing with and understanding our graph data. Another thing for us is that although our "online" data is represented as a legitimate graph in memory (and for querying), we rely on, use, and create lots of RDF-based data (the RDF model is ideal for our use case) and since Cayley can essentially be used as a triplestore, this has been great for us as well.

Hope this helps.

- Jonathan

P.S. Again, @barakmich, sorry for not having a couple PRs yet, man.

@barakmich
Copy link
Member

@jonathanmarvens No worries -- hey, if it's working out for your startup, that's awesome and I'm glad to hear it :)

@barakmich
Copy link
Member

Closing this, for lack of actionable things, but do know that it served as a bit of inspiration for http://www.meetup.com/NYC-GDG/events/194717652/

@robert-zaremba
Copy link
Author

For having a clear use-case overview one need to know CAP parameters and availability of transactions. Can you describe them in a documentation / readme?

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