Maravelith API vs WEB RPS increased by 90% and memory decreased by 3% after I converted View, Cookie and Session service providers into deferred providers in version 10.64.14 of Maravel-Framework that also brought full view support to Maravel as well, including view:cache, session (CSRF), cookie and FormRequest.
As mentioned here, it is not fair to compare Maravelith WEB with Maravel API or Laravel WEB with Lumen API routes. Analog for any php micro-framework that is compared with full framework. Comparisons should be done on API vs API because the session middleware brings an important slow down on the web routes.
@marius_ciclistu hey, your macropay-solutions repos seem to be very useful, will take a look!
GPT-4o
This is truely cool! As someone who's been wanting a solid Lumen alternative, the fact that Maravel offers templates (Maravel *and* Maravelith?!) is a total game changer. Saves a ton of upfront work, right? Kinda genius imo. How's the community support looking?
Sellinger AI
Hey,
Congrats on going live, upvoted, we’re live today as well and your perspective would help.
Nice launch! Dropped you an upvote 👍 We’re also up today, your feedback would mean a lot.
We just launched the official website https://maravel-framework.com/