You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There have been lately a couple of reports of hard to fix low-level issues that can only be reproduced with openswoole.
Additionally, roadrunner is easier to install and manage in general, while the performance is basically the same, so it probably makes sense to do the transition and recommend using roadrunner.
The list of reasons includes, but it's not limited to:
Less convenient to install. Roadrunner can be installed "by Shlink".
Integration is more complex in general. A dedicated library is required (mezzio/mezzio-swoole), while roadrunner natively supports PSR-7 and a simple script does the job.
It's true that openswoole 22 supports PSR-7 too, but it has two problems: 1) While older versions are supported, there's no way to "just" switch to this approach. 2) I did a POC and could not get it working.
Performance is almost the same as openswoole (although more benchmarks are still needed).
The only considerations are:
Roadrunner logs are not exactly the same as the ones generated by mezzio/mezzio-swoole when using openswoole. It would be good to get as close as possible.
The main missing feature is the request ID, but it doesn't seem to be supported by roadrunner.
It is possible to provide openswoole config via env vars, which is ignored by roadrunner. Would be good to see if something similar is possible with roadrunner. To be investigated in future if demanded.
The docker image is currently published with two flavors. No suffix uses openswoole, and -roadunner suffix uses roadrunner.
In order to keep BC, publish three versions from now on: No suffix has the "default" runtime, whichever it is. Then one suffixed tag is published for every specific runtime, warrantying that runtime will be used even if default one changes over time.
The text was updated successfully, but these errors were encountered:
There have been lately a couple of reports of hard to fix low-level issues that can only be reproduced with openswoole.
Additionally, roadrunner is easier to install and manage in general, while the performance is basically the same, so it probably makes sense to do the transition and recommend using roadrunner.
The list of reasons includes, but it's not limited to:
The only considerations are:
It is possible to provide openswoole config via env vars, which is ignored by roadrunner. Would be good to see if something similar is possible with roadrunner.To be investigated in future if demanded.-roadunner
suffix uses roadrunner.The text was updated successfully, but these errors were encountered: