I'm with you on the memory thing. It kinda scares me since I'm boot strapping my startup. Linode $10/1 GB server is really tempting. Fortunately, I think that e

I'm with you on the memory thing. It kinda scares me since I'm boot strapping my startup. Linode $10/1 GB server is really tempting. Fortunately, I think that even with a few smaller Linode instances, I can reasonably base on ArangoDB such that I scale it when my app needs to scale. To press on about issue one, in a general sense, what I like about ArangoDB is the thoughts behind it and the continous execution of those thoughts. Is memory an issue? Possibly. Is the team aware of memory-mapped files' limitation? Yes. Will they improve in future release? Probably based on the excellent work they've produced in the past. Their implementation of graphs is interesting to the general point. ArangoDB presently stores relationships in a collection. This won't scale. Neo4J's free book on graph databases explains why[1]. Fortunately, the ArangoDB team has a graph API (I'm in the process of implementing that now for Clojure [2]). This means, when they move to a more scalable architecture, I and anyone who use the API should be golden. By the way, I'm a proponent of ArangoDB. Just in case that wasn't clear. I've got several projects for it. [1] - http://graphdatabases.com/ http://graphdatabases.com/ [2] - https://github.com/deusdat/travesedo https://github.com/deusdat/travesedo