Slim VS Spiral Framework

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/

Go for Slim: https://www.slimframework.com/

From the same developers :

PHP framework : https://spiral.dev/

ORM library : https://cycle-orm.dev/

This SDK server is already available for RoadRunner 2.0+ and Spiral Framework users.

✅ Spiral (Twig, Blade, Latte, Plates, Smarty, Handlebars, Mustache, Spiral View)

To give you some hint, you mention few of our instruments - RoadRunner, Cycle ORM. Accidentally, theese instruments are also part of our main battle framework - Spiral (https://github.com/spiral/framework), which we use for all of our commercial projects for over 12 years so far.

Check https://github.com/spiral/framework - it would satisfy your perf requirements (roadrunner under the hood). We pushed it up to 250k on synthetic hello world, but in real world 20k are achievable without much hassle.

Yes, you are responsible for cleaning the memory after yourself. Most of modern frameworks can do it for you since they can control the state using DI. If you are looking for a more friendly way to manage memory take a look at https://github.com/spiral/framework It is Symfony like framework developed specifically for resident memory applications.