Replies: 16 comments 12 replies
-
|
Originally posted by Chris on 2016-01-30T18:22Z Thanks, interesting article! I would like to add that this:
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks! I chose to focus on micro frameworks only, and I guess I had to make a subjective decision of what I considered a micro framework to be. The frameworks with 10-50x more stars probably didn't make the cut because they were "too big". Got any suggestions on frameworks I missed? I would not mind revising the post with new frameworks if there are some I've missed. I think that small commit activity and not having a `composer.json` file ties into each other. It means that no effort is made for keeping the framework, and in the end the applications that rely on it, up to date with bug and security fixes. And yes, people need simple frameworks for building small applications. I decided to focus this one for more experienced developers looking for a framework to build a REST API with. But Silex is a great example where you can build a minimal application with some database calls and some Twig templates. Using Composer for those small applications is for me not a stretch of what we can demand even of a junior developer :) |
Beta Was this translation helpful? Give feedback.
-
|
Originally posted by Viva on 2016-04-03T00:37:18Z Very interesting article, thank so much it helped me a lot |
Beta Was this translation helpful? Give feedback.
-
|
Originally posted by Zsolt on 2016-04-20T00:24:57Z You should also try equip framework and radar. Both are really tiny things, based ADR (Action-Domain-Responder pattern) and psr-7. |
Beta Was this translation helpful? Give feedback.
-
|
They both look really promising, I like the approach ADR takes. I will dive deeper, test them out and possibly update the post! |
Beta Was this translation helpful? Give feedback.
-
|
Originally posted by Antonis Adamakos on 2016-05-14T20:48:50Z Nice research! I would advise though anyone to use RESTLER ( https://www.luracast.com/pr... ) - it is built "exclusively" for building apis with versioning, authentication, throttling etc. The best thing is that it automatically generates a resources.json for swagger/open apis with all routes, methods, docs, parameters etc., parses your php doc blocks and have functional explorer like https://github.com/Luracast... Amazing tool, highly recommended :) |
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure if I'm stupid or not, but I can't seem to find the documentation for it :) |
Beta Was this translation helpful? Give feedback.
-
|
Originally posted by Cristian Tala on 2016-05-17T20:15:07Z I will be waiting for part 2 :). |
Beta Was this translation helpful? Give feedback.
-
|
Originally posted by kennii on 2016-05-21T02:47:44Z +1 |
Beta Was this translation helpful? Give feedback.
-
|
Originally posted by Mika Andrianarijaona on 2016-06-07T20:21:45Z Great post thanks. It was really helpfull to me as it's the firts time I will work with a php micro framework and it was difficult to me to choose one |
Beta Was this translation helpful? Give feedback.
-
|
Originally posted by TudorB on 2016-06-17T11:58:45Z Great article. I am looking forward part 2 :) |
Beta Was this translation helpful? Give feedback.
-
|
Thank you. I'll take a closer look at it! |
Beta Was this translation helpful? Give feedback.
-
|
Originally posted by Azaz Qadir on 2016-08-19T15:11:26Z Slim is great for creating Rest API and it's lightweight and easy to learn. Here is an example of how easy it is to create Rest API using Slim: https://www.cloudways.com/b... |
Beta Was this translation helpful? Give feedback.
-
|
Originally posted by Valentin on 2016-09-15T11:35:32Z Cool article! Thank you very much! I tried to find a framework myself but hardly found a half of those you listed. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! But I do not agree with you on this point. Limonade first and foremost is a "try to solve it all by itself"-framework without any external dependencies. That to me is a valid point for not going further with the framework in this post. Secondly, if the framework had external dependencies but were not updated in a year, how would you know that security and performance patches were implemented? Sure a framework can have a solid foundation and be production worthy, but it's kind of a smell to me when it hasn't been updated in over a year. |
Beta Was this translation helpful? Give feedback.
-
|
Originally posted by Maksym Minenko on 2016-09-19T06:21:40Z A very nice research indeed! Thanks a lot. |
Beta Was this translation helpful? Give feedback.
-
|
Originally posted by Leonardo Cabral on 2016-12-21T20:43:31Z Interesting article. Albeit the lack of better requirements for research methodology related with the framework performance and scalability (a simple 1000 "Hello world" on Apachebench will give enough request data to make a more feasible elimination round.) Flight - a disqualified one - for example will make 1000 requests before 500ms. And here's two of your survivors: Lumen (5.2) takes 2500ms and Slim (3.4) takes 4500ms to do the same task. I don't know you but as a enterprise/startup player it counts a lot. I understand your preference for dependencies but nowadays with Composer the microframework paradigm is to build a lean enviroment, with the best of many worlds. In general Its a good article. I'm ok with that. Happy 2017! |
Beta Was this translation helpful? Give feedback.
-
|
Performance is often something that shouldn't be considered when choosing a framework. All micro frameworks are fast to a certain extent, and with PHP7 it's even a smaller factor because of the large performance improvements that the language brings to the table. I also wrote in the article that I would not take performance into consideration for eliminating frameworks. If extreme performance is a requirement, people will probably do their own extensive research into that aspect. I hope. :) Happy 2017 to you too! |
Beta Was this translation helpful? Give feedback.
-
|
Originally posted by Tony on 2017-02-11T07:16:14Z Part 2 plz!! |
Beta Was this translation helpful? Give feedback.
-
|
I know, I know. I should really get to work on that! |
Beta Was this translation helpful? Give feedback.
-
|
Originally posted by Carlos Guzman on 2019-05-30T13:18:33Z Are you still working in the 2nd part? ;-) I really enjoyed your article and I agree with the criteria you used to choose. Though maybe your post is quite old now, it is a good guide and it really helps me to choose a framework. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Hello! Haha I'll be honest and say that it has just slipped my mind. Haven't been writing actively on the blog for quite some time. Hopefully I'll get some inspiration back soon and write the 2nd part, I'll try to respond to your comment if that happens :) Also, thank you for the kind words! |
Beta Was this translation helpful? Give feedback.
-
|
Originally posted by korneliuskristianr on 2017-03-01T07:21:12Z Hi, nice research. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. I decided not to include a benchmark and gave my reason for it, I don't think its a viable metric in most cases. If you need it as a metric there are many benchmarks out there, however a benchmark is easy for a vanilla install of a framework. But when it comes to an actual application it's virtually impossible to get a benchmark unless you do it yourself and make an appropriate comparison based on how the application is used. |
Beta Was this translation helpful? Give feedback.
-
|
Originally posted by spuy767 on 2017-05-04T23:39:54Z He decided not to include a benchmark because why bother comparing fast the speed when your arbitrary guidelines for what makes a quality framework, glueing together random bits from other frameworks, eliminated the fastest one, by a huge margin. |
Beta Was this translation helpful? Give feedback.
-
|
Originally posted by devsmt on 2017-05-05T08:41:17Z I do not agree with the no dependency stigma, as they depend on PHP, which is more than enough for the task of serving some json, and many try to be micro-frameworks, that means having a small perimeter to defend against obsolescence. |
Beta Was this translation helpful? Give feedback.
-
|
Originally posted by Ravindra Singh on 2017-08-01T11:54:47Z When you actually need APIs to be exposed, here is one another post for Lumen - http://www.tundriyal.com/wh... |
Beta Was this translation helpful? Give feedback.
-
|
It seems you are dependency dependent. :-D I don't think we need dependencies for simple stuff like microframeworks. Actually dependency-less code might be much better constructed, compact, performant and bug free. |
Beta Was this translation helpful? Give feedback.
-
php-micro-framework-for-a-restful-api-part-1/
PHP micro framework for your REST API – Part 1: Selection
https://modess.io/php-micro-framework-for-a-restful-api-part-1/
Beta Was this translation helpful? Give feedback.
All reactions