IBM Cloudant vs. Google Cloud SQL

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.

Incentivized

Although Google Cloud SQL has room for improvement by addressing a minor lack of features, its features and services keep it high among other SQL database products. It is very fast compared to others. Since it is cloud-based, maintenance is also easier. Integration capabilities are also more than expected.

Incentivized

• 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!!

Incentivized

• Very easy to use and migrate existing database systems to Google Cloud SQL system
• Easy to query with real-time query assessment as well as processing metrics to help optimize the queries
• No need to learn any other querying language (like in Hadoop ecosystem), as SQL works pretty fine
• Easy-to-use GCP portal to type in queries and see the results on the screen (no need to go on command line )
• Easy to set up

Incentivized

• 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.

Incentivized

• Increasing support for more database engines may enable a wider range of application needs to be met.
• Implementing and updating cutting-edge security features on a constant basis.
• Streamlining and enhancing the tools for transferring data to Google Cloud SQL from on-premises databases or other cloud providers.

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

Incentivized

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.

Incentivized

Everything is great about using Google Cloud SQL, but I only dock marks for requiring the Cloud Auth Proxy to connect locally without using allowed networks. I get that it's necessary since it's behind a VPC but it's just a bit clunky to use. That being said, I wouldn't really call that a big deciding factor for Google Cloud SQL's usability.

Incentivized

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.

Incentivized

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.

Incentivized

Very happy by the commitment given by the team which has been really good over the last 7 years of usage.

Incentivized

GCP support in general requires a support agreement. For small organizations like us, this is not affordable or reasonable. It would help if Google had a support mechanism for smaller organizations. It was a steep learning curve for us because this was our first entry into the cloud database world. Better documentation also would have helped.

Incentivized

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

Incentivized

• 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.

Incentivized

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.

Incentivized

In our experience, we were down for almost a day, because Database Engineers at Rackspace weren't able to understand or provide a solution, and when they did, they had to recreate the database from the scratch. On a server, this is time consuming. When we faced a similar scenario on Google Cloud SQL it was as easy as to recover from the last image through the console. We were back up in less than 30 minutes. Such a solution, saves you money by reducing churn and keeping the business operating.

Incentivized

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.

Incentivized

• 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.

• When first migrated to a cloud environment, the Cloud SQL instance had a higher cost than our former MySQL VM instance, but many other infrastructure costs had also been reduced and the total balance of our migration to the cloud was a reduction of 45% of our infrastructure costs.
• DB performance has increased and maintenance tasks reduced in a high percentage.
• Disaster recovery plans are easier to follow now than before our cloud migration.

Incentivized