Remix clone Hacker News

We dabbled with Cloud Run and Cloud Functions (which as of v2 are just a thin layer over Cloud Run anyways).

While they worked fine for HTTP workloads, we wanted to use them to consume from Pub/Sub and unfortunately the "EventArc" integrations are all HTTP-push based. This means there's no back pressure, so if you want the subscription to buffer incoming requests while your daemons work away there's no graceful way to do this. The push subscription will just ramp up attempting to DoS your Cloud Run service.

GKE is more initial overhead (helm and all that junk) but using a vanilla, horizontally scaled Kubernetes deployment with a _pull_ subscription solves this problem completely.

For us, Cloud Run is just a bit too opinionated and GKE Autopilot seems to be the sweet spot.

▲

gizzlon 5 hours ago | parent [-]

> The push subscription will just ramp up attempting to DoS your Cloud Run service

Interesting. My assumption would be that Cloud Run should quickly* spin up more containers to handle the spike and then spin them down again. So there would be no need for back pressure? Guess it depends on the scale? How big of a spike are we talking about? :)

*Let's say a few seconds

	▲	seabrookmx 2 hours ago \| parent [-]
		You typically have it configured with a cap on instances for cost reasons. Even if you don't, if you have other services (like a database) downstream, you might not want it to scale infinitely as then you're simply DoS'ing the DB instead of the Cloud Run service. Backpressure is really important for the resiliency of any distributed system, IMO.