ORM vs Query Builder vs Native driver

user_10269060 0
Viewed 606

I am really confused because I have heard a lot about ORM, I guess the best practise is to used ORM to not write SQL queries.

I tried Django ORM, Laravel ORM, Hibernate and they take much longer time to return the data.

For example: I code a script to insert a dataset using native queries and Django ORM, Django takes 4 minutes and my script take 1 minutes, more or less.

I think the response time is the more important thing when you code an api.

So, is not a better option to use the query builder?

query-builder orm
1 Answers

ORM is basically a way to introduce concepts of domain and type safety into work with databases. When you can have classes and properties with types, it's more easier to write logically structured and type safe code, also reuse existing functionality. Following these benefits, the main advantage of ORM is safety and clearness. Also, ORM could be a way to introduce an abstraction layer, allowing semi-painless migration from one database to another as details of interaction are hidden inside ORM engine.

For small projects without many developers working on or for application with short lifetime, it's obviously not a necessity, and introduction of an ORM can be considered as a disadvantage.

Addressing your example with slow insertion of data and accusation of ORM, it can be said that probably you aren't using ORM correctly or you are using it not in the most optimized for the task way. For example, your script can use no transactions at all or probably use less restrictive isolation level whereas ORM can target safety over speed, creating a transaction on each insert or utilizing more restrictive isolation level.

user_21520610
Related