IBM Cloudant Reviews

We use Cloudant to store production data used in analytics/machine learning models. We run an agricultural management platform to help farmers improve efficiency and reduce risk.

We have saved time with ease of integration. Need to explore more pros and cons in a production environment.

We use Cloudant for replicate data from our Blockchain platform. With Cloudant we can make queries and reports for our managers that want to see how the transactions in blockchain are working. It's very user friendly and it's stable too. Without it we did not have any visibility of the transactions.

I did not receive these benefits. It's very stable but we have to monitor like any other instances, I think there is no service that can self monitor itself.

We use IBM Cloudant primarily in our Watson IoT Platform, in combination with IBM Cloud Pak and Node-Red to receive and store IoT sensor data. It is used across a significant part of our organization, since we are an IBM Business partner for the entire IBM Maximo software stack. Everywhere IOT or Predictive Maintenance Insights is involved we make use of WIOTP in combination with IBM Cloudand.

The ease of use leads to fast implementation. Even with less knowledge, a consultant is able to have a fast start based on the combination of IBM Cloud Pak and integrated IBM Cloudant services.

Cloudant 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 business critical for our company and our many customers rely on its performance on a daily basis to perform their activities.

Yes, Cloudant operations team manages the underlying systems on our behalf and the support team is very helpful and proactive. They monitoring when the system is reaching some critical metrics. Some operations like automated backups and exports for reporting are still up to our team, though.

Cloudant is being used as the main storage system for all my current projects. Being able to easily retrieve and publish data to Cloudant over a standard and proven protocol has made it much easier to implement storage in any language and system required. Having such easily available storage has sped up the entire development process greatly.

We were using IBM Cloudant as our cloud storage platform for a project where we were collecting real-time environmental data. Later, we used this raw data for data manipulation and data visualization. The data was collected using a physical custom-made IOT sensor that was connected to IBM Cloud.
The purpose of this product was to aid impact investors to make guided, data backed decisions.

The scope of our project was never grand enough to to observe the effect of scale. But, with whatever we worked around, it performed seamlessly.

I'm using Cloudant as a persistent backend to a web app that leverages PouchDB. It is easy to query and seamlessly synchronizes the app data to the cloud.

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 the right implementation for Cloudant, but it offered database sync between datacenters.

Features like replication, monitoring, and ease of operation have been the key benefits. Also, the ability to work with JSON natively is also a big plus.

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.

Since it is a Database as a Service offer on IBM Cloud, you do not have to worry about basic infrastructure, provisioning and performance metrics. The user interface could improve but it is not a problem. So basically you can expect the promise of lower TCO to come to life in this case. In general no availability issues - so very minimal support cost.

Cloudant is the database for all our mobile applications with offline-first architecture, and it's the best option to keep everything synced and secure.

This is the best way to use CouchDB, because Cloudant adds the authorization layer required for a real live app, and also the infinite capacity with the flexibility to grow from $0 to whatever is required according to the amount of users you need to support.

Also, we have now using Cloudant as the main database for data capture apps and the source for all our catalogs in order to free resources from our rdbms system.

Finally, considering CouchDB is part of Bluemix, you will have the chance to grow, adding on more services for your app.

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.

Monitoring the execution time and optimizing based on that has surely helped.

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.

We achieved a time saving milestone due to the automation of the maintenance. Due the company policy we implemented an external application for that but Rest API gave us the ability to do that. The support is being reduced to minimal as this app is taking care of routine tasks daily.

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.

It is being used as a noSQL database across the organization for big data analytics and is used amongst other things for text analytics as it permits unlimited index fields.

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.

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.

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.

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.

We use Cloudant as our primary data store for a marketplace solution.

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.

It's our primary store for user-generated and transactional data.

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.

We use Cloudant to store the data that can't be easily recreated.

We are using Cloudant as storage for events data and logs for further analysis.

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.