Spiral Framework VS Slim Framework

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.

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 is very lightweight and has a similar API to Express https://github.com/slimphp/Slim

Yes, I've opened a ticket with Slim. I also saw it in a non-slim file (Pimple) so I don't think it is a Slim issue.https://github.com/slimphp/Slim/issues/2160

Sounds like part of Slim's RoutingResults. Which then is pretty much:

Switched from Python to PHP and now using Slim. Very happy with the move so far.

At my day job we needed to develop an API and I've never really tried to build one using vanilla PHP, but instead used frameworks such as CodeIgniter or Slim or just a simple file that would mimic the functionality of an API but not be a proper one. Also we had a requirement that we needed to have full control over the code so we were not supposed to use any of the pre built solutions because of that requirement.