CouchDB vs MongoDB: What are the differences?
CouchDB and MongoDB can be categorized as "Databases" tools.
"JSON" is the primary reason why developers consider CouchDB over the competitors, whereas "Document-oriented storage" was stated as the key factor in picking MongoDB.
CouchDB and MongoDB are both open source tools. It seems that MongoDB with 16.3K GitHub stars and 4.1K forks on GitHub has more adoption than CouchDB with 4.24K GitHub stars and 835 GitHub forks.
According to the StackShare community, MongoDB has a broader approval, being mentioned in 2189 company stacks & 2218 developers stacks; compared to CouchDB, which is listed in 61 company stacks and 31 developer stacks.
What is CouchDB?
What is MongoDB?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using CouchDB?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Used MongoDB as primary database. It holds trip data of NYC taxis for the year 2013. It is a huge dataset and it's primary feature is geo coordinates with pickup and drop off locations. Also used MongoDB's map reduce to process this large dataset for aggregation. This aggregated result was then used to show visualizations.
MongoDB fills our more traditional database needs. We knew we wanted Trello to be blisteringly fast. One of the coolest and most performance-obsessed teams we know is our next-door neighbor and sister company StackExchange. Talking to their dev lead David at lunch one day, I learned that even though they use SQL Server for data storage, they actually primarily store a lot of their data in a denormalized format for performance, and normalize only when they need to.
Nearly all of our backend storage is on MongoDB. This has also worked out pretty well. It's enabled us to scale up faster/easier than if we had rolled our own solution on top of PostgreSQL (which we were using previously). There have been a few roadbumps along the way, but the team at 10gen has been a big help with thing.
Document (JSON) DB.
- - queries must be pre-defined as views (not as flexible as query formulation on the fly)
- - community and ecosystem not as large as mongodb
- + PouchDB is an excellent JS library to interact with CouchDB or even work in offline-then-sync moce
We are testing out MongoDB at the moment. Currently we are only using a small EC2 setup for a delayed job queue backed by
agenda. If it works out well we might look to see where it could become a primary document storage engine for us.
Used for proofs of concept and personal projects with a document data model, especially with need for strong geographic queries. Often not chosen in long term apps due to chance data model can end up relational as needs develop.
By being built on, of, in and around CouchDB, Smileupps offers to its customers secure and reliable CouchDB hosting and a CouchDB-based app store to build and sell serious business-enabled web applications