• Advantages:
  • Considerations:
    • Their faq recommends that it not be used for Very Large (Cassandra sized) terabyte scenarios.
    • Not clear on their strategy for UserAgent access to Services (pass-thru routing or Foxx?)
    • Schema-free schemas with shapes: Inherent structures at hand are automatically recognized and subsequently optimized.
    • Querying: ArangoDB is able to accomplish complex operations on the provided data (query-by-example and query-language).
    • Application Server: ArangoDB is able to act as application server on Javascript-devised routines.
    • Mostly memory/durability: ArangoDB is memory-based including frequent file system synchronizing.
    • AppendOnly/MVCC: Updates generate new versions of a document; automatic garbage collection.
    • ArangoDB is multi-threaded.
    • No indices on file: Only raw data is written on hard disk.
    • ArangoDB supports single nodes and small, homogenous clusters with zero administration.
  • Disadvantages:
    • Trivial: their SVG graph viewer needs love.