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.
Database of the future: Cluster Of Unreliable Commodity Hardware
What do you like best about the product?
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.
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 about the product?
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 is the product solving and how is that benefiting you?
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.
- Leave a Comment |
- Mark review as helpful
Easy To Use NoSQL Database
What do you like best about the product?
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.
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 about the product?
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.
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.
What problems is the product solving and how is that benefiting you?
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.
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.
the world of database with Couch DB
What do you like best about the product?
I like the ease of use, also can work in a comfortable manner with respect to transactions and data handling. I like mainly because I am fond of NoSQL database and database managers it seems pretty friendly and easy to use
What do you dislike about the product?
very few things I do not like, though, I have more experience in SQL BDD and often prefer to use the sql because the handling of data that are related one is more comfortable in sql. and nosql are not the best option in these cases.
What problems is the product solving and how is that benefiting you?
I resolved to deploy to multiple database designs due to information processing and management of data required
Recommendations to others considering the product:
nothing, i think its ok. i like this aplication
A flexable framework for map-reduce based REST APIs.
What do you like best about the product?
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.
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 about the product?
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 is the product solving and how is that benefiting you?
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)
Very easy to implement into you mobile app development!
What do you like best about the product?
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 about the product?
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.
What problems is the product solving and how is that benefiting you?
Try to implement databases into mobile development apps and ensure scalability across multiple devices with different specs.
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.
Simple but powerful backend service
What do you like best about the product?
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.
You can also do offline available apps using PouchDB in the browser and CouchDB in the server.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
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.
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
Migrated from MySql to NoSql using Couchdb and futon
What do you like best about the product?
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 about the product?
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
maybe I am not aware of a more native ODM
What problems is the product solving and how is that benefiting you?
building HR system that present the in organization network using surveys collected using web application built in C#/ASP.net
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
Fast read speed - ideal for write once read many data
What do you like best about the product?
Super fast read speed and flexibility of storing data as JSON strings.
What do you dislike about the product?
Not a dislike, but this database isn't suitable for storing data such as images. It's meant for fast reading smaller chunks of data quickly. Also write speeds are fast but not blazing. It's not a fault, but something you need to consider depending on your application
What problems is the product solving and how is that benefiting you?
Storing data such as user profiles, OAuth tokens etc. Written once (or not so often) and read many times.
Recommendations to others considering the product:
As with any database - choose wisely and think about exactly what your requirements are
Offline first!
What do you like best about the product?
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.
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 about the product?
I don't think there is anything I dislike
What problems is the product solving and how is that benefiting you?
Using websites that downloads lots of data or makes lots of requests, you can load everything very quickly on slow 3g connections.
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.
Couch!
What do you like best about the product?
I love what couch offers like every other SoSQL DB out there; schemaless data.
What do you dislike about the product?
They could make a better security solution out of the box.
What problems is the product solving and how is that benefiting you?
Service based databases.
showing 21 - 30