Apache CouchDB is an HTTP + JSON document database with Map Reduce views and bi-directional replication. The Couch Replication Protocol is implemented in a variety of projects and products that span computing environments from globally distributed server-clusters, over mobile phones to web browsers.
N/A
IBM Cloudant
Score 7.4 out of 10
N/A
Cloudant is an open source non-relational, distributed database service that requires zero-configuration. It's based on the Apache-backed CouchDB project and the creator of the open source BigCouch project.
Cloudant's service provides integrated data management, search, and analytics engine designed for web applications. Cloudant scales your database on the CouchDB framework and provides hosting, administrative tools, analytics and commercial support for CouchDB and BigCouch.
Cloudant is often…
$1
per month per GB of storage above the included 20 GB
Pricing
Apache CouchDB
IBM Cloudant
Editions & Modules
No answers on this topic
Standard
$1
per month per GB of storage above the included 20 GB
Standard
$75
per month 100 reads/second ; 50 writes/second ; 5 global queries/second
Lite
Free
20 reads/second ; 10 writes/second ; 5 global queries / second ; 1 GB of storage capacity
The feature-set, including security, is very comparable. Overall, IBM's services added to the product are mature and stable, although product support and engineers could be a little better. Global availability is improving, and Disaster Recover Capabilities are great. Overall, …
Cloudant is a hosted solution so it works better for me. Also, it includes a better authentication layer than CouchDB. As for Couchbase, it has membase but the hosted options are much more expensive. In the SQL world, I tried several sync solutions but the configuration and …
Cloudant stacks up very well especially since it can perform multiple functions - primarily a noSQL schema-less data base but when integrated with an MDM solution (master data management) it can also do caching services efficiently and can also be used as a graph data base. …
It's easier to use than Dynamo, more open than Firebase, and has better documentation that CouchDB... it might not be fair to compare Modulus, Modulus obviously suffers from some scalability issues and might not be in the same class... but its a hosted DB service we had some …
All other NoSQL document-centric DB must be installed on premise on in the cloud as complicated clusters. The "as a service" formula and the open source origin were the same reasons for Cloudant choice, freeing us of all system and administration tasks!
Cloudant is a database as a service with a strong support team. The feature set is comparable to other solutions but not all are managed services, or have easy scalability, or can demonstrate production level reliability and performance.
We used to host CouchDB ourselves, but moved to BigCouch at first for scalability and then to Cloudant to reduce the maintenance overheads. We use Elasticsearch alongside Cloudant these days, since _changes streams make it easy to feed data from Cloudant into Elasticsearch. …
Cloudant blows all of the other competitors out of the water. The robust UI, the scalability, the management console, these are all reasons why Cloudant is a superior product to any of these "competitors". Cloudant is head and shoulders above the rest. It was a pleasure to …
Cloudant extends features of CouchDB, but you don't have to host it for yourself. IBM does this for you. Also Cloudant is free if you are under $50 per month. And there is integration with other IBM products, like dashDB (for analytics).Cloudant has CouchApps and it's a feature …
Great for REST API development, if you want a small, fast server that will send and receive JSON structures, CouchDB is hard to beat. Not great for enterprise-level relational database querying (no kidding). While by definition, document-oriented databases are not relational, porting or migrating from relational, and using CouchDB as a backend is probably not a wise move as it's reliable, but It may not always be highly available.
Our organization found Cloudant most suitable if One, a fixed pricing structure would make the most sense, for example in a situation where the project Cloudant is being used in makes its revenue in procurement or fixed retainer — thus the predictability of costs is paramount; Two, where you need to frequently edit the data and/or share access to the query engine to non-engineers — this is where the GUI shines.
It can replicate and sync with web browsers via PouchDB. This lets you keep a synced copy of your database on the client-side, which offers much faster data access than continuous HTTP requests would allow, and enables offline usage.
Simple Map/Reduce support. The M/R system lets you process terabytes of documents in parallel, save the results, and only need to reprocess documents that have changed on subsequent updates. While not as powerful as Hadoop, it is an easy to use query system that's hard to screw up.
Sharding and Clustering support. As of CouchDB 2.0, it supports clustering and sharding of documents between instances without needing a load balancer to determine where requests should go.
Master to Master replication lets you clone, continuously backup, and listen for changes through the replication protocol, even over unreliable WAN links.
Because our current solution S3 is working great and CouchDB was a nightmare. The worst is that at first, it seemed fine until we filled it with tons of data and then started to create views and actually delete.
the flexibility of NoSQL allow us to modify and upgrade our apps very fast and in a convenient way. Having the solution hosted by IBM is also giving us the chance to focus on features and the improvement of our apps. It's one thing less to be worried about
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
It's mostly just a straight forward API to a data store. I knock one off for the full text search thing, but I don't need it much anyways. Also, the dashboard UI they give is pretty nice to use. It provides syntax-highlighting for writing views and queries are easy to test. I wish other DBs had a UI like this.
it is a highly available solution in the IBM cloud portfolio and hence we have never had any issues with the data base being available - we also do continuous replication to be on the safer side just in case some thing goes awry. We also perform twice a year disaster recovery tests.
very easy to get started and is very developer friendly given that it uses couchDB analytics. It is a cloud based solution and hence there is no hardware investment in a server and staging the server to get started and the associated delays/bureaucracy involved to get started. Good documentation is also available.
online resources are good enough to understand but there is nothing like testing. In our case, we discovered some not documented behavior that we take in count now. Also, the experience in NodeJs is critical. Also, take in count that most of the "good practices" with cloudant are not in online courses but in blogs and pages from independent developers
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
The feature-set, including security, is very comparable. Overall, IBM's services added to the product are mature and stable, although product support and engineers could be a little better. Global availability is improving, and Disaster Recover Capabilities are great. Overall, it's very comparable to MongoDB as a DBaaS offer, available globally and with great documentation.
The service scales incredibly well. As you would expect from CloudDB and IBM combination. The only reason I wouldn't score it a 10 is the fact that document trees can get nested and nested very quickly if you are attempting to do very complex datasets. Which makes your code that much more complex to deal. Its very possible we could find a solution to this problem with better database planning to begin with, but one of the reasons we chose a service over a self-hosted solution was so we could set it up quick and forget about it. So we weren't going to dedicate a team to architecture optimization.