It is a factor when deploying orchestrated containers. In k8s for example, it's terribly in efficient to have nginx + php as separate containers with access to the same files. The request path goes like: external load balancer -> ingress controller -> local nginx -> fpm. There's an extra webserver in front which none of the other platforms need which only adds to latency.
The result is that on k8s, node + a fast router like fastify is roughly 3x times faster than your basic php rest api with Symfony. Although, if you switch to php + roadrunner in the same containerized context, php and roadrunner is roughly 2x faster.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It is a factor when deploying orchestrated containers. In k8s for example, it's terribly in efficient to have nginx + php as separate containers with access to the same files. The request path goes like: external load balancer -> ingress controller -> local nginx -> fpm. There's an extra webserver in front which none of the other platforms need which only adds to latency.
The result is that on k8s, node + a fast router like fastify is roughly 3x times faster than your basic php rest api with Symfony. Although, if you switch to php + roadrunner in the same containerized context, php and roadrunner is roughly 2x faster.