octane VS frankenphp

The web server my app uses is not too slow, after load testing with wrk **the RPS on a single 512MB dyno with database queries is 474 requests per second. While running this test, I could still use the app but the response times were higher (400ms-800ms instead of the usual <110ms).

Re Octane, yes it's WIP https://github.com/laravel/octane/pull/764 there were some performance issues found which don't seem to affect non-Laravel apps which is weird/confusing so that's still being looked into. But, soon.

I was hoping that Octane would add support, but the person running the Octane github is one of those people who quickly closes every issue that isn't considered a bug. So no traction is ever built up like on https://github.com/laravel/octane/issues/110 .

Laravel was recently updated to support serverless deployments, alongside the launch of Vapor[1].

Octane[2] is also very exciting. Using Swoole[3] (or another similar driver), Laravel applications can be run entirely in-memory. Early benchmarks showed Octane increased concurrent requests from ~500/sec. to ~6,000/sec.

[1] https://vapor.laravel.com/

[2] https://github.com/laravel/octane

[3] https://openswoole.com/

Another feature of Laravel you might want to take a look at, just became available since the last Laracon. It's called Octane, and it's currently in a beta version, but its potential for optimization, compared to a normal Laravel app, is pretty great. Note that it requires PHP 8.0.

Taylor Otwell already showed a glimpse of Laravel's latest open-source package, Octane, during his Laracon Online talk - but today, the new package is available on GitHub for everyone to beta test.

New 0.7.3 release includes a rule that can check Laravel Octane compatibility of your application. It basically automates the things mentioned in the official docs. You can give it a try now! And let me know what do you think!

Recently the Laravel Octane package was released. It was created to make Laravel with Swoole and RoadRunner more friendly. We are using RoadRunner instead of php-fpm in dev.family for some time now, and we decided to share our experience and to reveal what advantages it has.

Uses the new FrankenPHP server to add SSL support to your local environment

Depending on the application you can already do this. For example: https://frankenphp.dev/

File size of binaries is almost never a relevant factor. Your server running your code is probably not so constrained on disk space that it would matter. It's not like it's gigabytes, it's only ~110MB. See the assets on the latest release: https://github.com/dunglas/frankenphp/releases/tag/v1.0.0

A new player is entering the game: FrankenPHP. This is a new application server which can be used instead of Apache or nginx.

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!

And up-and-comer is https://frankenphp.dev/ which invokes PHP directly from a Go server (as a plugin for Caddy) using CGO. Not quite stable yet, but it's looking good and lots of progress has been made. Disclosure: I work on Caddy :)