Reviews by real users

Just finished a project using open source libraries and have fresh impressions?

Write a review to share your experiences with open source!

On DevRates we focus on reviews by developers using libraries on their daily work.

Technology radar

Launching a start-up or commercial project using open-source libraries? No time to evaluate various technology stacks?

Interested in the latest trends and top-rated open source projects for all layers of your application?

DevRates contains projects reviews of most popular tagged categories and programming languages.

Build your skill profile

Join DevRates and build your public profile from libraries you know and experience positions from projects you've been involved in.

Follow projects and don't miss any news from blogs and twitter on your wall.

Your company is looking for talented developers? Register on DevRates and show your technology stack on your company profile.

JOIN THE COMMUNITY TAKE A TOUR

Related project

Hibernate

Review details

Created 7 months ago
Review score is 0

Overall review rating

4.0
Usability
7.0
Simplicity
2.0
Documentation
5.0
Community
4.0

hibernate is ubiquitous and quite simple to start with. but i met only frustration and dispair, when working with hibernate. there are thousands annoying bugs in bug tracker, documentation lack details (so you are forced to read a book)

heavy use of hibernate results in enormous memory consumption(so manual flushes are a must).

deadlocks are a usual thing and hibernate dont allow to tune locking order.

hibernate don't work with database constraints nicely.

entity state can only be managed from one side of bidirectional relationship.

proxy usage in not trivial when implementing equals or polymorphism. proxy visitor pattern is an example of proxy ugliness.

duplicated entities when doing join fetch is just ridiculous. don't tell me about OUTER joins - if there is always master entity, hibernate should always do master left join child. any solution offered by hibernate community results in perfomance problem - using Set results in duplicates send over network and increasing network load, using distinct projection results in filesort in most databases.

overall, hibernate was a performance issue in our last project. hubernate took much time mantaining it's own session and collection, each commit took seconds(!)

Sign in to vote for review score: 0
Scroll to top