Google Cloud Spanner is a cloud database-as-a-service product offered as a service on Google Cloud Platform (GCP).
N/A
IBM Cloud Databases
Score 8.2 out of 10
N/A
IBM Cloud Databases are open source data stores for enterprise application development. Built on a Kubernetes foundation, they offer a database platform for serverless applications. They are designed to scale storage and compute resources seamlessly without being constrained by the limits of a single server. Natively integrated and available in the IBM Cloud console, these databases are now available through a consistent consumption, pricing, and interaction model. They aim to provide a cohesive…
N/A
Pricing
Google Cloud Spanner
IBM Cloud Databases
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Google Cloud Spanner
IBM Cloud Databases
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Google Cloud Spanner
IBM Cloud Databases
Features
Google Cloud Spanner
IBM Cloud Databases
Database-as-a-Service
Comparison of Database-as-a-Service features of Product A and Product B
Google Cloud Spanner is suited for limitless horizontal scaling while maintaining strong consistency which needs to support ACID. NoSQL databases work in scaling but no ACID support. RDBMS support ACID, but horizontal scaling is not as great. The API it provides result in some limitations to related areas of the code, such as connection pools or database linking framework. So high # of connection pools can vary.
Less Appropriate Scenario: 1) Small Scale or Low Budget Projects 2) Organizations with limited expertise in cloud technologies may find the learning curve steep, especially if they are not familiar with the IBM Cloud platform 3) If database requirements are highly dynamic and change frequently, the comprehensive features and management provided by IBM Cloud Databases might be overkill. A more flexible, self-managed solution could be preferable for adapting to rapid changes.
The ease of setup was effortless. For anyone with development experience, a few simple questions such as name and login data will get you set up.
The web application to manage cluster settings, billing settings and even introspect the data was simple and most importantly worked all the time. This can not always be said for web interfaces of other products.
Better cost reports, before just increasing to another tier, thus increasing the price. This is critical for early stage startups, where budget is tight.
Add more data center options. As a comparison, a similar service, Aiven.io has dozen more options than Compose (basically all big cloud providers). We moved from AWS to Digital Ocean, which made us stop using Compose, since Compose forces us to be either on IBM or AWS.
IBM is our trusted partner which never failed to meet our expectations. Stability, efficiency, usability and security is a must have for our business which is fully provided by IBM Cloud Databases
IBM Cloud Databases' pricing structure is easy to understand, and if you choose the right product, you can operate your system at minimal cost. Although there is ample documentation available, there doesn't seem to be a user community running on it, so specific usage know-how and troubleshooting can sometimes take longer than expected.
Support is helpful enough, but we haven't always had questions answered in a satisfactory manner. At one time we realized that Compose had stopped taking database snapshots on its two-per-day schedule, and had in fact not taken one for many days. Support recognized the problem and it was fixed, but the lack of proactive checks and the inability to share exactly what happened has caused us to look elsewhere for production work loads
At that point, we were looking at something [that] can hold our relational database, [...] provide stable connection, and maintain high ACID transition. BigTable is for nonrelational database so it was out of our [sight] very quickly. BigQuery is a data warehouse that can hold huge amount of data but not ideal for transition. AWS RDS is [...] similar to Spanner but because most of our services are already on GCP, so we went with Spanner.
The reason why I choose IBM Cloud Databases is that the IBM cloud toolset is already being used in other functions of the company and by using IBM Cloud Databases, the other cloud tools are better embedded and integrated. If the company is set to use amazon tools, I would go for rds.