DEV Community

Discussion on: Graph databases: which one?

Collapse
rasjonell profile image
rasjonell • Edited

I've been using ArangoDB for a while now. Although it's not as mature as Neo4j, it's constantly evolving and has some distinctive features that make it worth trying. It has a wide range of drivers so language wouldn't be a barrier.

Collapse
ayyappa99 profile image
Ayyappa

Can you share your experiences on ArangoDB? I'm looking to use it on a high traffic app and wondering if its a good fit.

Collapse
rasjonell profile image
rasjonell

I really enjoy working with ArangoDB. It's not just a database but, thanks to the Multi-Model Datastore and Foxx Microservices, it can actually be your applications whole data-layer. Meaning that you don't need a separate K/V store to hold session cookies as you can have a K/V store inside ArangoDB. You can also have queues to create recurrent/delayed jobs, and you can manage all of this with Foxx Services that sit inside your database have native access to in-memory data!

Thread Thread
ayyappa99 profile image
Ayyappa

Really appreciate for answering :) I have couple of questions, if you don't mind.

Do you see any limitations w.r.t key/value store or document data storage?
Till what traffic I don't need to worry about performance?
What are the average latency values for key-value or document storage?

Thread Thread
rasjonell profile image
rasjonell

I've mostly used the native graph model. The only time I used the k/v model for session storage I never hit enough traffic to think about performance tuning, but the community and the ArangoDB team on slack and stack overflow are really helpful if you need any assistance.