domain-persistence

To separate domain models from JPA persistence entities, define pure POJOs for domain logic and JPA-annotated classes for data access, converting between them via ModelMapper in repositories to maintain clear boundaries.

Domain models get polluted when JPA annotations and persistence logic are placed directly in domain classes. Enforcing strict boundaries by keeping domain models as pure POJOs with IDs only prevents this coupling.

The best way to handle UUID, BigDecimal, and BigInteger types is enforcing strict type handling during explicit conversions, ensuring these fields map correctly between pure POJO domain models and JPA persistence entities.

Configure repository conversion by applying ModelMapper for explicit mappings, using static factory methods to instantiate objects and manually managing audit fields to keep domain and persistence boundaries distinct.

Yes, this approach works with standard Spring Data JPA architectures by applying typical DDD-style patterns, using VO patterns and explicit repository conversion to keep domain models decoupled from persistence concerns.

You need Value Object patterns when enforcing strict domain boundaries to encapsulate specific types like UUID or BigDecimal, ensuring domain models remain pure POJOs free from persistence entity annotations.