Simplifying the project stack?

Question

symfony

there is a web project that reads / writes data from three databases (both have rest)
1. Elasticsearch databases (read only, content is stored)
2. SQL databases (recording / reading orders and personal account)
3. redis (reading / writing cache ES of one request, and user session cache)
architecture SSR
What is the minimum framework you can advise for this project, orm is not used, data is all read and written by http requests. The web part is just a data mart that external users spin and the maximum they can do is record the order and personal data. The framework only needs to read data from rest Elasticsearch, read/write to SQL via rest, and render pages on the ssr server side.

Answer 1

Well, if he still needs to render pages, then either nestjs or loopback

Answer 2

To work with Elasticsearch, ruflin/elastica works very well , although there are also more low-level official bindings: elasticsearch/elasticsearch To work with Redis, predis/predis
is most often used , but the situation with it is now incomprehensible due to the fact that the author has not maintains the library and currently has issues with PHP7.3+. There is a fork that fixes this problem, but most of the libraries are tied to predis, so how the situation will resolve further is not very clear yet. HTTP requests are now usually handled using guzzlehttp/guzzle , although there are other good options.
To work with SQL, there are many libraries of varying degrees of development and popularity. If you want plain sql, then you can look at doctrine/dbal , it is very developed and stable. Any modern framework can tie all this together, personally I would look towards Symfony (it is quite possible to make a micro framework from the
4th version , which is why the development of Silex was stopped ), but there are also real microframeworks, for example, slim / slim is very popular

Answer 3

The framework only needs to read data from rest Elasticsearch, read/write SQL via rest, and render pages on the ssr server side.

You don't need a framework.
Choosing a tool because it is fashionable is not the right approach.
Dependence on the developer will not go anywhere, the framework gives only tools for structuring, how to distribute them depends only on the developer. Even in the MVC framework, MVC is violated very often, and this is just a data separation scheme, everything is more complicated with the structure.
A framework-oriented developer is something terrible, everyone, of course, knows some tools better than others, but a focused one is more about someone who has mastered only a hammer, and now everything is nails for him. Therefore, if not a specialist, but a framework, is involved in design and architecture, then many problems await you in the future, because the tool, in principle, cannot do this.