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 considered part of a new generation of 'NoSQL' databases that don't require fixed table schemas and is challenging the dominance of traditional relational databases (including the popular MySQL). Cloudant, Great Managed NoSQL at Significant CostMy organization had a need to store a moderate amount data for an insurance client. Our data storage solution needed to be flexible enough to support our BI solution as well as any in-house web apps the client might develop to their claims department. It also needed to be limited in the additional DBA overhead required to operate it. That is why my organization chose IBM Cloudant because it was able to meet the BI need, the needs of the web stack developers, and the DBA were kept happy too.,We had a small data mart project that required the storage of some rather highly connected data that also had a relatively small footprint. This made IBM Cloudant an obvious choice because we could store the data in a data structure that met our project need al while using a platform that our web development team understood and was comfortable with. We had a bunch of geospatial data that we needed for analysis. Having GeoJSON being natively supported by Cloudant made it an easy choice. Cloudant was cloud-based and didn't require a DBA support it, this allowed the project to move ahead without pushback from the infrastructure team.,It was only after we went with the cloud-based solution that IBM rolled out an on-premise version. We found that a 3rd-party ODBC driver was required for a few applications that needed to pull data out of Cloudant. The sales process was difficult because the salesperson we used was not as versed on Cloudant as I had hoped.,6,The simple fact that we could spin up a Cloudant instance quickly in the cloud without the need to procure hardware and software allowed the project to start sooner than what is typical. Being fully-managed the IT department was able to keep staffing levels the same and not have to send a bunch of people off to training.,Cloudant allowed us to implement a project faster due to it being fully managed and basically a plug-and-play type data store. Being fully managed meant that we spent a fair bit of time on the phone yelling at IBM Support because they didn't know jack about how to solve the issues we ran into/ Overall Cloudant worked for us because the project timeline and budget allowed for more money to be spent on services rather than hardware (OpEx vs CapEx).,MongoDB and Microsoft SQL Server,No,Product Features Prior Experience with the Product Vendor Reputation Existing Relationship with the Vendor,The one thing we would change is by having more technologies to evaluate. The NoSQL market is flush right now with options, but during the build-up to our project, Cloudant seemed to be the one solution that management could be comfortable with.Short and sweetIt's our primary store for user-generated and transactional data.,Scalability. Fast ingest rates. Fault tolerance. Great for building data pipelines (_changes streams).,I'd like to have an option of specifying a view (or multiple views) for the _changes stream that will be used to process the documents returned alongside changes (with include_docs=true) Database-specific monitoring dashboards would be great. Ability to tweak job priorities (on dedicated clusters).,10,It allows us to store fairly complex documents atomically and define map-reduce aggregations at a later time without going through the pain of schema migration.,8,Definitely so, moving to the fully-managed service allowed us to focus on developing our core platform without having the engineers distracted by database maintenance. Also, Cloudant team's response times are great, which means that that in the rare occasions where we suffer from a failure, recovery times are short.,Elasticsearch and CouchDB,Elasticsearch, CouchDB,Yes,Price Product Features Product Usability Product Reputation Vendor Reputation,We wouldn't change a thing.,9,No,Building data pipelines. Map-reduce. Search.,Monitoring the activity of each database (as opposed to the whole cluster). Accessing shared databases via the dashboard (some features need improving). Tracking the progress of indexing jobs could be easier, some kind of a progress bar would be useful.,8If it fits your need, you'll never have problems or complaints.We currently use Cloudant to store call detail records for our faxing platform. The platform itself stores these records, but the API is not easy to query. So we take every single record and store them in Cloudant. This includes not only the basic sender and receiver information, but also per minute costs for each fax. This allows us to easily present incoming and outgoing faxes to our users via our client portal. It's also great for the billing department in that they can quickly query the recordings for profit and cost analysis.,It stores a very large amount of information very efficiently. Granted, we're just storing call detail records, but we're storing 200K records in 50MB. Querying isn't as fancy as SQL-based databases. But if you know what you need and can get it in a view, it is very fast. I'm querying both date and phone number without any issues. The UI for managing your databases is top notch. We can build views and searches, and query those with issues. This lets us refine and perfect our JS functions and queries very easily.,Search Queries. They work when they work, but some of the documentation is a tad confusing and the bookmark system of pagination is not great.,9,I already knew about Cloudant before choosing it as our solution. I've always had issues with MySQL and others choking at 10K records, and I had no desire to be a DBA. So after looking over a few options, I felt that Cloudant fit our needs best. It's mix of JSON documents and view system fit perfectly the kind of data I needed to store and query.,10,Yes. The impact is that I'm not spending all day every day looking at database servers, and adding and scaling database servers. I never worry about system performance, or tuning, or scaling resources. That means a lot to me when I'm not just doing fax data storage, but also developing a client portal, and troubleshooting phone systems. I have enough to manage, and it's nice not to have to manage this.,MongoDB, Redis, Cassandra and Riak,InfluxDB, LogicMonitor, MySQL,5,1,Call Detail Record Storage Billing Data Storage Faxing Data,I use complex keys with Cloudant views to query not just CDRs by phone, but by date as well. Range queries on views are great!,I would really like to integrate it with InfluxDB and some monitoring software to create a more performant and efficient monitoring platform. Many software out there like to use ElasticSearch, but ElasticSearch is very costly resource-wise.,No,Price Product Features Product Usability,I would not change a thing. The core problem arose when querying for fax data would bring down our client portal on every single load. The fax server just refused to cooperate. Then and now, there are few products that would do what I need for little upfront costs. Most would require that I self-host, which I do not have time for.,Implemented in-house,No,Change management was minimal,Getting queries working correctly. I was new to how views worked so I went down the full text path only to find it didn't quite worked out how I thought. Then I realize that phone numbers are just long number and went that route with ranged keys on views.,10,No,8,No,It does what it says on the box. Stores data, retrieves data, queries data with Map/Reduce and full text search.,Full text search can be really tricky to get working correctly. It works, but then you find it's not quite querying the way you expect it.,Yes, but I don't use it,9Scaling our data layer without headachesCloudant allows us to scale our data layer without worrying about the operations side of things to manage such a big cluster. Cloudant is the main database system for our company. It's totally business critical for our company and our many customers rely on its performance on a daily basis to perform their work.,Scale your data layer without issues. Great support team. Great documentation.,The Dashboard application is really slow and very hard to use to do any hard work. No playground environment to test some very large map/reduce queries (and therefore any changes in the design have to reindex the whole DB). Besides being slow, the Dashboard is actually less usable.,9,Because of replication capabilities, our entire system is architected around this. Cloudant brings the CouchDB interface, but scales it to a new level. Earlier, we used the Heroku provided multi-tenant Cloudant connector, which got discontinued. Now, we have migrated to a dedicated cluster which has brought us the required level of support and scalability.,9,Yes, it allows us not to worry about the data layer, which is really why we choose for the multi-tenant solution, despite its quite aggressive price-tag (for startup standards).,,Heroku,, Mixpanel, Logentries, New Relic APM, Atlassian Confluence, JIRA Software, Travis CI,10,,Storing the business transactions performed offline Storing usage metrics Storing content configuration documents Reporting on all of the above.,Distributed replications Waiting on some really cool use cases for DashDB.,More reporting with DashDB. More ad-hoc reporting. Much more storage of data. Automatic archiving of the database (e.g. like Amazon Glacier) would be a killer feature.,No,Product Features Prior Experience with the Product Positive Sales Experience with the Vendor,No, we are happy with the service. The selection process was very simple since we were already using Cloudant through the Heroku connector (which was unexpectedly terminated, to be honest).,Implemented in-house,Change management was a minor issue with the implementation,Designing the documents to be scalable. (Manually) sharding of the document on many databases was a key design decision for us (we shard per "day"), so that we can more replicate back and forth. Designing performing views for large amounts of document (ad-hoc reporting) is very tricky.,9,Yes,9,Yes,Our account contact director Chris Snow is helping us to develop some extensions to Cloudant Sync during his free time.,Editing the docs in the dashboard Writing ad-hoc queries Permissions management,The Dashboard is slow and takes time to load many databases. Writing a new map/reduce view indexes the entire DB for every change. In Couchbase, you have a feature to create a view for a subset of the data, this is very convenient.,9
IBM Cloudant
91 Ratings
Score 7.2 out of 101
<a href='' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>TRScore

IBM Cloudant Reviews

IBM Cloudant
91 Ratings
<a href='' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 7.2 out of 101

Do you work for this company?

Show Filters 
Hide Filters 
Showing 4 of 91 IBM Cloudant ratings and reviews.
Clear all filters
Overall Rating
Reviewer's Company Size
Last Updated
By Topic
Job Type

Reviews (1-4 of 4)

Companies can't remove reviews or game the system. Here's why.

Feature Scorecard Summary

Performance (2)
Availability (2)
Concurrency (2)
Security (2)
Scalability (2)
Data model flexibility (2)
Deployment model flexibility (2)

About IBM Cloudant

IBM Cloudant is a distributed database that is optimized for handling heavy workloads that are typical of large, fast-growing web and mobile apps. Available as an SLA-backed, fully managed IBM Cloud service, Cloudant elastically scales throughput and storage independently. Cloudant is also available as a downloadable on-premises installation, and its API and powerful replication protocol are compatible with an open source ecosystem that includes CouchDB, PouchDB and libraries for the most popular web and mobile development stacks.

IBM Cloudant Features

NoSQL Databases Features
Has featurePerformance
Has featureAvailability
Has featureConcurrency
Has featureSecurity
Has featureScalability
Has featureData model flexibility
Has featureDeployment model flexibility

IBM Cloudant Video

IBM Cloudant Competitors


Has featureFree Trial Available?Yes
Has featureFree or Freemium Version Available?Yes
Has featurePremium Consulting/Integration Services Available?Yes
Entry-level set up fee?No

IBM Cloudant Technical Details

Deployment Types:SaaS
Operating Systems: Unspecified
Mobile Application:No
Supported Languages: English, French, German, Italian, Japanese, Korean, Portuguese/Brazil, Spanish, Chinese Simplified, Chinese Traditional