Hi,
One of the IT futur, is Container (docker like and kubernetes like) and Single Page Application...
On the other language the tendancy is to simplify the start time and single start of the application (only one process start the application runc) and simplify configuration; and simplify logging (all on the stdout/err of the container) to work better in this type of infrastructure.
On java side for exemple the tendency is bootstraping the servelet engine (of tomcat or jetty) in standalone process... no complex configuration...
With PHP you must use apache+mod_php, or nginx + php-fpm in the same container.... they are very comlex to configure (you must configure php, apache/nginx, some time +htaccess)... to package...
The ideal way is to embed the http server in php to be abel to start directly the php from php cli (php -S localhost:8000) ...
The actual http server implementation are minimal... and not very performante (lake of event/thread/process manager, and lake of http2 support)...
Swoole is perfect exemple of this tendency... but need some addition to permit standard php application like wordpress to work directly on the type of packaging....
And also abscence of concurrency (coroutine or thread, native simple multi process pool like process manager in swoole) are a real obstacle to the progression of php...
Swoole add this with the event model (not real threading, user mode thread)... but real thread while be a must...
Unit project from nginx are good exemple of that and good exemple of these tendency...
Mathieu
Daniel Martín Spiridione , 16/09/2019 20:56:
The lack of concurrent PHP features in 2019 is, in my opinion, sufficient
reason not to use it for CLI projects.
Some companies do not welcome installing extensions like Swoole, the
language should have native concurrent features.
Daniel
El dom., 15 sept. 2019 a las 0:33, Mike Schinkel (<mikeschinkel@gmail.com>)
escribió:
