ORM or NotORM? What is better to choose?

Question

PHP

I am looking for a wrapper for mysql (there is a possibility that there will be another base) convenient, I found the NotORM library htmlhook.ru/vzaimodejstviya-s-notorm.html but they say about it that it is not suitable for large projects, I saw Idiorm idiormru.readthedocs.org/ru /latest/index.html but somehow I didn't like it... Can anyone give me some advice? Or am I paranoid in vain and it is quite normal to use NotORM?

Answer 1

large projects are different. If you have complex business logic, then it is better to take Doctrine2. If there are a lot of read requests and complex selections, and at the same time the business logic is primitive (crud) - you can just take doctrine / dbal and not worry, map the data directly to some transfer objects. In this vein, all sorts of under-orms fit well, as they simplify mapping when recording.
In the PHP world, there is only one normal ORM - the doctrine (sadly, but the situation is similar in other languages, python - only SQLAlchemy, java - only hibernate in fact. This is due to the fact that the correct ORM with a date mapper is sooo difficult) . Everything else is so ... not serious. Just simplifiers that allow you to work with tables. On really large projects that bearded guys write, they take Active Record and put it in a separate layer so that even the application does not touch, they will use this thing stupidly as a DTO between the application and the database. Actually, many use the doctrine in this way, but these are already details.
ps in the readme the Pareto law is not correctly interpreted and not quite correct conclusions are drawn.

Answer 2

Doctrine2

Answer 3

Doctrine or eloquent, read about both, choose the one that best suits your case.