Hibernate: memory issues? limitations?

Question

Im works with Hibernate 3.6, and until today I could not find any flaws in its use. But today someone told me that applications using Hibernate will get memory problems when the project gets bigger. This will happen because there will be many objects (hibernate-pojo-objects) that will need to be created and saved, compared to an application that does not use sleep mode.

it is right? and are there any other drawbacks to using sleep mode? some also told me that working with objects gets confusing when the database is really big due to all the dependencies between the objects, but I cannot imagine it. Does anyone have any experience with this?

thank: -)

Answer 1

Some of them:

• Few or no opportunities for remote access and distribution.
• Mapping schemes can be tedious, and O / R mapping has its tricks, such as using lazy initialization, impatient loading, etc. What works for one may not work for the other.
• Limited clustering options.
• Large datasets can still cause memory problems.
• Security support only at the database level and lack of role-based security support without adding APIs such as Aspect Oriented Programming, etc.

Some other people also find that there are disadvantages for Hibernate.

Answer 2

Whenever you add an abstraction layer, it has to do extra work and use extra memory for this. If it uses additional memory, you may need to increase the maximum heap size or buy additional memory, which is usually cheaper compared to the cost of the developer, even if those who control the budgets do not see it. It may still cost you less than the development time that it saves you. Only you can decide if it's worth it.

Answer 3

You can find this presentation from PGCon interesting:

ORM or not ORM