
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.
Migrate from SQL Server to CouchDB
What do you like best about the product?
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.
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 about the product?
The admin interface is pretty young and has limitations such as it hard to search, at least at the beginning.
What problems is the product solving and how is that benefiting you?
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.
Recommendations to others considering the product:
Read the definitive guide before implement your project.
- Leave a Comment |
- Mark review as helpful
Thinking Documentally
What do you like best about the product?
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).
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 about the product?
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.
What problems is the product solving and how is that benefiting you?
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.
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".
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".
As CTO, I selected CouchDB from other databases to power our SaaS product offering.
What do you like best about the product?
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 about the product?
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.
What problems is the product solving and how is that benefiting you?
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.
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.
CouchDB
What do you like best about the product?
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 about the product?
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 is the product solving and how is that benefiting you?
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.
Using couchDB in my hobby project
What do you like best about the product?
Replication mechanism and update streaming capabilities, which proven very useful on front end development side by using PouchDB
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
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.
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.
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.
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 about the product?
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 about the product?
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 is the product solving and how is that benefiting you?
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.
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.
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.
showing 31 - 40