SQL vs ORM for big base?

Question

MySQL

there are many many-to-many objects + 5-6 entities associated with them.
1) it is difficult for me
to use orm (somehow easier to do sql)
2) not all fields need to be taken
3) the base will be large 100k-1m lines of the main object, and 5-6 times more than other types of tags.
In general, I'm afraid that the orm will work for a long time. +I don't always need to fully link an object with 5-6 entities. Sometimes you only need the main + 1 related entity. (for catalog)

Answer 1

In general, I'm afraid that the orm will work for a long time.

coding is generally scary, because no one is afraid and does load tests
PS: the database is not large, but mediocre

Answer 2

ORM will be much simpler and more reliable in the long run.

Answer 3

it is difficult to use orm (somehow simpler to do sql)

you yourself answered your own question, just highlight it in some separate DAO to reduce cohesion and increase maintainability.

Answer 4

Depends on a number of circumstances. Usually, the ORM, on the contrary, turns out to be more nimble if the project has work for the Identity Map . A partial answer to this question can be found in this Storm ORM article .