Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Slow start but on the right track
What do you like best about the product?
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 about the product?
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.
What problems is the product solving and how is that benefiting you?
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.
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.
- Leave a Comment |
- Mark review as helpful
Not distributed yet solid document oriented DBMS
What do you like best about the product?
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 about the product?
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).
What problems is the product solving and how is that benefiting you?
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.
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).
Development Stagnation
What do you like best about the product?
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 about the product?
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.
What problems is the product solving and how is that benefiting you?
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.
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.
Best noSQL Database for Beginners : )
What do you like best about the product?
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 about the product?
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.
What problems is the product solving and how is that benefiting you?
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.
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.
Using CouchDB nearly daily for last 5 years.
What do you like best about the product?
Stable and smart replication, especially in pair with PouchDB, and full REST API.
Formal documentation is full and well structured.
Formal documentation is full and well structured.
What do you dislike about the product?
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.
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.
What problems is the product solving and how is that benefiting you?
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.
Also we use couchapp features a little and build small static sites using CouchDB.
Recommendations to others considering the product:
Look at in-memory implementations + node.js or other webserver in front.
Great - As long as it fits your use case
What do you like best about the product?
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
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 about the product?
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
What problems is the product solving and how is that benefiting you?
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.
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
It's simple yet a very powerful noSQL database
What do you like best about the product?
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 about the product?
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.
What problems is the product solving and how is that benefiting you?
I am solving issues of storing unstructured data that I need to add to dynamically but may not know in what way.
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.
Creating for example, a simple calendar anotation app in Javascript with this is super easy
What do you like best about the product?
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.
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 about the product?
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 is the product solving and how is that benefiting you?
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.
A Database for the Web
What do you like best about the product?
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 about the product?
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?
What problems is the product solving and how is that benefiting you?
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.
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.
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.
Not even close to MongoDB
What do you like best about the product?
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 about the product?
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.
The community is very small, I had trouble finding answers to basic questions I had during the time I was trying it.
What problems is the product solving and how is that benefiting you?
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.
Recommendations to others considering the product:
If you find it useful, good for you. I'd prefer MongoDB and ElasticSearch.
showing 31 - 40