Cloudflare Workers vs. Google Cloud Functions

Good: really best in breed for lambda on the edge. it's much easier to make complex redirects decisions in JS rather than using rewrite rule syntax Good: wrangler CLI for local development Bad: no built-in retentions of logs and it's still hard to troubleshoot issues on the edge

Incentivized

Google Cloud Platform Cloud functions are an excellent way to start a serverless journey in GCP, however, using Cloud Run may be the better solution. For users not acquainted with Docker & Linux, I would definitely recommend Google Cloud Functions, however, for more experienced users, Cloud Run may be better suited.

Incentivized

• Needing a zip file is problematic (when wanting to automate deployment for example).
• Requires another solution to execute automatically (ex. cloud scheduler).

Incentivized

Overall Google Cloud Functions is losing a lot of benefits to other GCP services, making it less attractive to users. A simple example would be the need to zip application files and push them to Google Storage which makes it a bit complicated to automate via a CI/CD pipeline. Another "similar" solution would be using Cloud Run although the need for a docker image is there, with the recent evolutions to Cloud Run (ability to downscale to 0) it makes a lot more interesting.

Incentivized

Documentation is provided and clear for this service. Although GCP support is included in the current contract we didn't get to use it since the process is pretty straightforward.

Incentivized

• Using it for FinOps, we cut the bill in 2 for certain services (out of production).

Incentivized