> This is very interesting, I didn't know this. This is a perfect fit for PHP, as it was always designed with this model in mind, and the programmers that use PHP are already used to this way of developing, as that's exactly how php-fpm and mod_php already work and always have.

Yes, but now you have to pay for every requests made to your app instead of just paying $4 a month for a shared Apache server and I also have to architecture my PHP app in a rigid way to fit whatever "serverless" execution model the SAAS runs with.

Which may be much cheaper than $4/month if you have very low traffic numbers.

> Which may be much cheaper than $4/month if you have very low traffic numbers.

A big IF. My $4/month stay $4/month without the added complexity of "serverless" deployment nor every stupid constraints this business model imposes. If serverless actually didn't make money, this business model wouldn't exist or wouldn't be pushed, mainly by Amazon employees here.

It's php, so your architecture by nature is already serverless unless you are using some newer plugin like swoole.

For most projects, that $4 server is great and what I would prefer. But where serverless can excel is an application that has very spikey usage.

If your $4 server gets hit with spikes of usage that would require a $500 server for an hour once or twice a month, you might be better off with serverless, rather than paying $500/month to have a server that big all the time.

The traffic costs of a $500 server vs the price of ondemand pricing for an hour or two would still be in favour of the $500 dollar server.

why are we even talking about a $500 php server, that is like the 0.01% of websites, You either need really specialized requirements or to be in the top 1,000 websites to need anything near what you can get for $500/month.

That was an arbitrary number, but I don't think that is true. It doesn't take much functionality before you will start needing the power of a server in the $500 range. Many apps today do a lot more than serve up static requests. I run a php server with just a few thousand daily active users and we need a $250/mo server.

You have your app, and database, and then your logging, tracing, and tracking stack and It all starts adding up pretty quickly.

A fixed cost of $4 dollars that can host hundreds of websites or a variable pricing model where any traffic level would end up costing you more with no ceiling.

Choosing serverless would be a bad game theory strategy choice.

For example: https://bref.sh/