Home/ Questions/Q 8987785
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-15T21:52:27+00:00

I’m about to write a JPA based web application in Java and since it’s

  • 0

I’m about to write a JPA based web application in Java and since it’s my first time seriously working with persistent classes and databases in general, I would like to learn if I have to make specific considertions f.i. while designing the overall class structures like building it as flat as possible to keep the count of persistent classes low and the database structure simple. I really don’t expect long explanations but would like to get a short overview of general considerations which might not appear to be that obvious to one who is unexperienced with database applications.
Thanks in advance.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    general considerations which might not appear to be that obvious to
    one who is unexperienced with database applications

    Using an ORM is superficially easy and transparent, but there are many small issues to consider:

    • Object identity. Understand the root mismatch that relational database work with rows and keys, while in the object world, each object has one identity. There various ways to handle identity correctly, or incorrectly.

    • Mapping Data. First understand how you map simple data types (string, number, URL, etc.). See and understand techniques to handle convertion problems (URL or string, byte or blob).

    • Mapping Relations. Understand how you map relations (uni- and bi-directional), how to maintain the invariants with proper encapsulation, the issue of “orphans” objects who lost their parent, and how to map several relations to the same class differently, how to load eagerly or lazily and the link with the “N+1” select issue.

    • Mapping Inheritance. Understand the mismatch between object, class, and tables. Understand how far you can support inheritance with ORM.

    • Working with Sessions. Understand working with sessions: when an object is attached or detached, what’s the impact on lazy loading, how to deal with optimistic locking, the link between transaction and session.

    There is an abundant literature on JPA and ORM in general. The list above is just what came to my mind.

    Ideally, ORM should not impose constraints on your design. However, my advice would be keep it flat and simple.

    • 0