There's a general comparison on our website: https://www.arangodb.com/why-arangodb/arangodb-vs-mongodb/ https://www.arangodb.com/why-arangodb/arangodb-vs-mongod

There's a general comparison on our website: https://www.arangodb.com/why-arangodb/arangodb-vs-mongodb/ https://www.arangodb.com/why-arangodb/arangodb-vs-mongodb/ One major difference is that ArangoDB has full support of transactions across collections. Also while MongoDB now has limited graph functionality, ArangoDB is actually optimized for graph queries and can do arbitrary traversals and joins very efficiently. The problem with Gremlin/OpenCypher is that they are primarily designed as graph query languages. ArangoDB takes a multi-model approach and many ArangoDB users focus on documents first and add in graph queries as an optimization step as their products mature. AQL is designed to be very easy to learn and mixes the document and graph paradigms seamlessly, embracing the multi-model nature of the database. Personally I think that starting with a blank slate was the right choice compared to other multi-model databases that have found it necessary to extend a subset of a standard query language with their own proprietary additions to achieve the same goals.