Documentation is an area for improvement in Google Cloud Storage Nearline. Documentation might cause some issues during deployment in future updates of Google Cloud Storage Nearline. Other than that, everything works flawlessly.
From a storage standpoint, it would be beneficial if the retrieval cost could be optimized, as it is comparatively higher than storage costs in Nearline.
One area that needs improvement is the documentation, which I find to be disorganized and not user-friendly. The lack of comprehensive walkthrough guides for specific use cases makes it difficult to follow. To enhance the experience, more detailed examples, guides, and tutorials from start to finish would be beneficial. Additionally, the cost compared to other providers like Amazon could be regarded as a downside.
The UI could be a little bit more effective. Now, the UI is just a white background, but it's really helpful if there are options to change the theme. I prefer that.
The suggestion for improvement primarily revolves around cost efficiency. Currently, Google Cloud Storage Nearline charges a minimum of thirty days for data access. I propose a more flexible approach. Instead of a fixed thirty-day minimum charge, there could be a programmatic adjustment based on data access patterns. For instance, if Google Cloud notices that certain data is no longer frequently accessed, they could automatically adjust the billing. When data isn't actively used, the charges for access to that data should decrease. This approach would ensure that users are billed fairly for the actual access they require, especially when data access patterns vary over time.
As a lead developer, I struggled with the documentation for GCP. This could be improved by being made more clear. Also, the interface for managing file storage in the buckets could be improved, together with improved search and filter options. For the next release, I would like to see the solution behave more like a regular file-based system. Google Cloud Storage depends on OS, or it's supposed to be on Google Drive or another storage service. Google Storage files are sometimes very different. The solution should be expanded to be like a file-based system so that you can build a fast tool that stores files in Google Drive.
They need a better, more visual, user interface for folders and files. Right now, you can see a list of five. You need to see some details, more folders, and be able to drag and drop the folders. That would be useful. Those new to GoogleCloud may struggle a bit with the setup.
Nearline security could be better. The solution could integrate better with SEIM tools. We need to improve anything related to security, whether we're talking about IT, the technology platform on the Cloud, etc.
The solution needs to offer better System Information and Event Management (SEIM). I'd like to discover how we could implement something like that within Google's cloud. We are currently running the solution, but if I want to have a better security strategy, I know I have to do something else. It doesn't really offer that as part of the solution.
Vice President at a financial services firm with 501-1,000 employees
Real User
Dec 15, 2019
The pricing could be improved. It's completely non-competitive at this time. We have some issues around date/time conversions. It requires a little bit of tweaking to get things done. You can't seem to import a date/time field into SQL. The solution needs more GUI support.
Google Cloud Storage Nearline offers cost-effective storage for infrequently accessed data, providing seamless integration with Google Cloud services and flexible retrieval options.Google Cloud Storage Nearline is designed for businesses that need reliable and secure storage for data that is not frequently accessed but still requires long-term retention. It integrates seamlessly with Google's suite of cloud services, providing adaptable storage solutions that handle data flow efficiently....
Documentation is an area for improvement in Google Cloud Storage Nearline. Documentation might cause some issues during deployment in future updates of Google Cloud Storage Nearline. Other than that, everything works flawlessly.
From a storage standpoint, it would be beneficial if the retrieval cost could be optimized, as it is comparatively higher than storage costs in Nearline.
One area that needs improvement is the documentation, which I find to be disorganized and not user-friendly. The lack of comprehensive walkthrough guides for specific use cases makes it difficult to follow. To enhance the experience, more detailed examples, guides, and tutorials from start to finish would be beneficial. Additionally, the cost compared to other providers like Amazon could be regarded as a downside.
The UI could be a little bit more effective. Now, the UI is just a white background, but it's really helpful if there are options to change the theme. I prefer that.
The suggestion for improvement primarily revolves around cost efficiency. Currently, Google Cloud Storage Nearline charges a minimum of thirty days for data access. I propose a more flexible approach. Instead of a fixed thirty-day minimum charge, there could be a programmatic adjustment based on data access patterns. For instance, if Google Cloud notices that certain data is no longer frequently accessed, they could automatically adjust the billing. When data isn't actively used, the charges for access to that data should decrease. This approach would ensure that users are billed fairly for the actual access they require, especially when data access patterns vary over time.
They should provide more options or flexibility in terms of pricing.
As a lead developer, I struggled with the documentation for GCP. This could be improved by being made more clear. Also, the interface for managing file storage in the buckets could be improved, together with improved search and filter options. For the next release, I would like to see the solution behave more like a regular file-based system. Google Cloud Storage depends on OS, or it's supposed to be on Google Drive or another storage service. Google Storage files are sometimes very different. The solution should be expanded to be like a file-based system so that you can build a fast tool that stores files in Google Drive.
They need a better, more visual, user interface for folders and files. Right now, you can see a list of five. You need to see some details, more folders, and be able to drag and drop the folders. That would be useful. Those new to GoogleCloud may struggle a bit with the setup.
Nearline security could be better. The solution could integrate better with SEIM tools. We need to improve anything related to security, whether we're talking about IT, the technology platform on the Cloud, etc.
The solution needs to offer better System Information and Event Management (SEIM). I'd like to discover how we could implement something like that within Google's cloud. We are currently running the solution, but if I want to have a better security strategy, I know I have to do something else. It doesn't really offer that as part of the solution.
The pricing could be improved. It's completely non-competitive at this time. We have some issues around date/time conversions. It requires a little bit of tweaking to get things done. You can't seem to import a date/time field into SQL. The solution needs more GUI support.