aphiria VS Workerman

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.

I remember a consulting gig where they were pushing 50k requests per second with PHP in a 2018 laptop by using this framework https://github.com/walkor/workerman

In a real application, with database connection pooling and auth sessions, it went down to 15k requests/s.

And that was PHP7. PHP8 introduced JIT so it's probably significantly faster these days and hopefully fully typed.

The code above is an example of creating a websocket server from the usage example on the workerman/workerman page on github.

Workerman

That's cute. I managed to get 100k requests per second on a single i7 CPU this week using standard blocking code with Workerman. Zero added cognitive load. It also does DB pooling, workers, sockets and consumes relatively lower memory than other solutions.