Multiple choice technology architecture

When not to use hibernate?

  1. Horrible database design(i.e composite keys)

  2. application is mass operation

  3. Both of the above

  4. None of the above
Reveal answer Fill a bubble to check yourself
C Correct answer
Explanation

Hibernate may be unsuitable for applications with poorly designed databases using complex composite keys, which are difficult to map. It's also inefficient for bulk/mass operations where direct SQL or batch processing performs significantly better than ORM-based row-by-row operations.

Keep practicing — related questions