souin VS RoadRunner

HTTP plugin now support RFC 7234 caching options

It's always been blisteringly fast when we've used it, and I like the power of the configuration (it has its quirks but so do most powerful systems). But the overhead of setting it up and maintaining it due to having to handle TLS termination separately puts me off using it when other software is 'good enough'. If Varnish Enterprise was cheaper I would have bought it, but at their enterprise prices no way.

I'm keeping a watching brief on https://github.com/darkweak/souin and its Caddy integration to see if that can step up and replace Varnish for short-lived dynamic caching of web applications. Though I've lost track of its current status.

Centminmod (need lots of tweaks) or OpenLiteSpeed are consider more performant than default Nginx and Caddy, but I wish if someone can prove there is a better one out there or I just saw Souin HTTP cache (https://github.com/darkweak/souin) when I was reading Echo web framework for Go. Yet to experiment if there is a benefits unless it's insignificant.

FrankenPHP

why link to the old URL when linking to its redirected one is less confusing?

https://github.com/roadrunner-server/roadrunner#readme (MIT)

Don't follow any advice to use Apache as a reverse proxy, or bundle php with a classic web server.

There are real application servers using an event loop by now, most notably Roadrunner (https://roadrunner.dev), FrankenPHP (https://frankenphp.dev), Laravel Octane (https://laravel.com/docs/10.x/octane#introduction), Swoole Bridge for Symfony (https://github.com/insidestyles/swoole-bridge-bundle).

In general, you can do a lot with OpenSwoole or Roadrunner. They are vastly superior (in a container scenario) to any other suggestion in this thread!

https://roadrunner.dev which golang php application server which can replace nginx +php fpm has a module for running golang via php using sockets.

You could also use something like EventMachine (In ruby), Twisted (Python), Node (JS) or ReactPHP (for PHP) that will use the language and turn it into a web application server, and then you'll have only one long running process that handle all your requests with shared memory. You could even use something more fancy like RoadRunner in the case of PHP.

Have you considered optimizing the Laravel app? I love Go, but full rewrite for such low rate sounds overkill. Have you looked at the RoadRunner PHP application sample, for example?

Has state resetter for long-running workers serving multiple requests such as RoadRunner or Swoole.