aphiria VS Spiral Framework

Aphiria: https://www.aphiria.com/

I’ve been wanting a project just like this so I can finally try Aphiria! Very well done project, definitely worth a look.

Aphiria is a fav of mine - lesser know but being a fresh take since PHP 8 it has some opportunities that older frameworks never did.

I haven't promoted it much because it's still in alpha testing, but my framework Aphiria.

Compare output from Laravel to a framework that's not bed-ridden with overuse of Reflection, like Aphiria and see the result for yourself.

One of the promising frameworks I noticed is https://www.aphiria.com/ in case someone is interested to try out something different, something that's not full of evangelists who are wolves in sheep clothing.

Those are some of the things I sought to solve with MixerAPI. This is another project which saw the same shortcomings as I did, https://www.aphiria.com/, I just didn't think it made sense to build a ground-up framework to solve the problem. Use something existing, build on top, and don't mess with existing workflows in the framework. Just augment them is how I feel about things at least.

Author of Aphiria here. The base controller just provides a few properties and helper methods. If that's too much coupling for you, it supports POPOs as controllers too.

I use them as a micro-optimization in my router. Whenever I find a potential matching route, I yield return it and check it against constraints, eg does the HTTP verb match. This way, I don't have to grab all potential route matches prior to checking constraints.

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.