Reviews (1-22 of 22)
- 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.
IBM Cloudant Review: "Cloudant is a great choice for DBaaS for mobile apps on multiple platforms and devices..."
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 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 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.
- 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).
- 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.
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.
Finally, considering CouchDB is part of Bluemix, you will have the chance to grow, adding on more services for your app.
- Authentication improved with the API keys
- Synchronization with https, which means secure and trustable syncs
- Scale in a transparent way
- Free start with the $50 allowance makes Cloudant the best way to start
- It would be nice to have a way to import bulk data
- There must be a better way to check usage. There are a lot of transactions not shown in the actual report
- There must be a way to reset a db -- a way to set the actual data as the base and eliminate all deleted docs
It is not so good for report apps or to handle too much structured data, because the Cloudant query can turn in something tricky, specially if your data model gets complicated.
- I like that I can group multiple data objects into a single request to reduce the cost.
- 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.
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
* 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.
- 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.
- Coudant allows unlimited secondary index fields when compared to others that have certain limitations.
- Cloudant also has the ability to do bi-directional sync for replication and synchronization.
- Cloudant can run on bare metal and virtual machines.
- Cloudant can also be deployed in multi-user or private cloud environments.
- Sometimes, there are no slower response times [than] when trying to pull records - I mean that slowness is in terms of milli-seconds :-)
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.
- Support has been great addressing any issues.
- The documentation is very easy and straight forward to follow.
- The many storage locations and migration capabilities allow for quick and easy access to data wherever needed.
- Not supporting temporary views can be limiting at times.
Do you need remote storage with easy to follow documentation?
Do you already use NoSQL in any other projects?
Is JSON the data you wish to be able to storage and index easily?
Do you need to be able to easily replicate your database stores?
Do you need to share your database with multiple users?
- 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.
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.
- 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.
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.
- 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.
- Easy to configure and operate through the GUI.
- Seamless replication to CouchDB (like PouchDB).
- The multi-tentant option is free for low utilization (HTTP requests and storage).
- Instant database compaction on multi-tenant.
How easy it is to migrate from SQL Server to Cloudant?
IBM Cloudant Scorecard Summary
About IBM Cloudant
See here for pricing and support.
IBM Cloudant Video
IBM Cloudant Competitors
There is never a charge for the first $50 of usage each month. After that, data volume is charged at $1 per GB/month, "heavy" API requests (PUTs, POSTs, DELETEs) are charged at $0.015 per 100 each month, and "light" API requests (GETs, HEADs) are charged at $0.015 per 500 each month. API requests that read or write multiple JSON docs in bulk count as 1 API request.
IBM Cloudant Technical Details
|Supported Languages:||English, French, German, Italian, Japanese, Korean, Portuguese/Brazil, Spanish, Chinese Simplified, Chinese Traditional|