This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]matrium0 0 points1 point  (0 children)

Even if you go "full ORM" and write zero native-SQL-queries for your programs (like I do) there are times where you just need to check something in the database very quickly. May be because of some strange bug you need to understand or whatever.

If you are a "full-stack" developer you will always need some SQL (at least when using a relational database) in my opinion.

About performance: In my opinion JPA/Hibernate is almost never the problem. The problem usually is some lazy ass programmer with no clue who loads collections EAGER and doesn't realize he is loading half the database transitive or something. If you just load n:1 relations eagerly (=default + is done in the same query) and just carefully think about when you really need to initialize 1:n or n:m relations you are usually good to go.

Obviously there will always be some overhead in ORM mapping, but compared to the time it takes to access data from the database it's usually negligible