Performance-wise, the tool is working fine. With the tool, the trigger is not there. That is one of the things I noticed, as we cannot see or create a trigger. It is not possible to create a trigger, update a trigger, or delete a trigger. There could be some alternative in Google Cloud Spanner to create the trigger and all. Definitely, there must be some solution and I am very eager to explore such areas. If you ask me, I would say that I can easily maintain the product because I know about it if somebody is not aware of how to configure or how to do App Engine's configuration in Google Cloud, where App Engine and Kubernetes are core parts of the application. If you know App Engine and Kubernetes, then you can maintain it easily. Google Stackdriver allows you to trace all your configurations. There are a lot of features in Google products. Firstly, try to explore all the features before start to use the tool since then only you can use it. All the features are available in the tool and one should not doubt over why one can't utilize them. I rate the tool a nine out of ten.
Though Google Cloud Spanner is a relational database, there are some things that a person needs to know upfront. If your database schema is way too Static, you know how it will look if you use Google Cloud Spanner. If you make a lot of changes in the database schema during the development life cycle, you shouldn't consider the use of Google Cloud Spanner initially. A schema change is a pretty complicated process in Google Cloud Spanner. I rate the overall solution a nine out of ten.
Spanner is a very good infrastructure offered by Google Cloud, but I personally lack experience in Python since I only received my diploma in January. Spanner is easy to use for those with experience in Python and machine learning, and that deployment and execution are currently working well. I would rate it a ten out of ten.
We're using the latest version of the solution as it's a cloud product. It always self-updates. I'd recommend the solution to other users. From what I have experienced so far, I would rate it eight out of ten. I've been happy with its general capabilities.
Find out what your peers are saying about Google, Amazon Web Services (AWS), Oracle and others in Database as a Service (DBaaS). Updated: October 2026.
Database as a Service (DBaaS) offers users a cloud-based solution for managing, hosting, and scaling their databases with ease. It eliminates the need for complex hardware setup, making it a smart choice for modern applications requiring flexibility and efficient resource management. Due to its cloud-native nature, DBaaS provides seamless integration with existing cloud infrastructures. Organizations appreciate the automated backups, easy scaling options, and support for various database...
Performance-wise, the tool is working fine. With the tool, the trigger is not there. That is one of the things I noticed, as we cannot see or create a trigger. It is not possible to create a trigger, update a trigger, or delete a trigger. There could be some alternative in Google Cloud Spanner to create the trigger and all. Definitely, there must be some solution and I am very eager to explore such areas. If you ask me, I would say that I can easily maintain the product because I know about it if somebody is not aware of how to configure or how to do App Engine's configuration in Google Cloud, where App Engine and Kubernetes are core parts of the application. If you know App Engine and Kubernetes, then you can maintain it easily. Google Stackdriver allows you to trace all your configurations. There are a lot of features in Google products. Firstly, try to explore all the features before start to use the tool since then only you can use it. All the features are available in the tool and one should not doubt over why one can't utilize them. I rate the tool a nine out of ten.
You need to look at the data set and company requirements. I rate the product a nine out of ten.
Though Google Cloud Spanner is a relational database, there are some things that a person needs to know upfront. If your database schema is way too Static, you know how it will look if you use Google Cloud Spanner. If you make a lot of changes in the database schema during the development life cycle, you shouldn't consider the use of Google Cloud Spanner initially. A schema change is a pretty complicated process in Google Cloud Spanner. I rate the overall solution a nine out of ten.
Spanner is a very good infrastructure offered by Google Cloud, but I personally lack experience in Python since I only received my diploma in January. Spanner is easy to use for those with experience in Python and machine learning, and that deployment and execution are currently working well. I would rate it a ten out of ten.
We're using the latest version of the solution as it's a cloud product. It always self-updates. I'd recommend the solution to other users. From what I have experienced so far, I would rate it eight out of ten. I've been happy with its general capabilities.