[meta] Make Drupal compatible with persistent app servers like ReactPHP, PHP-PM, PHPFastCGI, FrankenPHP, Swoole

There is an integration of Laravel Octane with FrankenPHP.
The results show that FrankenPHP is even quicker than Swoole.

https://blog.laravel.com/octane-frankenphp

FrankenPHP has a known issue about crashes when certain PHP constructs and functions are used within Fibers. I think it would be great to open a separate Drupal core issue that tries to find out if Drupal makes any of those calls within fibers. That could happen independently of this issue, which affects all persistent app servers, not just FrankenPHP. However, I don't have any ideas at the moment on what the best way would be to determine if Drupal triggers any of those FrankenPHP crashes without first solving this issue.

The only child issue and possible way forward is ✨ Use symfony/runtime for less bespoke bootstrap/compatibility with varied runtime environments Active

FrankenPHP official support in Drupal would be awesome, I'll give it a try if I find the time !

Nice write-up and tool to catch shared data https://dev.to/sergiid/getting-symfony-app-ready-for-swoole-roadrunner-a...

Re: #87, that is the issue we need to untangle at #3324241: Provide DIC-friendly, concurrency-safe alternative(s) to `drupal_static()` → . Should we change the parent of that issue to this one? Runtime is one of a few items that need to be addressed. The reference to the ResetInterface in Symfony 7 is excellent and provides us a model to build on instead of rolling our own.

For searchability

Let's add Swoole then also for searchability.

Added an issue to add a Caddyfile to core, used by frankenphp (which is based on caddy), with an rough implementation of the early hints feature that's available thanks to frankenphp (and symfony). We can start by using that in the non-worker mode and once all the issues from this meta are dealt with we can turn on the worker mode of frankenphp to make everything faster without changing much on the infra side.

I don't think enough people are aware of the massive performance boost effect this feature can Drupal!! otherwise it would be done long time ago

There's fresh approach to add the Symfony Runtime's frontend in ✨ CLI entry point in Drupal Core (Dex) Needs review

Re @sinasalek there's long way to clean all static variables before Drupal sites can benefit of pre-bootstrapped kernel

Thanks for the update @standpoint
There has been many attempts do this over the years but non had enough strength to pull through.
I'm thinking about creating a new initiative, raise awareness and gather enough support to tackle this complicated issue.

Symfony supports runtime, which might be a good start. It's suppose to support different runtimes for running symfony
https://symfony.com/doc/current/components/runtime.html

As for static variables. it is possible to workaround it. There are multiple ways to address it. it appears that Swoole can handle it using co-routines
https://www.perplexity.ai/search/I-want-to-EZuTp_oHSmiElEHFpfToow