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.
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
- Leave a Comment |
- Mark review as helpful
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.
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.
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.
showing 21 - 30