TrustRadius Insights for IBM Cloudant are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Efficient Data Retrieval: Users have highlighted the ease of retrieving data for analysis as a key benefit, with many stating its importance. Reliable and Speedy Updates: Customers value staying updated with market changes due to the tool's reliability and speed, as mentioned by multiple reviewers. Excellent Customer Service: The efficient response time for bi-directional syncs and valuable statistics provided by Cloudant are appreciated by users in terms of decision-making. Smooth Integration Process: Users find the integration with Cloud Functions and a GUI designed for non-engineers positively mentioned, indicating its user-friendly approach. Advanced Data Storage Capabilities: Users praise the tool's indexing and data storage capabilities, emphasizing their satisfaction with this aspect of the service.
Loading Reviews List....
IBM Cloudant Reviews
4 Reviews
ManufacturingMechanical Or Industrial Engineering1Consumer Electronics1Consumer Goods1Aviation & Aerospace1
We used IBM Cloudant as a distributed, fully managed JSON database for IoT use cases. API integration was a must, and all the support to Apache CouchDB made a positive difference. Overall support and documentation from IBM Cloudant were satisfactory, as well as pricing. Global availability was generally good, except for China. Availability and SLAs were never a problem and the platform has always been stable.
Pros
API integration and support through CouchDB standards.
Managed Services.
Cons
Global availability, especially in Asia.
IBM Cloudant support is generally robust, but in some occasions we had to find solutions by ourselves.
Likelihood to Recommend
IBM Cloudant is generally a good tool for a NonSQL, document oriented Database as a Service. It is very scalable and reliable, and managed services through IBM seems to be working well. You can consider as almost no lock-in since it is based on CouchDB API structures and you can migrate to any other provider in the future if needed. If you need real Global Availability, like Asia / China you may need to look for alternatives.
VU
Verified User
Executive in Information Technology (Consumer Goods company, 10,001+ employees)
Currently, it's being used by our E-commerce Team, which spans all our digital solutions. It's currently used along with the Node-Red instance hosted within the IBM environment with multiple such instances supporting multiple Cloudant databases for all the database and storage-related facilities. IBM Cloudant helps manage it and is a very easy to adapt format helping with quick deployments.
Pros
It is NoSQL
It has better performance than Mongo Atlas
Queries are easy to use and support for views is also helpful
Cons
Speed of searching through records can be improved.
Some ML to predict enhancement in queries can surely help IBM and clients mutually target optimal solutions.
Views accepting multiple parameters.
Likelihood to Recommend
It is currently being used by our e-commerce team, which spans all our digital solutions. Used along with the node-red instance hosted within the IBM environment. With multiple such instances supporting multiple Cloudant databases for all storage/database facilities, it is very easy to manage.
We use Cloudant as an IBM proposed DB solution for dedicated cloud foundry IBM cloud environments. The initial structure is for a weird implementation to use Cloudant, as we are using it as a cache for some middle life data. I know cache is not a right implementation for Cloudant, but it offered a database sync between datacenters.
Pros
Cross datacenters sync
Quick sync performance and data transfer
Some pretty high add/update response time
Cons
We had some issues with concurrent data saving/reading
Due to CouchDB implementation the purge of some database field requires a copy of the desired fields to a new database
Could find an easier way to assign access permission
Likelihood to Recommend
As a incremental database I think the best use case is to store a sequential path of data events - like transactions storage.
VU
Verified User
Engineer in Information Technology (Aviation & Aerospace company, 5001-10,000 employees)