When comparing Redis vs ConcourseDB, the Slant community recommends Redis for most people. In the question“What are the best NoSQL databases for web applications?” Redis is ranked 2nd while ConcourseDB is ranked 6th. The most important reason people chose Redis is:
Redis has [great docs](http://redis.io/documentation), an active mailing list, and a github community.
Ranked in these QuestionsQuestion Ranking
Pro Good support
Redis has great docs, an active mailing list, and a github community.
Pro Redis uses the BSD license
This means that it is able to be used in a commercial product if one wants.
Pro There are numerous client libraries and frameworks to make redis more powerful
For Node.JS for example you can get something similar to what Parse.com was offering by using Node ORM.
Pro Redis is written in ANSI C and therefore doesn't have a VM
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.
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 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.
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.