Java Is Fast. Your Code Might Not Be. | Jonathan Vogel
Fixing common Java anti-patterns took an app from 1,198ms to 239ms. Eight patterns that compile fine and pass code review but silently drain CPU and b...
Java Persistence
Summary
A guide on choosing the right collection type (List, Set, Bag, or Map) for Hibernate to-many associations, explaining how each affects database performance and when to use which.
Highlights
- Map collections add overhead and should not be the default choice for to-many associations
- A Bag is an unordered collection mapped via java.util.List; most associations should use Bag over List
- For many-to-many associations, Set is preferred over List because it avoids inefficient delete-and-reinsert operations
- Ordering should be handled via JPQL ORDER BY clauses rather than through collection type selection
auto-generated
Context
Audience
Java developers working with JPA and Hibernate who need to optimize database performance through proper association mapping
DomainJava Persistence / Hibernate
Formatlong-form article
Accessfree online
Source Overview
To-many associations in Hibernate can be mapped with List, Set, Bag, or Map collections, but Map is generally not recommended due to added overhead.
Mapping many-to-many associations as a List causes inefficient database operations when removing elements, as Hibernate deletes and reinserts all association records. Using a Set is recommended for many-to-many associations because it results in more efficient and minimal database changes.
Topics
Related
Hibernate collection mappingsJPA to-many associationsJPQL ORDER BYHibernate performance tuningMany-to-many relationship design
