Should the route be placed in the web or in the api routes because the middlewares are not the same?

[macropay-solutions]

While Benchmarking our Maravel and Maravelith php alternatives to Lumen and Laravel, we noticed that Maravelith and Laravel can double their RPS when optimized (cached config, routes etc.) from ~280-290 to over 550 rps just by removing the middlewares from the web routes.

This project is meant to measure the boot time but this scenario shows that middlewares are braking the execution not the application boot.

So, the question is, should this Hello World be measured in web (session, cookies etc.) environment or in api environment?
@myaaghubi @joanhey

[macropay-solutions]

Note than Laravel >=11 comes with api routes disabled by default.

[marius-ciclistu]

The difference between api and web is significant. Comparing lumen api vs laravel web is not fair.
Analog for any PHP framework.

The web middlewares are an important overhead that does not matter in boot time and response time.

Here is another bench just with api vs web in laravel and maravelith: