framework-x VS Slim

Have a look at Framework X (https://framework-x.org). It's barebones, but provides routing and basic request/response handling to build your own stuff upon. It's based on ReactPHP so you can use it as standalone service or use it in shared hosting with FPM, whichever suits you.

Using FrameworkX default hello world example I get 12.4K req/s on my M1. FrameworkX is using ReactPHP. Unless I'm reading activity monitor wrong it's ~10MB idle and 12,5 MB max.

There are many micro-frameworks available like Slim, Mezzio(with Swoole may be), or if you are into async then you can also try Framework X(from core maintainer of ReactPHP). This frameworks have small footprints compare to Laravel, Symfony, etc. Yes, you can't get things like authentication, routing and other out of the box but they can easily be installed and configured to be used.

I saw it was mentioned in the Framework X

As others have mentioned, in certain scenarios using a long-running application server (rather than mod_php/php-fpm) to serve requests can make sense. There are a number of extensions and libraries available that facilitate this with asynchronous code execution - Swoole has already been mentioned but you may also want to check out ReactPHP (not related to JS React, other than they stole the name) and Framework X

The Framework X is an attempt to make ReactPHP into a micro framework, but I see little mention of it.

Framework-x https://github.com/clue/framework-x

With ReactPHP, I've written a couple websocket apps. Worked pretty great for that. https://framework-x.org/ is also a pretty good place to get started for a simple HTTP microservice-type app.

Yeah ReactPHP will do this. I have an event source server running and it was pretty easy (once you get the hang of using react). I had an nginx proxy in front of it for tls. Have a look at https://framework-x.org too

Currently Laravel is the "go to" for new PHP applications to mostly developers today, if not, plain PHP, Slim, Symfony and other frameworks does the job, but for Wordpress, custom PHP boilerplates or/and outdated PHP patterns (aka, single ton) is what we have for work in mostly cases, if not, hacky ways to integrate frameworks as Laravel itself or parts of it to leverage a better code structure.

Slim is a micro PHP framework used for web development with 11.7k stars and 2k forks on GitHub. It has a simple and intuitive API development process. It is a micro-framework, meaning you only get a minimum of support for HTTP requests and forwarding requests to appropriate controllers. So the question is, why should you choose a micro-framework? Because it offers you flexibility and high extensibility.

Slim 4, a minimalistic PHP micro-framework, offers middleware support to easily add CORS headers. Middleware in Slim acts like a series of layers through which your app sends a request. One such layer can be responsible for adding CORS headers.

SlimPHP 3 Skeleton app shows this as well: https://github.com/slimphp/Slim-Skeleton/blob/3.1.8/public/index.php

How hard did you look? There are plenty out there. FastRoute, Phroute, based on FastRoute, with basic middleware, League/Route - routing with middleware, using FastRoute, PSR 7 & 15, Slim Framework, at it's core, it like League/Route, etc. None of these require a full framework to use.

You can have the container call in a config folder with a file called dependencies or how ever you want. A few existing examples of this is here - Slim calls this app/dependencies in this skeleton project and Odan's Skeleton has this as config/container in their project.

Maybe use this if you don't like to dive into bigger frameworks: https://www.slimframework.com/