9 engineers on Hacker News describe using Google Cloud Storage first-hand: 3 endorse it, 0 regret it, 1 are mixed.
“We didn't want to split the origin and CDN, so we switched to Google storage. Vastly more expensive though.”
mixed · production · gazby · 2021-09-16 · source ↗ · wrong label?“We switched to GCS for our Maven artifacts and the problem went away.”
endorse · production · HiJon89 · 2020-12-02 · source ↗ · wrong label?“I used Google Cloud Functions + Google Cloud Storage to deploy a single function app. ... am very happy with it thus far.”
endorse · production · leesalminen · 2018-05-04 · source ↗ · wrong label?“gcs is way more responsive than S3. also, was fairly painless to migrate our S3 buckets to GCS”
endorse · production · 1 yr · jhgg · 2016-02-24 · source ↗ · wrong label?“At this point, we pay for some Google buckets and not much else in gcloud.”
neutral · production · jillesvangurp · 2026-09-08 · source ↗ · wrong label?“scriptable custom dashboards running on top of BigQuery data pre-aggregated and extracted to parquet on GCS.”
neutral · production · staticautomatic · 2026-08-17 · source ↗ · wrong label?“I opted for stashing and archiving into GCS / S3 directly”
neutral · production · awill88 · 2021-12-08 · source ↗ · wrong label?“I implemented an abstraction (similar to go-cloud's) between S3 and GCS because of that”
neutral · production · fishywang · 2018-07-24 · source ↗ · wrong label?“nsq-to-file rotates line-delimited json hourly which is gzipped and uploaded to gcs for archival.”
neutral · production · mattbillenstein · 2017-10-04 · source ↗ · wrong label?