60 minutes for HTTP functions.
10 minutes for event-driven functions.
60 minutes for HTTP functions.
10 minutes for event-driven functions.
Not sure why you would need 60 minutes for HTTP invoked functions, that alone should be a signal to offload it to another queue or asynchronous process.
I've used GCP / AppEngine for about a decade now. Built one biz that did $80m gross in its first year. Never even a small threat of being shut down. Recently had a billing issue with GCP and after explaining the problem, they credited me far more than I was even asking for.
I currently have 20k+ servers hitting Cloud Functions (golang) and Cloud SQL 24/7, which is a constant 50 requests/sec... costing me about $100 a month total. It was easy to set up, documentation is well written with clear examples, deployments are all through CI on Github. It just works.
Sorry, but I'm a fan.
To answer your question... https://cloud.google.com/tasks/docs/creating-http-target-tas...
Like I said we did it this way to avoid adding a proper queue and worker pool to this app so not recommended for heavy traffic but it works
Disclaimer I work for Google on Cloud Run.
Yet at the same time, HN loves to hate on GCP. Keep up the good work @yegle.