Is this really such a big niche? It's weird to me to you'd want to use PHP for something like this (and I love PHP, it just doesn't strike me as the best tool for serverless).
Is this really such a big niche? It's weird to me to you'd want to use PHP for something like this (and I love PHP, it just doesn't strike me as the best tool for serverless).
Unlike Node, Python, Java, etc. that start a long-lived server, each request is handled by PHP in a separate process.
That's what makes it really to use with serverless (and lift-and-shift, like what Treezor did).
Comparing Bref (https://bref.sh/docs#maturity-matrix) which inherits Lambda's 200ms+ cold starts vs Cloudflare's 5ms (https://blog.cloudflare.com/eliminating-cold-starts-with-clo...), for example, is a pretty big difference.
But I guess if performance isn't a critical use (or you just have so many invocations all the time in every data center that cold start isn't an issue), it's nice to be able to ~port~ copy and paste over your existing PHP code.
For context, 13B is like roughly a <strike>$2000</strike> (edit: more like $4000, sorry) spend on Cloudflare Workers, similar cost (harder to calculate but ballpark similar) on Lambda. That could be a single company spending the bulk of that.
(Further edit: Lambda pricing is way off too. See reply below.)
How come Lambda is so expensive for you?
At 13000M invocations/mo, that's $2600 in requests. Is it the GB-seconds duration charge that get you?
60'000'000 requests
1536MB RAM
300ms response avg
(calculation includes free tier):
Request costs: $11.80/month
Execution costs: $443.42/month
Total AWS Lambda costs: $455.22/month