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
Focus on your app development instead of on database management with Cloudant
Data model flexibility (18)
Deployment model flexibility (18)
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 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
Supported: Data model flexibility
Supported: Deployment model flexibility
IBM Cloudant Video
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. Clo...
English, 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).
MongoDB Atlas and Azure Cosmos DB are the closest competitors we found with Cloudant, especially in terms of fixed pricing and having a GUI for easy viewing and quick edits of data. Cloudant's pricing model flat out beats MongoDB Atlas' in terms of how easy it would be to predict costs. Cosmos DB is a much closer competitor, as it integrates well with Azure's stack similarly to Cloudant and the rest of the IBM Cloud stack; similar [throughout]-based pricing and replication options; and even the GUI and ease of query using SQL, which my team and I were more familiar with. Where Cloudant beats out Cosmos DB is again having a more simple pricing model (ops/sec vs Cosmos' "request units" voodoo) and being based on open-source software assuaging fears of vendor lock-in.
IBM Cloudant is great for quick deployment and configs of a database service, especially when it comes to rapid prototyping. In a research capacity, we need to spin up web services and run experiments quickly. IBM Cloudant is a fuss-free database service [that] aids in this process. Extracting data from [IBM] Cloudant can be done programmatically as well, which makes working with it much more ideal.
The gap that we wanted to cover was to deploy a self-managed CouchDB environment, which would allow us the bidirectional replication of Databases through several physical locations of the same client. IBM Cloudant was the best choice after evaluating some other platforms with similar solutions.
The documentation of Cloudant alone has made it my database service of choice. With MongoDB you have to manage hardware, sharding, networking... Cloudant takes all the hassle out of storage allowing you to focus on more important tasks.
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.
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 flow is not as smooth as the built-in capability in Cloudant.
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. Initially, when we tested against Cassandra, we found Cloudant faster when compared apples to apples for concurrent requests to the data base.
I have mainly used Cloudant as I work with IBM Cloud in my role and therefore it was easiest (and cheapest) to set up for the small scale prototypes we are building. (Which do however sometimes lead to scaled implementation)
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 experience with in the past....
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's search engine works well, but Elasticsearch makes it easier to visualise data through Kibana.