We performed a comparison between Google Cloud Spanner and Oracle Database as a Service based on real PeerSpot user reviews.
Find out in this report how the two Database as a Service solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The most valuable feature of the solution is its scalability. Scalability comes with two options, among which Google Cloud Spanner can scale horizontally, compared to other relational databases that scale vertically."
"The application deployment in the cloud is the best feature of the infrastructure."
"We can scale the solution if we need to."
"Google Cloud Spanner is stable."
"Oracle DBaaS performs well. It's similar to the MS Store."
"In terms of structured databases, I support SQL-based databases. SQL has its place, but not for plannable structure and transactional databases. At the same time, Oracle is very much optimized."
"Oracle Database as a Service is stable."
"The most valuable aspects of the solution are the general database system resilience and security."
"The most valuable feature of Oracle Database as a Service is the object types. The object types are not available in other databases, such as SQL and Postgres. Additionally, the security is very good."
"One of the key features is Oracle Database as a Service. We chose to implement it as a service, which provides good performance, for example. Flexibility and other features let us implement database research with the SQL team range of features also."
"It is a good solution and has a large community."
"The solution is very stable. It's very powerful."
"I want to improve the deployment of cameras and surveillance infrastructure."
"The tool needs to improve horizontal scaling."
"The cost can be a bit high."
"Google came up with something called Cloud Spanner Emulator, which fails to work like the real product if I want to develop some code and run a database locally on my machine."
"The price of the solution is an area of concern. From an improvement perspective, the price of the solution should be lowered."
"Its application development could be enhanced to fully utilize its features."
"The area in this solution that could be improved is that currently, it's difficult to do the setup. You need to do all kinds of command lines to get it set up. If that setup becomes easier and easily manageable, that would be great."
"The solution uses a large amount of CPU space, which could be improved."
"There is room for improvement in PL/SQL. It is not user-friendly and it is hard to understand."
"Oracle Database as a Service's initial setup was very complex."
"The solution provides the same type of RDBMS engine for all use cases. They need to provide different products that will be suitable for all use cases. The solution does not support the documentation of databases."
"I would like to improve the stability of the Oracle database."
Google Cloud Spanner is ranked 8th in Database as a Service with 4 reviews while Oracle Database as a Service is ranked 4th in Database as a Service with 63 reviews. Google Cloud Spanner is rated 9.0, while Oracle Database as a Service is rated 8.6. The top reviewer of Google Cloud Spanner writes "A stable and scalable relational database that ensures a return on investment for its users". On the other hand, the top reviewer of Oracle Database as a Service writes "Quite stable and renewable with an easy setup". Google Cloud Spanner is most compared with Amazon RDS, MongoDB Atlas, Oracle Exadata Cloud at Customer, Google Cloud SQL and Redis, whereas Oracle Database as a Service is most compared with Amazon RDS, Oracle Exadata Cloud at Customer, SQL Azure, Google Cloud SQL and Redis. See our Google Cloud Spanner vs. Oracle Database as a Service report.
See our list of best Database as a Service vendors.
We monitor all Database as a Service reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.