[ Cloud Scheduler + PubSub + Cloud Function ] vs [ Cloud Scheduler + CloudRun Jobs ]

[s4s7]

Is the later arch better now ?
Is there a case when the former is better ?

[knet · Accepted solution]

Both ways work.

Use Cloud Run jobs if your job is long-running; Cloud Run jobs can run for up to 24 hours. Also use Cloud Run jobs if you want to parallelize your job with multiple tasks.

Use Cloud Functions if you want to take advantage of the native eventarc integration. 

In many cases, both approaches will work.

[s4s7]

I want to deploy Cloud Functions (2nd gen) from image that is customized process and hosted in an artifact registry because this image is combined with external Golang package of private repository.
I'm planning to trigger Cloud Scheduler + PubSub, but it seems that Cloud Functions (2nd gen) is not supported from image hosted in artifact registry using gcloud command.

Can I deploy Cloud Functions (2nd gen) from image that is hosted in an artifact registry ?
If not, do I have to use Cloud Run jobs ?  And will the cost change?

[knet]

If your deployment unit is a container image, Cloud Run jobs are a better fit. For pricing, the pricing calculator may be helpful: https://cloud.google.com/products/calculator