Overall Satisfaction with Google Cloud Storage
We use Google Cloud Storage (GCS) for a variety of needs. My company manages terabytes of healthcare claims data, which we analyze and present to our customers in an easy-to-use application, mobile app, and reports. We use GCS to stage raw claims data for injection, to stage post-processed data for indexing, and for intermediary storage for a variety of analytics tools.
- Really great, easy to use interface helps us manage files easily. Storage is fast and inexpensive, so we don't have to spin up storage instances locally
- Great set of command-line tools to manage data and storage options via scripts and apps, as well as an SDK means we can build GCS into our orchestration and operations tools
- Robust integration with other Google cloud tools means that we don't have to think too hard about using GCS for a variety of storage tasks as we interact with other Google services.
- Some CLI options are a little more difficult to use, like parallel uploads
- The new user interface hides an option (create public link) that we've used a bunch —still there but much less intuitive
- Not straightforward to make files public or to change file policies
- Google Cloud Storage has reduced our overall storage costs by helping us manage tiered storage of data
- Integrating GCS with other google storage services means we don't have to go out of Google Cloud to process our data, saving on outbound bandwidth costs
- GCS has made integration into our tools really simple, so we can automate most workflows.
- Amazon S3 (Simple Storage Service)
We selected GCS vs. others because we decided to use other Google Cloud services. Since we integrated GCS into our tools, we're still using GCS today, even though we've largely transitioned away from Google Compute services. GCS is still a very solid choice, even if your server infrastructure is not hosted by Google. Moreover, its integration with BigQuery has been a big boost for us.