For years Hibernate has been optimized to store data and load of entire object graphs from the database. So you should assume that most persistence problems could be avoided by using Hibernate alone.
But it’s surprisingly easy to harm your project with … or should I better say “thanks to Hibernate” …
From practical experience I show in this talk how to:
- Delete most of your data with just one annotation;
- Implement the persistence logic in such a way that nobody will understand it;
- Reliably prevent the use of the entities in client applications and;
- Bring the database to its knees with thousands of queries.
If you’ve ever wanted to cause a project to fail with the help of Java’s most popular OR mapper, you shouldn’t miss this talk!