What micro framework do you recommend?

Question

Silex

Hello!
The question is: you need a framework to expand the capabilities of the CMS, for example, the main data with which the CMS processes it well, and when expanding the functionality, I would like to create a separate page and use the framework to work without touching the main CMS (this is such a tricky ass) .
As I understand it, Slim is quite a good tool, but without ORM.
What other forks can you say/advise? It is also desirable to write what it is good for, and how it fundamentally differs from slim?
And I also wanted the framework not to impose its structure / architecture (as, for example, Yii imposes it). The ideal option would be to be able to implement one entry point (that is, one page, with a little magic in.htaccess ) and then hook any files regardless of their "geographical" location.

Answer 1

Take Symfony 3 in microkernel mode . Profit:
by default - microframework, if this is not enough - you can quickly switch to symfony full stack solution. Well, the quality of the code and so on. symphony components have no competitors (except that zend can compete).
Composer, you can take any package that implements ORM. Another good question is do you need an ORM. It is not something that should de facto be present. Let's say if you have a monga as a database, then ORM is no longer needed, since there are no links between documents (more precisely, they should not be).
This item corresponds. There is a generally accepted best-practice, but in principle it is only about general things. And the structure of your code is up to you. There are also no restrictions on the architecture of your application, symphony only provides you with adapters for the UI (HTTP, CLI, etc.), that is, the organization of the UI of the application. The application itself, at least in plain php, can simply use the infrastructure provided by the symphony.
Are you talking about autoload now or what? What files? Stop thinking in files, think in objects, namespaces, etc. And the mapping of this to files is written once in composer.json.
ps Again, a framework is just a set of tools. he does not oblige you to do anything. Symphony is one of the few frameworks that provides freedom. That is, there is a structure by default, but you can change it as you like.

Answer 2

Silex

Answer 3

Not so long ago, I also asked a similar question. I chose a microframework for work. I looked inside slim and silex, and compared to slim, silex seemed redundant to me as a microframework.
Another plus to slim for more active development than silex.

Answer 4

I prefer Slim so far. Out of the box, not only a router, but also the most necessary - the implementation of DI through Pimple, sessions, middleware, etc. Twig or Eloquant connect easily as native. Top notch documentation. I am very glad.

Answer 5

If the problem is only in the ORM, Slim easily interfaces with Eloquent. But if we take Eloquent, then it makes sense to take the framework native to it, Lumen.

Answer 6

An excellent option would be f3 framework

Answer 7

If you need minimalism and freedom of action in general, then there is a reason to try the hleb microframework . Under the link the documentation in Russian.
ps The author of the topic most likely found the answer, but nevertheless the question is quite relevant.