I still love PHP and JavaScript

Re:I still love PHP and JavaScript by lmm on Tuesday August 02, 2022 @11:31PM (#32327344)

> I noticed being stateless made it difficult to scale for any complex app. It’s been 7-10 years since I used it but Drupal used 60-128MB+ plus per request. As it was stateless it had to do a full bootstrap for every request coming in, set up a new database connection, module discovery etc, all which was heavy to do for every request.

It doesn't make scaling hard, it makes scaling very easy because you can just horizontally scale out as many instances as you need. The constant factor is pretty awful, but that's the tradeoff you make for statelessness.

[ Parent | on HN ]

Re:I still love PHP and JavaScript by BFLpL0QNek on Tuesday August 02, 2022 @11:52PM (#32327463)

Ok, it makes scaling technically easy with horizontal scaling for the web tier, ignoring the DB.

In practice it makes scaling hard for financial reasons if you require 128MB+ per request. A 32GB server will struggle with more than 256 concurrent requests at 128MB+ per request. A 32GB server is an extremely large server for such low request numbers.

If you can bring the memory usage down stateless works well. I use a bit of rust on aws lambda with the lowest memory settings so pay fractions of a cent and can handle more traffic than I ever need. I do set up persistent connection pools for the life of the lambda and only bootstrap once to bring down latency per-request but treat it as an ephemeral horizontal scaled service.

[ Parent | on HN ]

Re:I still love PHP and JavaScript by lmm on Tuesday August 02, 2022 @11:57PM (#32327504)

The problem there isn't scaling - it scales perfectly - the problem is low performance.

[ Parent | on HN ]