JSON Machine VS aphiria

To handle this problem i've used "https://github.com/halaxa/json-machine" to decrease the memory usage and "https://github.com/spatie/async" to decrease the take taken for the "update process" to complete

Under the hood, it uses JSON Machine as a lexer and parser.

Seems like the issue is still open ! https://github.com/halaxa/json-machine/issues/36

Yes. We used it heavily when processing large amounts of data from huge API responses. I like how the whole processing chain can be built on top of it, for example using nikic/iter. Generators are also the heart of a low-memory JSON parsing library halaxa/json-machine, which I maintain, and many other similar projects.

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.