Skip to main content
TrustRadius
IBM Cloudant

IBM Cloudant

Overview

What is IBM Cloudant?

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…

Read more
Recent Reviews

Win-Win for IBM Cloud

9 out of 10
April 18, 2021
Incentivized
We were using IBM Cloudant as our cloud storage platform for a project where we were collecting real-time environmental data. Later, we …
Continue reading
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Popular Features

View all 7 features
  • Concurrency (21)
    9.9
    99%
  • Performance (21)
    9.8
    98%
  • Security (21)
    9.8
    98%
  • Availability (21)
    8.1
    81%

Reviewer Pros & Cons

View all pros & cons
Return to navigation

Pricing

View all pricing

Standard

$1

Cloud
per month per GB of storage above the included 20 GB

Standard

$75

Cloud
per month 100 reads/second ; 50 writes/second ; 5 global queries/second

Lite

Free

Cloud
20 reads/second ; 10 writes/second ; 5 global queries / second ; 1 GB of storage capacity

Entry-level set up fee?

  • No setup fee
For the latest information on pricing, visithttps://www.ibm.com/cloud/cloudant/pric…

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services
Return to navigation

Features

NoSQL Databases

NoSQL databases are designed to be used across large distrusted systems. They are notably much more scalable and much faster and handling very large data loads than traditional relational databases.

9.4
Avg 8.8
Return to navigation

Product Details

What is 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 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

  • Supported: Performance
  • Supported: Availability
  • Supported: Concurrency
  • Supported: Security
  • Supported: Scalability
  • Supported: Data model flexibility
  • Supported: Deployment model flexibility

IBM Cloudant Video

database management with Cloudant

IBM Cloudant Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo
Supported LanguagesEnglish, French, German, Italian, Japanese, Korean, Portuguese/Brazil, Spanish, Chinese Simplified, Chinese Traditional

Frequently Asked Questions

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).

Amazon DynamoDB, MongoDB, and Couchbase Server are common alternatives for IBM Cloudant.

Reviewers rate Concurrency and Data model flexibility highest, with a score of 9.9.

The most common users of IBM Cloudant are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(123)

Attribute Ratings

Reviews

(26-45 of 45)
Companies can't remove reviews or game the system. Here's why
February 14, 2019

Cloudant Rocks!

Deepak Kaul | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
We are a cloud based solution provider and our products are deployed on the IBM cloud and we used IBM Cloudant as a database (persistent) storage. We use it across the board to store anything that needs persistent storage, from text to images and document attachments as well.
  • Strong query interface, IBM Cloudant provides a very robust and flexible query interface allowing us to write simple as well as complex queries.
  • Performance, for the most part we have been happy with the performance of the Cloudant database
  • Simple and straight forward. Ability to roll out the instances quickly and with a simple interface has been important for us.
  • The shared instances of Cloudant can have better isolation mechanisms. We have had instances where the performance of our instance was negatively impacted because other instances on the same node were taking more resources.
  • Better conflict resolution. Cloudant should take away some complexity of conflict resolution from the application. Today the application has to manage most of that complexity.
Ideal for unstructured data and where data elements are self-contained for the most part. For relational-type data, Cloudant presents some challenges.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Cloudant DB is utilized in our organization in cooperation with IBM IOT platform to monitor supply chain for our disaster relief solution. Cloudant is also used to collect user reports and is used as a data dump for Watson learning to use for improving and also used for analytics.
  • It’s fast to setup and go
  • Good support for NodeJS
  • Integrates super easy with microservices
  • Documentation
  • Support for SQL
IBM is suited for development POCs as it's extremely easy to get it up and running. Less suited to handle sequential data such as login info and such
Naresh Jasotani | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
IBM Cloudant DB is currently being used at 2 of our customers' places. The implementation is more confined to a couple of departments / function areas of the organization, but surely they are looking to adopt it on a bigger scale. The DB hosts not only their custom-built vendor onboarding applications, but also supports a portion of their intranet portal to manage a lot of employee related non-HR information like events, knowledge bases, quizzes application etc. They are looking to migrate data and applications from other databases to IBM Cloudant DB.
  • For us, performance and scalability is the key, and Cloudant DB backed by CouchDB is scalable and performant.
  • IBM Cloudant dB is very easy to provision for sandbox, development, QA as well as production.
  • Support for Java for CouchDB app server analytics enables a greater control for over developers.
  • Schema free oriented very easy to program and build applications on it.
  • We love it!!
  • Lacks in-memory capabilities
  • Limited support for programming languages like Python, R, Perl
  • No XML support
  • No SQL support :(
Applications where concurrency and durability are more important as compared to in-memory functionalities, IBM Cloudant DB is recommended. For us, the key question is to have Java and C# programming support on the database, for building applications, however if Python, Perl or R support is required, then IBM Cloudant DB may not be an intelligent choice.
Score 6 out of 10
Vetted Review
Verified User
Incentivized
My 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.
The solution to store claims information worked for us, but the enterprise NoSQL market has expanded so much that we might not [have] used Cloudant had an alternative been available. Make sure you ask about ACID compliance and about what the difference between NoSQL and SQL databases are to that the IT managers understand why they are buying and how that differs from data solutions they've bought in the past.
Wes Wilson | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We use Cloudant as our online cloud database solution for our mobile health app. Our solution had to work cross platform with Android and iOS and allow syncing to local databases for offline use. Cloudant allowed for easy integration into our stack with very little setup. By not having to worry about converting between database architectures we were able to focus our development time on building features into our app.
  • Easy Setup
  • Simple API's
  • Great Documentation
  • Open Standards / Works with CouchDB and mobile PouchDB
  • Built in live listeners to watch for data changes would be a nice addition
If you are using MEAN stack and require a 3rd party cloud database it really is up there with firebase. Firebase has a couple extra features attached to its non-sql DB, and if you need those particular features then that might be a best choice. But if you don't, cloudant is far more open and most scripts and tools that work with CloudDB will work with cloudant. Firebase is far more proprietary which gives it a steeper learning curve also. Another thing to consider is how many different types of software will interact with your DB. If you are just building a web app and only one application needs the data then arguably the pros and cons against any hosted solution like Amazon Dynamo, Modulus (MongoDB), or Firebase is going to be minimal and subjective. But if you are using lots of different technologies and many different devices there is a major advantage to going with a less proprietary solution. You get all the compatibility of CouchDB but the reliability of having IBM behind your DBaaS.
Romualdo Gobbo | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
ResellerIncentivized
Cloudant NoSQL DB based on JSON is the foundation of our SaaS software solutions proposed in SaaS when the aim is document centric. Our last implementation was the Tracking & Tracing service offered in SaaS via IBM Bluemix, where all actors authorized can post their JSON docs in a very easy way without the constraint of one specific schema, and can retrieve or update the documents with RESTFul APIs that trace the "status" of each document.

Cloudant's flexibility helps in adding the data "views" even after the document creation, and this opens a new way to design documents, freeing them from relational constraints.

The replication function allows you to have in real time the same copy of docs updated in other Cloudant databases - even geographically distributed. Some interesting embedded features such as the Geo Query, based on the standard Geo-JSON specification, open the way to the development of location awareness solutions without the hassles to manage the geometry of the geo-map searching.
  • Managing different documents in JSON format: every well formed structure of JSON docs are stored without a previous data schema support.
  • Queu reviews: are the power map-reduce functions applying after the documents ingestion.
  • Replication: powerful and easy DevOps function to save, copy or back up the data from one Cloudant DB to another in synchronizing way even between different sites geographically distributed.
  • The automatic creation of Data Warehouse relational DB DashDB for Analytics from NoSQL is one of the [most] invaluable features ever found. The SDP-Schema Discovery Process is really unleashing the power of JSON schema-less into structured relational DB ready for all analytic tools without any programming intervention.
  • The API GEO call based on GeoJSON structure, is one of the features that has been much more awaited in the "location awareness" application now implicit in quite all applications from marketing to logistics. The GEO API is built by the query options making the geo search application integration more easy than ever.
  • To have a sort of LUW - Logical Unit Work when many documents are involved into a single update process. The changing of one document is related to its status information but it must be synchronized with all the other documents involved in the process.
Cloudant is perfect when you have to manage fixed documents, but with different content and an articulated data hierarchy. Furthermore it maintains many document structures in one instance of the DB. Cloudant should be used when the document has a "lazy" life cycle (better if it is only based on its workflow status information) and it is not comparable to an OLTP system where the data is constantly being updated.
Justin Saul | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We use Cloudant as our primary data store for a marketplace solution.
  • Cloudant is flexible and fast. From basic document storage, to aggregate data requests, to creating graph data models, Cloudant was flexible enough to handle it.
  • Cloudant events every record change enabling an easy way to event everything.
  • The Cloudant support team is fantastic.
  • At the time, filtered replication is sub-optimal for large data sets. This will improve over time.
  • The divide (cost & performance) from tenant to dedicated is a bit wide for startups.
Cloudant is fairly robust. If you have changing data structures, loose data structures, logging, event storage, or need mobile syncing, Cloudant is a great fit. If you have very relational data that needs constant ad-hoc analysis, I would stick with traditional setups.
Carlos Eduardo | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We use Cloudant with ACRA to track errors from our different mobile apps. Through Cloudant our company was able to optimize our workflow and make our apps better.
  • Cloudant is cloud. Through Cloudant our company was able to connect all of our services into a single database in a very easy and faster way. This made our maintenance and analysis about our services much easier.
  • Cloudant is elastic. This is very important in business today. We spend only what we really need and have used. Nothing more.
  • Cloudant is very easy. Our company was able to connect Cloudant with all of our services and apps very easily. In a few weeks Cloudant was completely integrated to our services.
  • Our company team is completely integrated with Cloudant. The service is great and any new feature will be welcome.
Cloudant is perfect for XaaS companies. The fit was just perfect for a company like ours, and we have improved our job since then.
August 01, 2016

Short and sweet

Kris Bandurski | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
It'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).
Great when the primary objective is reliable and quick data storage. Not ideal for applications that require running complex, relational queries.
Bryan Redeagle | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
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.
It's great for storing large datasets where you need to access records directly or can sort them into easily parseable lists. It's not good for complex queries. Don't think of it as a complete replacement for SQL. It fits certain needs, and SQL-like expression is not that.
Don Burks | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Cloudant started off as our database backup system, replicating from our production servers to the Cloudant service. We were configured to fail over to them in the event of a local database outage. Cloudant's uptime and search features were so impressive, we switched over to using them as our primary backbone, with replication now going to a different set of servers. Cloudant delivered a high level of service, and we were able to grow as a result.
  • Outstanding query interface
  • Full text searching!
  • Remarkable uptime and support
  • I would love to able to have more performance advice on my database.
I always advocate for choosing to store data in a manner that represents how you are going to be querying it. If you need well-indexed, performant queries, then Cloudant is an outstanding backend DbAAS that will support your business needs. Cloudant also takes care of stale view indices and other common maintenance tasks for you.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We were developing an IOT solution to reduce the power consumption in housing communities, for which IBM Bluemix was helping us a lot to achieve it. I was the major developer and architect for the team. Since the project was confined within our department we were using it only within our department.

Our main business objective was to perform data analysis on the data obtained - we had to store the IoT related information in the database and do fast processing on the data so we had to go with NoSQL database and indeed Cloudant was readily available - already integrated with Bluemix and much easier option was it stores the data as JSON which was much more convenient to our use case.
  • Easy integration
  • Better performance
  • High availability
  • Very limited functionality
  • Not much cloudant database management tools available
The cloudant sync option was very helpful during migration process for smaller data, but if you have large amounts of data, then import options are not that great or the documentation for importing was not that helpful.
Peter Ivie | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use Cloudant to store the data that can't be easily recreated.
  • I like that I can group multiple data objects into a single request to reduce the cost.
I haven't tried it at scale, but it was extremely easy to get started and works very well for what I am using it for. The low end price point can't be beat. Really, it's physically impossible without them paying me to use the site... now there is an idea! Thanks Cloudant
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We are using Cloudant as a base for our search engine! We have a search engine for arabic quotes and proverbs that is extracted from social media, we daily add around 20K records to our Cloudant database. We currently have around 9 million records. Basically we depend on Apache Lucene which is implemented with the database to serve as our search engine.
  • The indexing is fast.
  • Our data is safe there, we rarely have problems accessing or requesting the data.
  • One great thing is that we can address different boolean functions in our queries.
  • The ability to talk to the database through web services is great.
  • The analytic reports about the use of the database needs improvements.
  • A year or 6 months reports for the post/get hits will be great add.
For my case and my experience with Cloudant, it's well suited for search engines. If you have the data you can build a search solution above it in no time.
Denis Voloshko | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We are using Cloudant as storage for events data and logs for further analysis.
  • Scales well.
  • Full access via http is great!
  • I personally like replication to vanilla CouchDB to use it locally from time to time.
  • Downloading data from Cloudant is a pain. Feplication via http is slow.
  • I would add the ability to use external functions for Cloudant, as it's implemented in CouchDB.
Cloudant is good for storage for unstructured data and documents. I use it as alternative storage of raw events data (in addition to Localytics etc).
Score 9 out of 10
Vetted Review
Verified User
Incentivized

I am the founder of my 1 person startup, which develops a mobile application for virtual Stock Trading. The mobile app originally stored all user data (their portfolio, watchlist, account balance etc.) on the device itself. There were several scenarios where users ended up losing their app's data, for example hardware upgrades, OS upgrades on the same device, factory reset of the device. Also, because data was stored locally on the mobile device, users were tied down to using only one device.

The problems Cloudant solves for this app:

1. Persisting user's across physical device upgrades, OS upgrades on the same device, factory reset of the device, uninstall-reinstall of the application.

2. Synchronizing data between multiple devices for the same user giving them a true cloud experience which was lacking before.

As of now, I only have one product and it uses Cloudant. However I am extremely pleased with my experience with Cloudant and plan to use Cloudant for my future products as well.

  • Wide array of client-side libraries (Android, iPhone, Java PHP, JavaScript to name a few) provided by Cloudant make development easier and streamlined.
  • It is not JUST a DB - Ability to write JavaScript code on the Cloudant server makes it function as a web service provider along with a DB.
  • Cloudant is a true DBaaS provider. It is as close to one-click setup as it can be, and deployments take almost no time.
  • Cloudant provides bidirectional data replication
  • REST APIs
  • Per-document read privileges would be nice
  • Content Push - It would be good to see an in-built feature where a pool of clients can be linked to one or more documents so every time a document changes, the pool of clients linked to that document are notified of changes.
  • Provide a few templates for creating Filters on the DB.
Cloudant is well suited for scenarios in multiple cases:
1. Developers don't want to learn about setting up a database etc., and would rather focus on writing code to use the database.
2. An organization does not have dedicated resources to set up and maintain a database.
3. Writing micro-web services - in such a case, an organization can use Cloudant both as a DB and as a web server instead of setting up and maintaining two separate servers.
4. If an organization supports multiple client platforms, Cloudant is the way to go because it provides multiple client libraries as well as a REST API.
January 04, 2016

Cloudant, great for ACRA

Miguel Angel Merino Vega | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We decided to use Cloudant to implement an error handling database using ACRA on our Android Applications. First we tested it with a new application; after our first experience we decided to use it across all developments.

We needed a repository suited for ACRA to alert on any crashes our applications could experience. We looked for information and Cloudant's name appeared.
  • Fair cost and possibility to stay on free usage program.
  • High availability. Our databases never ever experienced falls.
  • Fair documentation access. We could find tutorials across the web.
  • The learning curve could be a little tough if used for first time.
  • UI could be redundant and unintuitive in some cases (at least about 1 year ago).
  • Little integration with other tools
Scenarios for the best use of Cloudant in our opinion are:
* Error handling logs.
* Spacial log database.
* Audit logs.
* Chats and social databases.
If you need a cloud repository for anything, Cloudant will be there for you. You could ease the burden of your main database and use Cloudant for these use cases.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We use cloudant as trustable path for a project associated with the Internet of Things. We control assets via a sensor and collect information about the gps position, their visibility and the time it has being registered. We save that in a local CouchDB database and use cloudant to replicate that information in a secure way.
  • Documentation. You really do well in that.
  • Reliability. We think IBM cloudant makes us feel secure with our data, we manage sensible information that we don't want to be open to the world.
  • Time. Everything can be done quickly. No too many configuration steps. The Cloudant API just works
  • Lack of a local version. We have to use alternatives as CouchDB or pouchdb.
  • The integration with other nosql databases should be easier.
  • Official wrappers for languages like python. That would be very useful.
I think that cloudant is appropriate everywhere you need to handle big quantities of data, and the confidentiality of that data is really important, and you need to keep the data organized with respect to several intricate variables. It would not be appropriate for small projects, or perhaps for projects were internet connectivity is an issue.
January 04, 2016

Cloudant DBaaS review

Score 7 out of 10
Vetted Review
Verified User
Incentivized
Cloudant is being used widely in our company across several projects while some of our classified data is still stored on our self-managed servers. DBaaS does save lots of work on deployment and maintenance, moreover, since most of our projects are hosted with Softlayer, where Cloudant hosts with as well, the network latency between our servers and Cloudant doesn't have significant impacts. In addition, NoSQL introduces a new way to make the query and big data storage easier with the understandable API context, programmers who are not familiar with database operations can still figure out the logic at the data processing part.
  • DBaaS means there is no need to deploy your own servers, which saves you the initial investment on hardwares.
  • Cloudant uses JSON as storage data format, which is commonly supported by all languages. As a result, no cost on data conversion.
  • Owing to the relationship between Cloudant and IBM, they can always get the best support and discounts for customers. For example, choosing Cloudant single tenant plan with hosting at Softlayer, there will be some discounts for you.
  • The single tenant plan seems to be expensive for some SMEs - data size may not reach the half of its minimum storage size, however, multi-tenant makes them feel unsafe for their business information.
  • The query language is not friendly for developers who are just moved from the SQL (MySQL, MSSQL...etc). It requires totally different skills.
Projects which with less classified data and less initial budget for production environment are great to use Cloudant multi-tenant service for the first several versions. For those sensitive data, unless purchasing the single-tenant plan, the multi-tenant context cannot ensure you a stable and provide the business level SLA.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We moved our SQL server database to Cloudant to allow for quick changes and easy testing. Using Cloudant allows for a super easy clone of the database with a simple one HTTP request. It also allows us to change our data schema without the craft related to SQL based databases. I had to write a small Object-Document-Mapper and didn't have to change the rest of the application. The price of using Cloudant was lower than a hosted SQL server.
  • Easy setup
  • Easy schema changes
  • Easy backup and restore
  • The tools for browsing and changing data
What is the price of using Cloudant?
How easy it is to migrate from SQL Server to Cloudant?
Return to navigation