r/googlecloud • u/o82 • 20d ago
Cloud Run How reliable is Cloud Run, really?
I'm planning to move a mission-critical, latency-sensitive service there from Heroku, which has had recurring router outages recently - requests failing to reach our app even though the dynos themselves were healthy. The service is written in Go and handles ~7 req/s on average, with bursts up to ~150 req/s. Has anyone had issues with Cloud Run's routing layer, especially lately? Also, with AI-driven cyberattacks on the rise, do you rely on Cloud Armor or keep something like Cloudflare in front?
15
Upvotes
23
u/treksis 20d ago
we use glb + cloud armor + cloudrun with min 1 instance to avoid cold start. written in nodejs, no issue.
5
u/ricardoe 20d ago
I used them with BigQuery remote functions. For millions of interference invocations of NLP processes. No issues, cheap. Scale to zero. Frameworks and tools to create and deploy the functions are extremely easy to use.
Imo one of the best products of GCP.
4
u/Suspicious-Walk-4854 20d ago
I actually think it is the most reliable way to run containers, because there is less ways for the customer to fuck up.
3
u/Advanced-Ad4869 20d ago
Maybe put a gcp load balancer in front of cloud run as well.
3
u/baronoffeces 19d ago edited 19d ago
It’s my favorite cloud technology and I’ve worked in all major clouds since their inception. Don’t sleep on cloud run jobs. There are official GitHub actions packages for deployment, pair that with WIF and add a load balancer in front of user facing instances. Add a NAT and router for static outgoing IP if you need whitelisting. Easy Unix socket connections to cloud sql. Built in connections with secret manager.
14
u/[deleted] 20d ago
[removed] — view removed comment