I use Google Cloud Storage Nearline primarily as a storage solution for user data related to applications and websites. It serves as a container for saving and storing this data.
Additionally, I utilize it for handling temporary files, particularly when working with Google Cloud Functions and Firebase Functions that have limitations with file sizes over 32 MB. In such cases, the data must first be downloaded to Google Cloud Storage before processing.
The most valuable aspect of Google Cloud Storage Nearline is its integration with the wider Google Cloud ecosystem. It works seamlessly with multiple Google Cloud services such as Cloud Functions, Cloud Run, and cloud operations like logging. This deep integration, facilitated by tools like Eventarc and built-in triggers, ensures a cohesive working environment. This value, despite sometimes higher costs compared to alternatives, justifies its use within a comprehensive suite of services.
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.
I have been using Google Cloud Storage Nearline for at least four years.
In my experience, Google Cloud Storage Nearline is stable. I have not encountered significant issues with data stability or missing files, though there can be occasional latencies due to maintenance. The stability is generally high for typical use cases within projects lasting under a year.
I have not faced scalability issues with Google Cloud Storage Nearline. I have not encountered bucket capacity limits or similar challenges that would require advanced scalability techniques in my projects.
I have generally navigated issues independently, relying on forums, blogs, and other resources. I find that contacting Google support can be challenging, so I prefer finding workarounds for software issues myself.
Neutral
I previously used Amazon Web Services. The switch to Google Cloud Storage Nearline was primarily driven by the companies I worked for, which were already integrated into Google Cloud ecosystem. Despite potentially higher costs, the integration benefits with services like BigQuery and Firebase were compelling.
The initial setup is relatively straightforward for those familiar with cloud fundamentals like service accounts and IAM. It could take around eight to nine out of ten in ease of setup. However, for users without cloud experience, the setup could be complex due to the need for understanding service integration and permissions.
The deployment was managed by me, or, in similar scenarios, could be handled by any engineer familiar with the company's requirements and cloud services.
From a pricing standpoint, Google Cloud Storage Nearline is more expensive compared to some alternatives like Amazon. I would rate the pricing at five on a scale of one to ten.
Amazon was the alternative solution I had used before switching to Google Cloud Storage Nearline.
Overall, Google Cloud Storage Nearline is a solid solution within Google ecosystem, which is why I rate it seven out of ten.
Enhancements in documentation and user guides, along with more competitive pricing, could elevate its standing.
