CouchDB Reviews & Product Details


What is CouchDB?

CouchDB is a database that completely embraces the web. Store your data with JSON documents.

Write a Review

CouchDB Profile Details

CouchDB Profile Details

Vendor
The Apache Software Foundation
Description
Community-led development since 1999. FoundationProjectsPeopleGet InvolvedDownloadSupport ApacheHome. We consider ourselves not simply a group of projects sharing a server, but rather a community of developers and users.
Company Website
Year Founded
1999
HQ Location
Wakefield, MA
LinkedIn® Page
www.linkedin.com
Employees on LinkedIn®
1,824
Twitter
@TheASF
Twitter Followers
53,780
Show moreShow fewer

Companies Using CouchDB

Button
Rosetta Stone
SendHub
Floored
Tabtor
Speakaboos
Attendify
Stride Health
Rinse
Cinarra Systems
GAIN Fitness
ShoppinPal

CouchDB Reviews

Filter Reviews
Filter Reviews
Sort by
Ratings
Company Size
User Role
All Industries
Write a Review
1-45 of 45 total CouchDB reviews

CouchDB Reviews

Write a Review
Filter By
Connections
Show reviews that mention
1-45 of 45 total CouchDB reviews
Copy Review URL
Ingeniero de sistemas
Mid-Market
(51-200 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"CouchDB is free and open source, a marvel"

What do you like best?

CouchDB is the easiest database manager to install of all the ones I've tried. In addition, maintenance is very easy. On the other hand, it scales the documents very well. It has a replication protocol that is very useful for creating servers.

What do you dislike?

There is not much online documentation about this database manager and the learning curve is usually a bit slow because despite not being a complex software, learning to use the interface requires some time.

Recommendations to others considering the product:

CouchDB is solid and the only thing we have invested is time to learn how to use it so that we can exploit all its characteristics. We believe that it is an important technology in our business. I recommend it.

What problems are you solving with the product? What benefits have you realized?

In CouchDB we store information about employees, customers, invoices, support tickets, among other things. This manager keeps all the data organized and allows us to view them in a web page with JSON.

Copy Review URL
Programmer
Internet
Small-Business
(11-50 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Easy To Use NoSQL Database"

What do you like best?

CouchDB will be easy to pick if you are already familiar with JavaScript and JSON. The data is stored as JSON, and you use MapReduce functions in JavaScript to query the data. This makes it a nice complement to a full-stack JavaScript application running Node and a JavaScript front end.

If it fits the requirements of your application, you can use CouchDB as a REST API, and forgo the need for an additional API implementation on the server.

Easy to get started and good documentation to learn how to use the database. There is a GUI available to easily view your data.

What do you dislike?

The GUI that is available is not always intuitive. When I was first gettings started with it there were a few things that did not work as I expected them to that caused frustration.

The MapReduce query method can be hard to adjust to if you are used to traditional SQL databases. It is very powerful, but takes some time to get familiar with it.

Recommendations to others considering the product:

As with most database decisions, you need to understand the needs of your application. CouchDB is well suited for document storage, but you will probably have an easier time with something else for a typical CRUD app.

What problems are you solving with the product? What benefits have you realized?

I have used CouchDB to store documents in a writing application. It was easy to sync documents with the database on the fly as you edited the documents. CouchDB was very flexible, which made storing different types of documents very easy.

Copy Review URL
Developer
Marketing and Advertising
Mid-Market
(201-500 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"A flexable framework for map-reduce based REST APIs."

What do you like best?

CouchDB is vastly more than just a database - it's practically a website framework. You interact with it using plain Javascript, JSON, and HTTP for everything. No need to write an API or backend administration tools and you get user management / access control for free. Unless you're dealing with multiple terabytes of data, or a model that requires instantaneous & frequent document updates, Couch is all you need to get up and running.

Plus, because of CouchDB's change-log model, synchronization between multiple master nodes is trivial. With PouchDB (based on Couch) you can even store a copy (or subset) of your database on the user's device, or in the web browser.

What do you dislike?

As of 2016-10-19, singular CouchDB 2 nodes are still a bit slower than CouchDB 1.7 (probably due to code changes that make clustering easier) and there isn't much documentation for deploying CouchDB to Kubernetes yet. Also, the map/reduce workflow, while incredibly simple and elegant, isn't quite as efficient as a system like Apache Spark.

What problems are you solving with the product? What benefits have you realized?

Starting up and running small (less than 1TB of data) APIs. I love using Couch for this, because you can immediately expose it to the web and start using it. You can even serve basic resources from it like images, JS, and HTML (even though it isn't the most efficient way to store those)

Copy Review URL
Managing Director, Founder
Media Production
Small-Business
(2-10 employees)
Validated Reviewer
Review Source
Copy Review URL

"Database of the future: Cluster Of Unreliable Commodity Hardware"

What do you like best?

CouchDB is a way to rethink data on the web. It is so much more than a database, it is a way to structure information, organise it and make it available in whatever medium might be necessary. If you have data and you want to serve a web page straight from CouchDB, you can, since its views are completely customisable and can spit out whatever you want it to.

CouchDB is some of the most resilient software I've ever used. It was clearly made to be run on large clusters of cheap unreliable servers and fulfils this role extremely well. Its replication protocol makes it easy to create networks of servers that can survive anything.

What do you dislike?

Development and enthusiasm for CouchDB seems to have tanked, and it's massive development effort seems to now be focussed on support for large users. It would be nice to get some of the world changing spirit back.

What problems are you solving with the product? What benefits have you realized?

CouchDB enables us to use a stack as lean as possible. It is most of the software we need to run things, be it saving tonnes of data, files or serve pages. It works especially well for this on a small scale but we have trouble finding out how to scale this effectively.

Copy Review URL
Founder
Management Consulting
Small-Business
(11-50 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Best noSQL Database for Beginners : )"

What do you like best?

As someone who isn't a full time developer, and is self-taught, I love CouchDB. It has many features that just make it easier to get started with and use. First, it's got a graphic interface, so I can go in an look at my data very easily. Second, everything in CouchDB is JSON, so it's already in a format I'm used to using everywhere else. Views are written in JavaScript, which I already know from web dev. And, to boot the API is just HTTP. The advanced features are cool as well. Database syncing and replication are awesome. And, so far I've never lost any data!

What do you dislike?

I don't like that there are so many branches of CouchDB. Cloudant has a totally different GUI. Couchbase is weirdly different. There's too many interpretations. CouchDB would be great if people just implemented it as Apache puts it out there.

Recommendations to others considering the product:

The "definitive guide" is okay: http://guide.couchdb.org/index.html but playing with it yourself is the best way to get acquainted. Also, check out PouchDB at some point. If that project is successful, I think the two together could be a real powerhouse for web app development.

What problems are you solving with the product? What benefits have you realized?

I'm using CouchDB for very simple things, storing user info, website data, data for events my company hosts, and so on. Everything's neat and organized, and if I ever need to look at my data differently, I can pull our a view and throw it into a webpage with D3.js and get really graphical.

Copy Review URL
Ssr. Front-end Developer
Internet
Enterprise
(1001-5000 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Thinking Documentally"

What do you like best?

As opposed to RDBMS, documental databases (in particular, CouchDB) allow to quickly prototype and develop a fully-functional application. Being easily installed, configured and deployed, CouchDB keeps you from wasting time around tinkering settings, allowing you to focus on what's really important.

Plus, the idea of using JavaScript as a query language via MapReduce expressions is great for developers, since you don't need another new language for your database operations (if you're not used to SQL).

What do you dislike?

Despite being so easily deploy, I find that its Web Admin interface lacks some functionality. I get it - it's a documental database, and everything is treated that way, even its authentication & authorization scheme. But it's not *that* intuitive to setup users and roles, as one would expect coming from a RDBMS world.

Recommendations to others considering the product:

Always get the latest version.

Always read the documentation. Sometimes, CouchDB introduces breaking changes in their API, and you'll have no idea why your app is failing if you haven't "read the Good Book".

What problems are you solving with the product? What benefits have you realized?

I'm working on a real estate management and search platform. The main issue at hand was the diversity of data that a realtor can report about a household. There's a vast amount of features that aren't the same from realtor to realtor. So, the idea was to handle a baseline structure (the common denominator of house features) as well as support realtor-specific data, configurable from a dashboard. These specific features, however, must be used by the search engine as well. So, anyone looking for a new home can get to be extremely specific on terms of filters. For instance, if I want a house with two bedrooms, a bathroom, a fully-equipped kitchen, within 5 blocks of the nearest hospital and a supermarket 2 blocks away and with a garage big enough for a 4x4 vehicle, the search engine will harness both generic and specific data structures. CouchDB, with its flexible structure, allows to easily handle dynamic payload structures.

Copy Review URL
CTO
Computer Software
Mid-Market
(51-200 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"As CTO, I selected CouchDB from other databases to power our SaaS product offering."

What do you like best?

The ease of integration of CouchDB into our technology stack was excellent. Our stack is based primarily on JavaScript (nodejs) and adopting CouchDB was a very easy sell in our organization from this point of view alone.

What do you dislike?

The lack of redundancy built in to the core CouchDB offering is our only misgiving. This is mitigated somewhat by the BigCouch companion product, but we would like to see the ability to deploy a single database over multiple shards built into the core.

Recommendations to others considering the product:

The only misgiving we have is its lack of in-built redundancy through replication. It is possible but tricky to set this up with the stock CouchDB distribution. The BigCouch project offers a promising alternative and I believe plans are in place to merge it into the core distribution as the project matures, but this has not yet happened. Otherwise, I would highly recommend CouchDB for its flexibility, ease of use and performance.

What problems are you solving with the product? What benefits have you realized?

We have rapidly evolved our data models to align with changes in our business. For this, we needed the flexibility and performance of a nosql database. CouchBD proved extremely easy to administer, was performant and fit well into our technical architecture (nodejs on the backend). With very little effort, we have been able to adapt to changes in our business needs.

Copy Review URL
Software Engineer
Information Technology and Services
Mid-Market
(501-1000 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Using couchDB in my hobby project"

What do you like best?

Replication mechanism and update streaming capabilities, which proven very useful on front end development side by using PouchDB

What do you dislike?

Querying. Getting concrete item by more than one field becomes complicated task. It is only easy to get one item by one field, or all items at once.

Recommendations to others considering the product:

Understand that this database is designed to slightly different use cases than other, popular, NoSQL databases. Get quick course on it, understand its' benefits and problems before doing any decisions.

What problems are you solving with the product? What benefits have you realized?

Movie recommendations. Algorithm is partly based on users' action log, for which couchDB is proven to be very useful. By having custom views, it is easy to get some data slices which are vital for algorithm to function, and are non-trivial task in other databases. Another benefit is versioning. It is easy to track internal changes done on user object.

Using PouchDB, it became very easy to provide user with real time data on front end. Any changes on user object are instantly replicated on front end.

Copy Review URL
CEO
Small-Business
(2-10 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Slow start but on the right track"

What do you like best?

I like the default sync features of CouchDB. This is truly the reason I came across using couchDB in my mobile product. I also like that it is a no-sql db and the drivers are really just a HTTP-REST API.

What do you dislike?

To get started with CouchDB was a nigthmare. It was extremely hard to understand and get a grip on how to fully use it. There is much information out there that is CLEAR. There is a lot of unclear information even to a veteran coder like myself I just didn't get it for about 4 days.

Recommendations to others considering the product:

If you need data to sync from mobile to web or one server to another. THIS IS YOUR TOOL. Once you get pass the learning curve it is easy sailing. You can literally get back on the couch because you will be coding less.

What problems are you solving with the product? What benefits have you realized?

The ability for my users to work offline is ONLY done by the use of CouchDB. This is truly amazing. The power of CouchDB is great. Even though it started off rough for me, it is now my default DB when developing an application. I was a champion of MongoDB, but now I evaluate CouchDB first and Mongo second.

Copy Review URL
Computer programmer
Computer Software
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"A Database for the Web"

What do you like best?

I like the restful web api, the fact that you don't need any client libraries to work with it, the focus on data isolation -- by allowing you to segregate your data in multiple database files,all managed by a single server instance and also within the same database with the help of map reduce views. And the fact that it's written in erlang, a highly concurrent programming language, makes the deal even sweeter :)

What do you dislike?

You need to think about your queries *beforehand*. Since the only querying mechanism that couchdb supports is via map/reduce indexes, rebuilding the indexes can prove to be expensive in case you change the the way you query your data. Might be a blessing in disguise though?

Recommendations to others considering the product:

If you can be patient and take time to learn map/reduce queries you'll find couchdb to be one of the most programmer friendly databases.

What problems are you solving with the product? What benefits have you realized?

Couchdb allows me to have a flexible schema so I can accommodate the changing business requirements. At the same time it has functions that allow me to validate the data that is stored. So I have the flexibility of a schemaless store and the reliability of a rigid schema database.

Setting up automated backups in couchdb is easy as a pie. All you need to do is make an http call and you can have your data set replicated across distributed couchdb instances. With couchdb you can be certain that your data will always be safe and available when you need it.

It's cookie authentication feature can be reused in the application layer to implement complex access control lists. it's restful interface and focus on data segregation allows me to build independent microservies that can be moved to their own instances should the need arise.

Copy Review URL
Senior Computer Scientist / Scrum Master
Computer Software
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Not distributed yet solid document oriented DBMS"

What do you like best?

The best feature of this DBMS is the _changes stream that provides live stream of all changes happening in the database. This allows for implementing any synchronization system that may replicate all databases around the world exactly how we want to.

What do you dislike?

The fact that CouchDB is not an distributed database. We ended up using BigCouch that only makes CouchDB distributed and CouchDB is currently merging with BigCouch (CouchDB 2.0 Alpha). Only if this version will be finised we will be able to use this database once again (replication feature is not what we are looking for).

Recommendations to others considering the product:

If someone needs something like CouchDB only distributed - CouchBase is very nice alternative. Most likely with better support and with additional cache layer (memcached).

What problems are you solving with the product? What benefits have you realized?

All we need is document database that stores some metadata and allows data replication across multiple datacenters. We also needed this database to be distributed which is not a case.

Copy Review URL
Software Developer
Retail
Mid-Market
(51-200 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Great - As long as it fits your use case"

What do you like best?

Ease of document storage. It is very fast to get up and going. Of course since everything is document based, it is very flexible to data changing

Replication is also a huge plus. Anybody that has ever set up a MySQL slave would appreciate how easy replication is with CouchDB

What do you dislike?

Views and the lack of ad-hoc queries. Views are inflexible once you get into a production environment. If I were to change a view on a production machine, it would lock up the entire design document until CouchDB was able to re-index. There are ways around this, but still pretty inconvenient

Recommendations to others considering the product:

Make sure it fits your use case. I would not say that CouchDB is a silver bullet by any means. But under the right circumstances, it is definitely the right tool for the job

What problems are you solving with the product? What benefits have you realized?

Syncing data across multiple machines. CouchDB allows us to replicate large data sets without having to worry about the intricacies involved in developing a homemade solution for this.

Copy Review URL
CI
Small-Business
(2-10 employees)
Validated Reviewer
Review Source
Copy Review URL

"Small quick projects only"

What do you like best?

shared capabilities,

sync filter is amazing.

map reduce indexing

easy deployment, ready setup for windows, Mac -- this what i use..

fuxton replication task make life easy to transfer data from server to another.

pouchdb integration for offline web users..

Contributors are very collaborative in discussions to give you the best solution IF EXIST and work around if not.

Really there is many others lovely feature..

What do you dislike?

-performance is disaster. they cant or to be accurate its an open source and these people don't get paid for there work,, i saw tens or issues with feature request asking for collections to sort there data or enhancement for Indexing; that a New index consume hours to be build maybe days for big data, no strait solutions for Indexing problem all are inefficient work arounds which is not suitable in real world.. and this dive the product far away from nosql flexibility... why a developer will switch for a product will help me in some scenario and kill my app on other standard one's.

-security is the worst, we are living in hackable world and we cant set any read security permissions.. so if we set another layer to do so, this will drop the sync feature, then we don't need couchDB for anything expect its noSQL db..

-update function doesn't allow to to interact with other doc.

-no transaction.

- documentation need enhancement for quick learning.. its took me a while to mention that they have view index and map reduce index..

and also there is a big question mark for the future of this product!! there is no road map.

Recommendations to others considering the product:

really only recommended for small web app that doesn't require high level of security,

What problems are you solving with the product? What benefits have you realized?

building a quick portal with pouchdb... to enable offline and real time sync...

Copy Review URL
UC
Small-Business
(11-50 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Simple but powerful backend service"

What do you like best?

The interface to interact with the NoSQL database is a simple RESTful api. This way it can be directly accessed from a web browser. You can have a static website and a CouchDB with a very little configuration and you are ready.

You can also do offline available apps using PouchDB in the browser and CouchDB in the server.

What do you dislike?

You can not set read permissions of a single document, you have to do it in the whole database. The common solution to this is to have one database per user, but this can be not enough for more advanced cases.

Recommendations to others considering the product:

See PouchDB if you are going to implement something in the browser. If you want to have social login and registration to access CouchDB you should check superlogin or similar packages

What problems are you solving with the product? What benefits have you realized?

Having an application that can be usable when the client is offline and synced when it gets online. The replication system and the change notifications of CouchDB are great to achieve this.

Copy Review URL
CTO & Co-founder
Computer Software
Small-Business
(2-10 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"CouchDB is excellent NoSQL technology"

What do you like best?

The best feature of CouchDB is it's simplicity and use of familiar technology and concepts:

- A RESTful API means I can use any language to access it (even using shell and curl).

- It plays well in the HTTP-based world with things like proxy servers, load balancers, and SSL offloading.

- Map/reduce functions written in Javascript allow me to create dynamic web pages via lists & shows.

- APIs to assist in the integration of CouchDB with other technologies:

* change API lets me connect to Elasticsearch using logstash

* os_daemons support lets me integrate external apps and services into CouchDB environment

- Replication is simple and powerful in both master-master and master-slave modes

What do you dislike?

#1 issue with using CouchDB is lack of consolidated documentation on how to solve issues. Forgive me authors, but the books out there are not great. Be prepared to spend a fair amount of time searching for answers. If this is your first NoSQL/document database, prepare for a learning curve mostly on your own.

Recommendations to others considering the product:

Consider how fast the technologies in your stack change and the impact of these changes. CouchDB is based around common and well-know technologies: HTTP, JSON, Javascript.

When we started with CouchDB, we did not plan on using logstash or Elasticsearch. But we use both now and the integration was trivial. We can use Postman for experimenting and testing. These are just two examples of how easy it was to make CouchDB work with other things - an effort that would have been much harder if CouchDB had a binary interface, or didn't use JSON, or required us to leanr a new language to write our m/r functions.

What problems are you solving with the product? What benefits have you realized?

We are capturing large amounts of unstructured data from hundreds of remote locations and at greatly varying rates. The devices sourcing this data range from IoT (Raspberry Pi) to very large servers. We process around 500GB of new or modified data per hour - CouchDB handles this fine.

CouchDB is also used for simple messaging between systems (using change API). And we use replication to distribute software updates out to remote sites. This provides a simple and "free" reliable mechanism to update many sites automatically.

We use M/Rfor simple, single-term searches and for summary displays of data (using shows & lists). We use logstash to send data from CouchDB to Elasticsearch for more complex & fulltext searches.

Benefits have been numerous: we have scaled horizontally and vertically several times with no issues. Performance of CouchDB is excellent on mediocre hardware. CouchDB has proved to be very reliable and immune to issue caused by bugs or network errors.

Copy Review URL
Архитектор
Information Technology and Services
Small-Business
(2-10 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL
Business partner of the vendor or vendor's competitor, not included in G2 scores.

"I have been using Couch DB since 2010. More over I am a creator of Async CouchDB client for Java."

What do you like best?

Our team uses the CouchDB/PouchDB stack in our latest project. It is very important for our product to have a continued access to the data on the mobile devices when connection is down. "Offline first" is a great and most important feature of CouchDB/PouchDB for us.

What do you dislike?

The most unhandy thing is a Web Console Futon/Fauxton. It's very limited for some data manipulation scenarios. F.e. it's impossible to delete some range of documents found by query.

What problems are you solving with the product? What benefits have you realized?

We are engaged in the retail automation. We provide each shop assistant with a tablet (Android + Phonegap + PouchDB) which is synchronized with CouchDB server. This allows us to optimize many business processes and to receive detailed reports on the staff work and the movement of goods.

Copy Review URL
Software Developer
Computer Software
Small-Business
(2-10 employees)
Validated Reviewer
Review Source
Copy Review URL

"Offline first!"

What do you like best?

I'm developing a website and I expect that most users are going to be mobile ones.

Considering this, my users are going to be on slow and unstable 3g and 4g connection and they don't want to spend their data plan every time they load my website. Using couch db I can make my data that won't change be loaded only once and then saved for future uses.

Besides, it's really easy to implement, the documentation is enough for you to get started and for all my needs.

What do you dislike?

I don't think there is anything I dislike

Recommendations to others considering the product:

If you focus on mobile first, you should consider going offline first, as most users are in unstable 3g/4g connection and don't want to spend their data plan downloading data for you app multiple times. Load it once and display it multiple times.

What problems are you solving with the product? What benefits have you realized?

Using websites that downloads lots of data or makes lots of requests, you can load everything very quickly on slow 3g connections.

Copy Review URL
Programmer
Utilities
Validated Reviewer
Review Source
Copy Review URL

"Creating for example, a simple calendar anotation app in Javascript with this is super easy"

What do you like best?

As a NoSQL db engine, it uses JSON to store "documents" (In SQL known as tables), it has a simple and easily configurable REST API you can change to fill in your needs, also using your computer / server's resources pretty well so it won't fail when managed properly.

Another big plus is you can configure it almost completely right from your browser, which is a super cool thing to do sometimes you want to save some time if you're not a terminal / cURL wizzard.

What do you dislike?

When i tried it for the first time circa q4 2012, i had some real issues when doing stress tests to my infrastructure. It wouldn't handle the traffic properly and eventually go down. Something you must take in mind when using this kind of data storage is that if your CouchDB fails, some or all of your current and running queries might fail and wreck havoc in your stored data.

What problems are you solving with the product? What benefits have you realized?

I used it for a very simple task i was trying to implement for the store i was working on, it worked so good i had kind of a crush in it for a couple weeks, then i started using another engine because people at the office required me to.

Copy Review URL
AE
Small-Business
(11-50 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"CouchDB"

What do you like best?

CouchDB is super easy to get up and running. I use CouchDB for prototyping my Node.JS apps because I can learn about my data modelling on the fly, and quickly get to a place where I can start interacting with the data. CouchDB's replication is also super slick, and because of the way it versions it's documents I feel like potential conflict is well handled. The web interface is great.

What do you dislike?

I never got my head around Couch apps. I'm not sure it's a defect within the product, but it's certainly not a model that I would use for development. I also tend not to use Couch's authentication, because I don't entirely understand it's authorisation system. It's quite opaque to me.

What problems are you solving with the product? What benefits have you realized?

I often use Couch as my go to database for small data modelling exercises, or to back-end my data visualisations. It's easy to import and export the json, and adapters exist in all the languages I write in.

Copy Review URL
UC
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Development Stagnation"

What do you like best?

CouchDB is well-designed for one purpose, and one purpose only: mobile sync. It does this job fairly well, given other tools like PouchDB which can be used to sync across the two.

What do you dislike?

CouchDB is lacking in other features when compared to alternative document databases like MongoDB. No document-based security options, no backend tools or connectors, no builtin support for other platforms. Moreover, there is substantially less documentation when compared to other platforms. Also: performance-wise, CouchDB does not compare to other database engines.

Recommendations to others considering the product:

If you are going to use CouchDB, consider a commercial variant like CouchBase, otherwise MongoDB will be cheaper overall.

What problems are you solving with the product? What benefits have you realized?

We were looking for a document database to be the data backend for a hybrid web app. The app needed to work offline, so we considered CouchDB (and CouchBase) to do document sync. However, security and performance of MongoDB led us to choose it, as the app has a substantial amount of processing which is required.

Copy Review URL
Software Engineer
Defense & Space
Enterprise
(10,001+ employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"CouchDB is a great document store but is not designed for search"

What do you like best?

In many ways, I found CouchDB to be a web developer's dream database. With an HTTP interface for every aspect of its API and the Futon admin app built right in, it's incredibly easy to create and browse documents -- far easier than finding a client to browse your SQL holdings. The simple yet powerful map-reduce interface really adds a lot of value as well. Overall, I found CouchDB to be a great solution if you need the flexibility of a schema-less, JSON document store, and you are interested in very well defined queries of some of your attributes.

What do you dislike?

While the map-reduce interface provides easy indexing for specific queries, CouchDB is not designed for search. Separating "queries" from "search" is the important aspect here for me. I see CouchDB as an excellent choice when you can define indexes that slice data in a very specific way across a handful of defined attributes. However, most of my apps lately tend to be search related, with the need to query across many dynamic fields at once. They also tend to require spatial, full text, and metadata (range, etc.) filters simultaneously and CouchDB just doesn't offer that. For that reason, we've migrated to Elasticsearch as our primary data store instead.

Also, while the ability to replicate data across nodes is great, in general we didn't really end up using it and probably would have preferred a clustering solution instead of a full replication. If you are not using this feature, it can also get in the way a bit due to the overhead of carrying around potentially lots of revision metadata. For instance, we found it difficult at times to find ideal maintenance windows to perform database compaction of our revisions because we were very write heavy throughout the day.

Recommendations to others considering the product:

I highly recommend looking at using Elasticsearch if you need real search capabilities.

What problems are you solving with the product? What benefits have you realized?

I've grown to really like schema-less JSON data stores over SQL, even if I have data that has relationships. To me, "relationship" does not imply the need for relational databases. There's nothing wrong with having attributes that act like foreign keys in your document. There's no SQL-like join available in CouchDB, but for me, the simplicity of having one stop shopping and getting all attributes in a single document by denormalizing is a great win. I think organizing our data in this way has greatly simplified our data structures and increased the time to market for some of our API features.

Copy Review URL
Senior Software Engineer
Internet
Mid-Market
(501-1000 employees)
Validated Reviewer
Review Source
Copy Review URL

"Not even close to MongoDB"

What do you like best?

Apache has good ideas, most of them are very useful. CouchDB is one of those good ideas, but I wouldn't classify it as useful. It's good to have a company as Apache supporting the tool, I think it has a great future, but we still haven't found it's value.

What do you dislike?

It resolves a non-existent problem. Why would I use CouchDB and not MongoDB or ElasticSearch? It's still not clear to me. I also found the documentation extremely boring and old school and the books I found do not seem interesting.

The community is very small, I had trouble finding answers to basic questions I had during the time I was trying it.

Recommendations to others considering the product:

If you find it useful, good for you. I'd prefer MongoDB and ElasticSearch.

What problems are you solving with the product? What benefits have you realized?

I'm always looking for good database tools for various projects and modules. I currently use MySQL, MongoDB, RedShift and ElasticSearch. I considered CouchDB but ended up discarding it since I didn't think it adds anything new. So, my business problems were not solved.

Copy Review URL
AM
Small-Business
(11-50 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"It's simple yet a very powerful noSQL database"

What do you like best?

I like couchdb because it is light weight and easy to deploy. The web UI also makes it quick to test map reduce functions against your data. Because couchdb is restful integrating it with web apps is very easy. Replicating couchdb is also very easy which is nice.

What do you dislike?

I would like couchdb to have a better documentation on tuning it for high connection usage. Also replication is nice for a flat model but it would be nice to see some way of seeing easily if replication is delayed.

Recommendations to others considering the product:

There are a lot of good books on couchdb that are on amazon. Sometimes the documentation on the web is a little disconnected.

What problems are you solving with the product? What benefits have you realized?

I am solving issues of storing unstructured data that I need to add to dynamically but may not know in what way.

Copy Review URL
UR
Enterprise
(10,001+ employees)
Validated Reviewer
Review Source
Copy Review URL

"Very easy to implement into you mobile app development!"

What do you like best?

I really like CouchDB for my app development as it is very simple to use and integrity into mobile apps without much initial required. It is a perfect fit for small projects such as mobile app as they are often simple and do not require too much complex queries. In addition, CounchBD is beginner friendly and much less complicated to use that other products out there. It is also stable.

What do you dislike?

If you are working with very large databases and have to use very complex queries or large volume of queries, CouchDB might not be a good choice to use.

Recommendations to others considering the product:

I would definitely recommend CouchDB to new users who are just into mobile app development and want to implement databases into their app with super fast and simple data queries.

What problems are you solving with the product? What benefits have you realized?

Try to implement databases into mobile development apps and ensure scalability across multiple devices with different specs.

Copy Review URL
Director of Software Development
Internet
Small-Business
(11-50 employees)
Validated Reviewer
Review Source
Copy Review URL

"Migrate from SQL Server to CouchDB"

What do you like best?

CouchDB is the simplest database I've ever worked with and one of the most powerful.

It uses HTTP verbs for interact with the database which is very intuitive and clear.

The query mechanism is very different from RDBMS and has learning curve but once you get the hang of it it's really amazing what you can accomplish with it.

What do you dislike?

The admin interface is pretty young and has limitations such as it hard to search, at least at the beginning.

Recommendations to others considering the product:

Read the definitive guide before implement your project.

What problems are you solving with the product? What benefits have you realized?

I was in charge of developing a web-based application and as usual requirements changed. The fact I didn't had to explicitly define a schema ahead of time really help move really fast.

Copy Review URL
Senior Engineer
Hospital & Health Care
Enterprise
(10,001+ employees)
Validated Reviewer
Review Source
Copy Review URL

"Migrated from MySql to NoSql using Couchdb and futon"

What do you like best?

The simple structure of the data and the ability to get data directly using ajax if needed directly from a simpler web application

What do you dislike?

less smooth when using visual studio, currently i am using a package called CouchPotato for ODM but the MSSQL is much easier to use when using native C# and not ASP.net

maybe I am not aware of a more native ODM

Recommendations to others considering the product:

Better integration with Visual studio , and maybe some videos explaining the basic idea of NoSql- it tool me a while to get the hang of it

What problems are you solving with the product? What benefits have you realized?

building HR system that present the in organization network using surveys collected using web application built in C#/ASP.net

Copy Review URL
Software Engineer Intern
Marketing and Advertising
Validated Reviewer
Review Source
Copy Review URL

"Used CouchDB platform for one of the Mobile App project"

What do you like best?

Firstly, CouchDB is very easy to learn and implement. It has rich api's and is well documented, easy to follow manual and installation guide with clear examples.

I have used CouchDB java clients Ektorp and CouchDB4J for implementation and is very easy to implement. What I really liked about CouchDB was the Futon interface, it gives live map of the NoSQL database, it is easy to track the Collection objects, modify them on the fly and also gives quick view of the entire schema

What do you dislike?

CouchDB is really if the requirement is to build a light weight database structure, keep it simple and performance is priority, but then again this holds good for small scale requirements. Unlike MongoDB which I feel is much more robust than CouchDB, provides various options for implementation, there are options for replication, sharding, monitoring and has provides feature rich interfaces which CouchDB lacks.

Recommendations to others considering the product:

Use CochDB, if your requirement is to build an application with light weight database ,performance needs and quick implementation.

What problems are you solving with the product? What benefits have you realized?

I have used CouchDB for a small Mobile application, which required storing dynamic content of varied length.

Benefits realized after using this product

1. Easy maintenance

2 Performance

3. Scalablity

Copy Review URL
Associate Staff Developer
Computer Software
Validated Reviewer
Review Source
Copy Review URL

"We developed our first version of our product PocketLabs with it. We used CouchBase with is a fork."

What do you like best?

Master to master replication

Automatic resharding

Scalability in general

Couchbase admin.

Read speed.

Simple to use and administrate.

Multi version concurrency control

What do you dislike?

Eventual consistency, Limits the type of projects you can use it for. Great for mostly read apps. I would not use it for apps that require frequent updates.

Limited querying capabilities. Not multi key.

Recommendations to others considering the product:

The problem I see in general is with the word no-sql.

CouchDb is no-sql but so is redis and mongoDb and they are very different.

No-sql offers specific solutions for specific problems. This is different from the SQL world where you solve everything with SQL. People that live with sql typically install their database even before they receive specs.

That being said CouchDB is designed to serve information with speed and redundancy in a scenario where you are mostly reading data. You will also have a limited freedom regarding querying (even if you script). It would be a fantastic DB for a catalog but be wary if you need need heavy updates as it takes some time for data to propagate, or if you need to run reports that have not yet been defined.

What problems are you solving with the product? What benefits have you realized?

Its fast and simple to develop. Great for startups and prototypes.

You can use it as a very large cache.

You can use it as a versioning system for documents.

By design its awesome for syncing data between apps.

Copy Review URL
Senior .NET Developer
Marketing and Advertising
Mid-Market
(51-200 employees)
Validated Reviewer
Review Source
Copy Review URL

"Overall a pretty savvy DBMS"

What do you like best?

What I liked best about starting off using couchdb was replication. This fits well with a client server application that needs to sync to the cloud. Also, I liked the restful API that is available and the out of the box authenticat ion is great.

What do you dislike?

I dislike having to create views and remember the specific key value pair that the view provides. Also, it would be great to support some type of tradional join as you get in a sql db. My code is more verbose bc of this and I'm not able to do the heavy lifting server side.

Recommendations to others considering the product:

Do not use couch if using very relational data as your business logic will become a nightmare and unmaintainable. You might be able to understand Mongo better if coming from the RDBMS world, but overall there is great support for this dbms (i.e. documentation is excellent and administrative tools are pretty good)

What problems are you solving with the product? What benefits have you realized?

As mentioned, I am benefiting from client-server replication and user authentication. Also, I wanted an abstraction layer between my db and my application and I get that with the restful api. Bc of the restful api, I was able to pick it up quickly.

Copy Review URL
AC
Small-Business
(11-50 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"Using CouchDB nearly daily for last 5 years."

What do you like best?

Stable and smart replication, especially in pair with PouchDB, and full REST API.

Formal documentation is full and well structured.

What do you dislike?

Built-in Javascript query server is slooooow. Overall CRUD performance is also quiet weak.

Product site looks bit outdated and messy and is not focused on users‘ needs.

New 2.0 preview is at least not faster then previous version.

Recommendations to others considering the product:

Look at in-memory implementations + node.js or other webserver in front.

What problems are you solving with the product? What benefits have you realized?

We are building distributed systems operating in unfriendly environment – carrier and power loss, unstable transmission rates and so on. CouchDB helps a lot.

Also we use couchapp features a little and build small static sites using CouchDB.

Copy Review URL
Co-founder
Information Technology and Services
Small-Business
(2-10 employees)
Validated Reviewer
Verified Current User
Review Source
Copy Review URL

"User and admin of CouchDB and BigCouch"

What do you like best?

CouchDB views are very fast and the REST interface is simple and easy to integrate with.

What do you dislike?

View corruption is a real problem with larger views and rebuilding them can take significant time.

Recommendations to others considering the product:

I recommend CouchDB for smaller datasets. We tried using it with our server monitoring results but view corruption made it impossible to maintain. You're also likely to run out of disk space since large data sets are stored on-disk very inefficiently. For smaller data, it's an excellent choice.

What problems are you solving with the product? What benefits have you realized?

Schema-less data retention and fast pre-built views are what drew us to CouchDB.