4 ms·
One thing that gets left off is the per-request lifecycle. It makes requests easy to think about, but it makes RPC/SQL connection pooling a lot harder, and that
by dehrmann 4y ago
One thing that gets left off is the per-request lifecycle. It makes requests easy to think about, but it makes RPC/SQL connection pooling a lot harder, and that's one of the first things you do when you care about performance.
- trog 4y agoCan you explain what you mean here a bit more? I worked on some large PHP sites (millions of users a month) and didn't really have any problems with these things, but maybe you're talking about a specific type of RPC?
- dehrmann 4y agoOne place I worked put all their services behind private ELB instances. They didn't use PHP, but if they did, they'd pay the cost of HTTP(S?) connection establishment for each service call because the connection couldn't be reused across multiple incoming requests. DB connections have the same issue.