10 engineers on Hacker News describe using Google Cloud Run first-hand: 3 endorse it, 2 regret it, 1 are mixed.
“That was an issue for us when we were running on Google's Cloud Run. We switched to Blaxel and it's much faster now.”
regret · production · yzhong94 · 2026-04-22 · source ↗ · wrong label?“upwards of 2 seconds in Cloud Run startup time. You pay premium for autoscaling, for keeping one instance warm at all times”
regret · production · dxbydt · 2024-07-12 · source ↗ · wrong label?“We started with cloud run but our monolith has a few worker threads that we don't want killed so we moved it to proper vms.”
mixed · production · jillesvangurp · 2022-09-23 · source ↗ · wrong label?“Cloud build deploys to cloud run. ... Worked great for us.”
endorse · production · 2 yr · lostsoul8282 · 2022-05-04 · source ↗ · wrong label?“we migrated some of our services to Cloud Run for lower costs... the migration was very easy.”
endorse · production · hn_throwaway_99 · 2021-11-20 · source ↗ · wrong label?“I have been using it for a while for smaller services that integrate with both Cloud Datastore and Cloud Pub/Sub, and I think it works really well”
endorse · production · mikkelbd · 2019-12-09 · source ↗ · wrong label?“deployed using GCP cloud run”
neutral · personal · lightning19 · 2023-03-11 · source ↗ · wrong label?“We wrote about how we migrated off Cloud Run to K8s”
neutral · production · artembugara · 2022-01-11 · source ↗ · wrong label?“I built it to deal with GCP infrastructure (private networking and Cloud Run).”
neutral · production · neomantra · 2020-11-03 · source ↗ · wrong label?“The code you see really does run in production for App Engine and Cloud Run.”
neutral · production · prattmic · 2019-12-17 · source ↗ · wrong label?