When comparing ConcourseDB vs MongoDB, the Slant community recommends MongoDB for most people. In the question“What are the best NoSQL databases for web applications?” MongoDB is ranked 5th while ConcourseDB is ranked 11th. The most important reason people chose MongoDB is:
Miles above other databases in educational resources.
Specs
Ranked in these QuestionsQuestion 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 Perfect documentation and tutorials
Miles above other databases in educational resources.
Pro Great speed
MongoDB queries can be very fast because the data is usually all in one place and can easily be retrieved in a single lookup. But this is true only when the data is truly a document. When it's trying to emulate a relational model it starts to become really slow because it may have to perform many independent queries to retrieve a single document.
Pro Uses JSON
As Node.js uses JavaScript there's no need to map the returned JSON data from MongoDB, as JavaScript is a superset of JSON. Essentially solving object-relational impedance mismatch by its very nature. Working with JSON is also easier overall as it more easily fits into how you would represent data on the client.
Pro Doesn't require a unified data structure
Mongo is very flexible in that it doesn't require a unified data structure across all objects. So it's rather easy to use.
Pro Easy to scale
MongoDB has powerful sharding and scaling capabilities for when the data stored in the database gets so large that a single machine may not be able to store all of it. Sharding solves this problem through horizontal scaling. Mongo gives developers the ability to easily and painlessly add or remove as many machines as needed.
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 Reported to lose or corrupt data
MongoDB is famously known for leaking and losing data over time.
Con Document Stores may be not suited for relational data
MongoDB has no JOIN, all relations are supposed to be resolved client-size which entails additional requests to the server.
Con Need many search features
Though it is possible to index and search text in documents in MongoDB 4.0 in multiple languages. The indexing and search is not as powerful as for example Elastic Search. For instance not being able to search for only parts of words.