CouchDB: NOSQL is faster than SQL
Victor Pease Solano | TrustRadius Reviewer
Updated March 22, 2016

CouchDB: NOSQL is faster than SQL

Score 7 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with CouchDB

CouchDB is corporate wide solution used for:

  • route planning for sales force
  • a central farm and mobile devices replicating the content partitioned per user
  • Syncrhonization
  • Fast http interface
  • Dead easy scalability
  • Authentication
  • Security (you must compile your own https capable instance)
  • Project mango is not built in yet
Effective:
  • synchronisation is dead simple and powerful
  • map/view is ultrafast for most common queries
  • scalability is super simple
Ineffective:
  • server side operations are limited to queries
  • bulk updates are all client-side
  • data validation is completely client side
  • document level security not possible

  • better hardware utilization
  • bandwidth isolation because replication allows local data
  • couchdb is free
  • Cloudant
CouchbaseDB is essentially faster with more options but of course with a cost. Cloudant is the hosted option with a better security schema.
couchdb is basic, there are options like mango query and https that must be included as built in but [are] not yet.
CouchDB is best suited for:
  • db front end for mobile applications
  • apps with no intensive data entry requirements
It is not suited for:
  • bulk operations
  • apps with server side requirements
  • complex queries

CouchDB Implementation

it support is minimal also hw requirements. Also for development, we can have databases replicated everywhere and the replication is automagical. once you set up the security and the rules for replication, you are ready to go. The absence of a model let you build your app the way you want it
Yes - design: this is the most critical one,because we need to define what is couchdb to be used according to their capabilities.
implementation: here we define how to perform all the operations related to the db like data import, export , replication and notifications.
testing: during all stages we had to test all the features on couchdb and this is pretty easy because we can have a test server with the replication feature
Change management was a big part of the implementation and was well-handled - the main one: you have to change the way of doing things inside the it department because they are used to relational tools. Sometimes simple admin tasks are not trusted by IT and when dealing with databases is more critical because they expect data models and access and indexes. Its difficult to understand that some simple tools can do a good job
  • Make IT to understand they don't need a tool to "query" data on CouchDB. All data is managed by the app
  • Disk management is the most critical part but that can be managed with a replication strategy
  • Filtered replication debug was an issue at the very beginning
  • Cors was an issue for some apps

Using CouchDB

Couchdb is very simple to use and the features are also reduced but well implemented. In order to use it the way its designed, the ui is adequate and easy. Of course, there are some other task that can't be performed through the admin ui but the minimalistic design allows you to use external libraries to develop custom scripts
ProsCons
Like to use
Relatively simple
Easy to use
Consistent
Quick to learn
Convenient
Feel confident using
None
  • replication control
  • logging
  • data browsing
  • user management
  • db permissions
  • server configuration