Likelihood to Recommend Our organization found Cloudant most suitable if One, a fixed pricing structure would make the most sense, for example in a situation where the project Cloudant is being used in makes its revenue in procurement or fixed retainer — thus the predictability of costs is paramount; Two, where you need to frequently edit the data and/or share access to the query engine to non-engineers — this is where the GUI shines.
Read full review I find Qubole is well suited for getting started analyzing data in the cloud without being locked in to a specific cloud vendor's tooling other than the underlying filesystem. Since the data itself is not isolated to any Qubole cluster, it can be easily be collected back into a cloud-vendor's specific tools for further analysis, therefore I find it complementary to any offerings such as Amazon EMR or Google DataProc.
Read full review Pros 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!! Read full review From a UI perspective, I find Qubole's closest comparison to Cloudera's HUE; it provides a one-stop shop for all data browsing and querying needs. Auto scaling groups and auto-terminating clusters provides cost savings for idle resources. Qubole fits itself well into the open-source data science market by providing a choice of tools that aren't tied to a specific cloud vendor. Read full review Cons 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. Read full review Providing an open selection of all cloud provider instance types with no explanation as to their ideal use cases causes too much confusion for new users setting up a new cluster. For example, not everyone knows that Amazon's R or X-series models are memory optimized, while the C and M-series are for general computation. I would like to see more ETL tools provided other than DistCP that allow one to move data between Hadoop Filesystems. From the cluster administration side, onboarding of new users for large companies seems troublesome, especially when trying to create individual cluster per team within the company. Having the ability to debug and share code/queries between users of other teams / clusters should also be possible. Read full review Likelihood to Renew the flexibility of NoSQL allow us to modify and upgrade our apps very fast and in a convenient way. Having the solution hosted by IBM is also giving us the chance to focus on features and the improvement of our apps. It's one thing less to be worried about
Read full review Personally, I have no issues using Amazon EMR with Hue and Zeppelin, for example, for data science and exploratory analysis. The benefits to using Qubole are that it offers additional tooling that may not be available in other cloud providers without manual installation and also offers auto-terminating instances and scaling groups.
Read full review Usability It's mostly just a straight forward API to a data store. I knock one off for the full text search thing, but I don't need it much anyways. Also, the dashboard UI they give is pretty nice to use. It provides syntax-highlighting for writing views and queries are easy to test. I wish other DBs had a UI like this.
Read full review Reliability and Availability it is a highly available solution in the IBM cloud portfolio and hence we have never had any issues with the data base being available - we also do continuous replication to be on the safer side just in case some thing goes awry. We also perform twice a year disaster recovery tests.
Read full review Performance very easy to get started and is very developer friendly given that it uses couchDB analytics. It is a cloud based solution and hence there is no hardware investment in a server and staging the server to get started and the associated delays/bureaucracy involved to get started. Good documentation is also available.
Read full review Support Rating Very happy by the commitment given by the team which has been really good over the last 7 years of usage.
Read full review Online Training online resources are good enough to understand but there is nothing like testing. In our case, we discovered some not documented behavior that we take in count now. Also, the experience in NodeJs is critical. Also, take in count that most of the "good practices" with cloudant are not in online courses but in blogs and pages from independent developers
Read full review Implementation Rating Test the architecture on CouchDB helped us to address initial design flaws. The migration to Cloudant as such was very painless. We have migrate our replication system to Cloudant Android Sync for mobile devices. We have regular informal contact with the Cloudant leadership to discuss our use cases and implementation strategies. Read full review Alternatives Considered 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.
Read full review Qubole was decided on by upper management rather than these competitive offerings. I find that
Databricks has a better Spark offering compared to Qubole's Zeppelin notebooks.
Read full review Scalability The service scales incredibly well. As you would expect from CloudDB and IBM combination. The only reason I wouldn't score it a 10 is the fact that document trees can get nested and nested very quickly if you are attempting to do very complex datasets. Which makes your code that much more complex to deal. Its very possible we could find a solution to this problem with better database planning to begin with, but one of the reasons we chose a service over a self-hosted solution was so we could set it up quick and forget about it. So we weren't going to dedicate a team to architecture optimization.
Read full review Return on Investment IBM Cloudant is very secure and we never have to worry about losing data/unauthorized access It is one of the best data backup system and works well Global availability means it is easy to connect to the nearest data center and this reduces load time which is great. Read full review We like to say that Qubole has allowed for "data democratization", meaning that each team is responsible for their own set of tooling and use cases rather than being limited by versions established by products such as Hortonworks HDP or Cloudera CDH One negative impact is that users have over-provisioned clusters without realizing it, and end up paying for it. When setting up a new cluster, there are too many choices to pick from, and data scientists may not understand the instance types or hardware specs for the datasets they need to operate on. Read full review ScreenShots