3 ms·

Anyone can do "concurrency" by starting from scratch with a fresh process each time. That isn't "having a concurrency story" it's rather the opposite I think. I

• stevewatson301 4y ago
  PHPs model would be okay if they used green threads/goroutines. That way, you can have a far larger number of workers, as most of them are blocked on database connections or HTTP requests to other services.
  • heurisko 4y ago
    PHP's model is different, not a mistake. It has proved successful so far. The shared-nothing, short-lived process avoids classes of issues such as with slow memory leaks, accidentally blocking event loops, and shared memory threading issues. Most PHP sites will utilise php-fpm, so it isn't really true that each request will spawn another PHP process. The language historically hasn't been that great, but its shared-nothing architecture has always been the good part.
• weatherlite 4y ago
  On the other hand its simple and works for many many people and apps. I wouldn't just discount it. The fact that "Anyone can do" it is a pro.