When comparing ArangoDB vs ConcourseDB, the Slant community recommends ArangoDB for most people. In the question“What are the best NoSQL databases for web applications?” ArangoDB is ranked 4th while ConcourseDB is ranked 6th.
Ranked in these QuestionsQuestion Ranking
Pro Easy cluster setup
Pro Supports joins
Unlike many NoSQL databases, ArangoDB does support joins in AQL queries.
Pro Transaction save
You can use ACID Transactions for short and small data retrieval and/or modification operations in ArangoDB.
Pro Document and graph-orientend
You can model your data as documents or as a graph - no data model lock-in. You can even combine both models and use them in a single AQL query.
Pro Powerful Java Driver (Sync & Async)
ArangoDB has a very good Java Driver for synchronous and asynchronous. In addition the team there is working on a Spring Data integration.
Pro Can easily query data from any point in the past
Because of its powerful version control capabilities, Concourse can easily and painlessly query and get data from any point in the past.
Pro Fully ACID compliant
ConcourseDB is known to have a very holistic approach to robustness and data integrity which is reflected by it being fully ACID compliant.
ConcourseDB has always been strict about making sure data is valid before allowing it into the database, and there is no way for a client to bypass those checks.
Pro Built-in version control
Concourse tracks versions of your data by default. This way you can easily edit data without being afraid of losing anything since Concourse can easily revert to a previous state.
Con Not very popular
Since ConcourseDB is not a very popular solution among developers, it may be hard to find libraries or SDKs to easily integrate it into any platform with which you are developing.