title: JPA entity model best practices
body: <p>We try to figure out a memory leak and right now we are at a point where we think about the size of the entity model and relations between entities. We are using EclipseLink 2.0.2 as JPA provider running in WebLogic 10.3.3.</p>
  
  <p>Our model consists of 162 entities. Those are not all directly connected to each other but you can navigate from one starting entity to an arbitrary other entity through transitive relations. All associations except one-to-one are lazily loaded.</p>
  
  <p>So, what was your biggest entity model and did you consider any memory leak or other wired behavior? Do you have any recommendations for designing an entity model? Are there common patterns you experienced to cause problems?</p>