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!
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?
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.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
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.
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!
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?
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.