Hello everyone, I recently made API performance optimization experiments when a way is to use a laravel fastcgi TSR, replace the php-fpm. According to the results of the current test, you can get great performance, about 50 + X.
Currently only used in the stateless interface calls the scene, there are still shortcomings and deficiencies, hoping to get everyone's views.
Thank you for your reply.
That meant that at present only suitable for some API, like json api, there is no cookies, no sessions.
The main reason is:
Run the command line mode, session, cookie, etc. are not available, Http middleware is also unavailable.
No complete implementation fastcgi protocol, file upload is unavailable.
Since the TSR, laravel some originally in the request shared instance, will become shared between requests, like 'Auth', 'Session', which will bring bug.
In fact, in order to solve the above problem, In laravel I do a lot of changes, but there are still some problems. For purposes of discussion simple, I just consider optimizing the API without cookies.
Scene I actually used some running laravel online application, some data need to be open to other applications by way of some APIs, and a relatively high performance requirements.
If an application is designed to start a pure API way, I think most scenarios lumen performance should be sufficient.
By avoiding every request to initialize the framework of resources, based on laravel optimization or optimization based on lumen, there is not much difference.