Apache CouchDB is an HTTP + JSON document database with Map Reduce views and bi-directional replication. The Couch Replication Protocol is implemented in a variety of projects and products that span computing environments from globally distributed server-clusters, over mobile phones to web browsers.
N/A
MongoDB
Score 8.6 out of 10
N/A
MongoDB is an open source document-oriented database system. It is part of the NoSQL family of database systems. Instead of storing data in tables as is done in a "classical" relational database, MongoDB stores structured data as JSON-like documents with dynamic schemas (MongoDB calls the format BSON), making the integration of data in certain types of applications easier and faster.
$0
per month
Pricing
Apache CouchDB
MongoDB
Editions & Modules
No answers on this topic
Shared
$0
per month
Serverless
$0.10million reads
million reads
Dedicated
$57
per month
Offerings
Pricing Offerings
CouchDB
MongoDB
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Fully managed, global cloud database on AWS, Azure, and GCP
More Pricing Information
Community Pulse
Apache CouchDB
MongoDB
Considered Both Products
CouchDB
Verified User
Anonymous
Chose CouchDB
Open Source, and freely able to install it on any OS you desire (the big 3, anyways) CouchDB was selected for that, it's early-adoption of JSON and its mobile-friendly environment. Also, I have used it off and on in various non-professional projects, and it was really one of …
Compared to MongoDB, CouchDB's Map-Reduce paradigm poses a steeper learning curve for SQL users. However, CouchDB's master-master replication is an advantage of implementing a load-balanced solution. Even though, currently, CouchDB has strong community support, as an open …
MongoDB and CouchDB are both document stores, but their concurrency models and ability to scale are very different. MongoDB cannot replicate / shard over unreliable links and network partitions have been the cause of data loss in the past. MongoDB has an easier query language …
It has been 5+ years since we chose CouchDB. We looked an MongoDB, Cassandra, and probably some others. At the end of the day, the performance, power potential, and simplicity of CouchDB made it a simple choice for our needs. No one should use just because we did. As I said …
S3 blew this out of the water, we can get over 30 files a second, almost no failures, auto backed up, don't need our own server, and a much simpler interface with PHP Laravel.
We looked at MongoDB and Firebase. MongoDB gives us the best working db engine with a very intuitive design. However, it does not work as well offline. Firebase was extremely hard to create searching and indexing. Using a third-party to search didn't work for us or at least it …
I have briefly used MongoDB in other products, and it proved that it had better integration capabilities with Ruby on Rails and node.js software platforms, more than CouchDB. But I never had the chance to actually replace CouchDB with MongoDB in the current product to see what …
The environment I work in is somewhat unique in that we use both MySQL and MongoDB. However, each is used for specific purposes that the other is not well suited for. MongoDB is not a relational database like MySQL, so it serves as the perfect place to dump key bits of data for …
We have [measured] the speed in reading/write operations in high load and finally select the winner = MongoDBWe have [not] too much data but in case there will be 10 [times] more we need Cassandra. Cassandra's storage engine provides constant-time writes no matter how big your …
Both Couchbase and MongoDB are document-oriented NoSQL databases, so they have very similar features. While they do have some fundamental differences in terms of how they scale, shard, etc. the one key reason why we went with MongoDB is its availability and support from the …
The flexible structure underlying MongoDB's construction is not found in other competitors; the ability to easily change the structure without affecting other stored documents. It is very ideal for projects that you cannot predict that the structure will change this way. Of …
Implementing new features for application becomes simpler with MongoDB since you don't need to run database migration scripts just to for example add new fields to database only to store some extra data. This is especially good for the deployment phase. Only new version of …
MongoDB is a robust and scalable db which offers a lot of cool features out of the box. Being open sourced and backed by a great community with developer tools like mongo compass , it was a no-brainer to go for it. It has connectors in almost all programming languages and is a …
I would say Cassandra is better than MongoDB since it has the backing of Facebook to it. Its inherent properties like versioning put it into the other category of columnar databases, but it's one of the NoSQL databases which you should definitely consider for your organization …
This tool is only capable of reading real-time data very smoothly. The transition was also pretty easy and quick. Syntax is also very easy and comfortable to learn and use.
The main reason for selecting is that it works very fast under the Intellijet module environment and we …
In our early development days we weighed NoSQL databases like MongoDB with RDBMS solutions like MySQL. We were more familiar with MySQL from past experience but also were wary of painful data migrations that slowed down development iterations and increased the risk of outages …
Snowflake and Redshift are much more mature and have been around longer. MongoDB is definitely much less expensive and if you are in a startup, this is an almost for-sure option. Redshift can be slow and Mongo is much faster. However, losing the relational database aspect could …
It's very fast and easiest to use. Many companies are using this nowadays. It's helped to complete many software products very quickly so the year income has increased compared with last years. Many programmers are now leaning this tool as back end developers so that we changed …
MongoDB is our go-to database solution for any project, and the more we work with it the more we love it. Some say that NoSQL is pointless... Our developers wholeheartedly disagree, because they love working with it. Though both NoSQL and SQL have their purposes, in most …
Your default choice should not be MongoDB in my opinion. Most user-facing systems are relational by nature so a well known and reliable SQL database would be easier to maintain and simpler to develop long term. If you highly value speed of development go with firebase. If you …
It does not belong to certain cloud platforms. MongoDB is an independent program that works with any cloud platform including Amazon Web Services and the Google Cloud Platform. For companies who want to maintain a cloud agnostic structure, MongoDB is a great choice for NoSQL …
MongoDB and Cassandra are both database system from the NoSQL family. MongoDB can be used in lots of use cases while Cassandra has a specific usage. There are some features that MongoDB provides efficiently while Cassandra doesn't and vice-versa. Like, you can update the data …
We tend to choose MongoDB when we're faced with a particular situation: we know that we need a NoSQL database in general, and want an open-source implementation that allows us to prevent against platform lock-in. Amazon's new DocumentDB product even allows us to choose to use …
It's good as a general JSON document store and basic map/reduce system. For more specialized tasks like message queuing, graph traversal, streaming metrics aggregation, or arbitrary table joins, I'd recommend another database.
MongoDB [is] great at storing JSON data grouped into "collections". In this format, you can store any JSON documents and conveniently categorize them by collections. The JSON document contained in MongoDB is called binary JSON or BSON and, like any other document in this format, is unstructured. Therefore, unlike traditional DBMS, any kind of data can be stored in collections, and this flexibility is combined with the horizontal scalability of the database. It should be noted that MongoDB does not have links between documents and “collections” (this is partially compensated by the Database Reference - links in the DBMS, but this does not completely solve the problem). As a result, a situation arises in which there is a certain set of data that is not related to other information in the database, and there is no way to combine data from different documents. In SQL systems, this would be an elementary task.
Easy to learn. When I picked up MongoDB for the first time, I had little background in database management or modeling. If you have a background in javascript (and JSON)... then you can figure out how to use MongoDB pretty fast.
Fast performance.
It's relatively easy to set up in certain environments because there are lots of ready-made solutions out there.
There's a lot of support in the existing ecosystem for it —, especially in the node.js realm.
Query syntax is pretty simple to grasp and utilize.
Aggregate functions are powerful.
Scaling options.
Documentation is quite good and versioned for each release.
As a highly distributed database system, CouchDB naturally has strong high availability with traffic load-balancing capability. It is also easy to scale and replicate data in a cluster for redundancy. However, there is still some room for query performance improvement in the future.
MongoDB is one of the most famous non-relational databases in the world, there are famous active projects that use this database. I think that the same company that develops the database gives you the online induction totally free is something that really is very positive. Accounts with a first-class support to be able to relate the correct implementation of the database, in addition to teaching you the best practices to optimize your projects, I believe that with this decision it is more than obvious which is the best decision at the time of seeing with which database to work.
Couchdb is very simple to use and the features are also reduced but well implemented. In order to use it the way its designed, the ui is adequate and easy. Of course, there are some other task that can't be performed through the admin ui but the minimalistic design allows you to use external libraries to develop custom scripts
It is one of the reasons why we prefer it to store documents in a JSON-style format, to access the desired document very quickly regardless of its size, to be readable by human eyes, and to be easily scalable and manageable.
I have reached multiple times to the MongoDB community for the help and they have provided each and easy solution for every problem. Over the internet and on stack overflow many people responds over the challenges. Now this tool is very much used in every company and projects so internally many people are there to give a support.
it support is minimal also hw requirements. Also for development, we can have databases replicated everywhere and the replication is automagical. once you set up the security and the rules for replication, you are ready to go. The absence of a model let you build your app the way you want it
While the setup and configuration of MongoDB is pretty straight forward, having a vendor that performs automatic backups and scales the cluster automatically is very convenient. If you do not have a system administrator or DBA familiar with MongoDB on hand, it's a very good idea to use a 3rd party vendor that specializes in MongoDB hosting. The value is very well worth it over hosting it yourself since the cost is often reasonable among providers.
Open Source, and freely able to install it on any OS you desire (the big 3, anyways) CouchDB was selected for that, it's early-adoption of JSON and its mobile-friendly environment. Also, I have used it off and on in various non-professional projects, and it was really one of the first exposure to databases in my career
The environment I work in is somewhat unique in that we use both MySQL and MongoDB. However, each is used for specific purposes that the other is not well suited for. MongoDB is not a relational database like MySQL, so it serves as the perfect place to dump key bits of data for quick retrieval later. This is something we can't easily do with MySQL. On this smaller database, MongoDB also lets us retrieve data more quickly with its fast and efficient querying.
Biggest impact on our business has been that CouchDB has been pretty invisible from a cost or issues perspective. It just works.
We use the Apache releases, so it's free. Of course there is a cost to "free" - we have invested time to become fluent in using and understanding CouchDB. But we feel the investment was well worth the effort and we have a solid, fundamental technology to our products that "just works".
There are some things we do - SaaS vs self-hosting - that have probably been kept simple by using CouchDB. Overall, we are extremely happy with CouchDB.
We can make more open and flexible systems due to its easy adaptation to new evolutions in web applications.
In the latest versions it offers support for different transactions and we could carry out real tests related to the concurrency of the application.
MongoDB allows you to have distributed clusters, which improves the speed of the queries by reducing the latency that exists between the database cluster and the service that executes the query.