3 ms·
I’m wondering. I also have a new project to work to, and I want to try laravel, as I am not using frameworks generally, despite some Magento work. I played wi
by JeanMarcS 9y ago
I’m wondering.
I also have a new project to work to, and I want to try laravel, as I am not using frameworks generally, despite some Magento work.
I played with VueJS and it looks like the good combo to start with.
And then I found this [0], benchmarking PHP frameworks. Of course we can’t tell (or I haven’t found) if the tests were in production mode, and if it’s relevant.
Do you have any experience with this ? Because in my project, the routing aside, it’s just a CRUD app.
Thanks if you can answer.
[0] https://medium.com/@asked_io/php-mvc-framework-showdown-7-1-performance-2da52ac9fcba https://medium.com/@asked_io/php-mvc-framework-showdown-7-1-...
- kyriakos 9y agoCRUD is what php does best. Framework overhead is not significant part of the request time so unless you're serving millions of requests it doesn't really add up compared to i/o and dB. So I think benchmarking is meaningless.
- JeanMarcS 9y agoThanks
- jjeaff 9y agoEven for simple CRUD, I would use laravel. And if it really is simple, use Laravel's Lumen, which is a streamlined version of the framework specifically for API development. I used to worry about overhead. I stuck with codeigniter for that reason. But in reality, the difference in overhead is indistinguishable even at large scale. Save yourself developer time and throw a few extra vCPUs at your project. CPUs are WAY cheaper than developer time (even if it's your own unpaid dev time).