Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing ConcourseDB vs CouchDB, the Slant community recommends CouchDB for most people. In the question“What are the best NoSQL databases for web applications?” CouchDB is ranked 4th while ConcourseDB is ranked 11th. The most important reason people chose CouchDB is:
CouchDB works very well even when the network is physically partitioned
Specs
Question Ranking
Pros
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.
Pro Works well between physical network partitions
CouchDB works very well even when the network is physically partitioned
Pro Available
CouchDB is considered an available DMS according to the ACP theory of database management. As such it allows every client to always read and write
Pro Useful for applications where versioning is important
CouchDB is mostly used in applications where a large amount of data needs to be accumulated and where data only changes rarely.
Pro Changes API
You can use the RESTful API to listen for changes in your database, which is something most databases can't do. It makes it really easy for clients to keep their view of data up-to-date.
Pro RESTful API
Since everything is stored as a JSON document and served over HTTP, it's perfectly suited for communicating with client-side javascript, with or without middleware.
Cons
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.
Con Can only achieve consistency through replication and verification
Since CouchDB is considered an AP (Available, Partition-Tolerant database management system), it is not really consistent (not all clients can have the same view of the data consistently) and the only way to achieve some "eventual consistency" is through replication and verification of data.
Con Uncertain future
After a very promising start, development began to drag after major supporters like Canonical, Selenium and CouchOne either shut down or moved to other tools. Development has begun to pick up again.
