Design Patterns used in Hibernate Framework

In this post, let's discuss a different kind of design patterns which are widely used in the Hibernate Framework. Design Patterns denote the best computer programming practices in the object-oriented software development. Hibernate framework has been built by using the following design pattern or standard practices.
I list few known design patterns used in Hibernate Framework.
Please mention in a comment, if you know any other design patterns used in Hibernate Framework.
You can also read my post of Design Patterns used in Spring Framework

Domain Model Pattern

The domain model is treated as POJO in Hibernate.
The domain model is an object model of the domain that incorporates both behavior and data.
Read more about Domain Model Pattern here
https://stackoverflow.com/questions/41335249/domain-model-pattern-example

Proxy Design Pattern

Proxy Pattern for lazy loading - https://docs.jboss.org/hibernate/orm/3.3/reference/en/html/performance.html
Proxy Pattern provides a surrogate or placeholder for another object to control access to it.
Read more about Proxy Design Pattern here 
http://ramesh-java-design-patterns.blogspot.in/2017/12/proxy-design-pattern.html

Factory Design Pattern

SessionFactory of Hibernate is an example of Factory Design Pattern.
This pattern defines an interface for creating an object, but let subclasses decide which class to instantiate. Factory Method lets a class defer instantiation to subclasses.
Read more about Proxy Design Pattern here 
https://ramesh-java-design-patterns.blogspot.in/2017/12/factory-design-pattern.html

Query Object Pattern

Hibernate Criteria API and the modern JPA2 Criteria API are an excellent examples Query Object Pattern.
Read more about Query Object Pattern here 
https://stackoverflow.com/questions/2068478/query-object-pattern-design-pattern

Data Mapper Pattern

A layer of Mappers that moves data between objects and a database while keeping them independent of each other and the mapper itself.
Read more about Data Mapper Pattern here 
https://en.wikipedia.org/wiki/Data_mapper_pattern

Unit of Work 

This pattern as part of Session object in hibernate.
Read more about Unit of Work  here 
https://martinfowler.com/eaaCatalog/unitOfWork.html

References

Purchase top Java books from Amazon Store:

Comments

Post a Comment

Popular posts from this blog

Value List Handler

The  Value List Handler  provides the search and iteration functionality. To perform a search, the Value List Handler uses a  Data Access Object  to execute the query and retrieve the matching results from the database. It is hard to understand this pattern so my suggestion is to go to  source code  section and have a look at code step by step gives you more clarity. This pattern is divided into a number of sections for simplicity like problem, forces, solution etc. Problem (Problem section describes the design issues faced by the developer) You have a remote client that wants to iterate over a large results list. Forces (This section describes Lists the reasons and motivations that affect the problem and the solution. The list of forces highlights the reasons why one might choose to use the pattern and provides a justification for using the pattern) You want to avoid the overhead of using EJB finder methods for large searches. You want to implement a read-only use-case that does
Read more