3 ms·
GCP Cloud Run with a schedule set to call the HTTP endpoint once an hour. Cloud Run will run any docker image, and give it a HTTPS URL. Scales to zero, allows
by emadda 4y ago
GCP Cloud Run with a schedule set to call the HTTP endpoint once an hour.
Cloud Run will run any docker image, and give it a HTTPS URL. Scales to zero, allows running in the background for up to an hour.
The benefit over FAAS is that you can run anything you want in the container, including multiple processes.
- lysecret 4y agoAlso much prefer cloud schedule over AWS version.
- leoff 4y agoI've just created a similar setup last week: 1. Cloud function, uses Puppeteer 2. Cloud scheduler for triggering cloud function 3. Cloud storage for data persistence Costs around 1 Euro a month, I had a similar setup for free in Heroku before.
- robszumski 4y agoI love Cloud Run, but can they please tie these two things together for me? It's a radio button that says "On schedule" and an input for the cron syntax.
- thraxil 4y agoIf you fit within the language/runtime restrictions, Cloud Functions and App Engine also both can be invoked with the same scheduler setup. We use Cloud Functions for monitoring all the time (schedule to call a function once per minute or so that scrapes some metrics from a third party API and pushes to a Prometheus gateway). Costs us something like $0.12/month and has been extremely reliable. We also run apps on App Engine when we can and there all you need to do is add a `cron.yaml` and you can invoke endpoints there easily and practically for free.