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

Data Mapper Pattern

Image
This pattern belongs to  Data Source Architectural Patterns  Catalog and this Catalog belongs to  Patterns of Enterprise Application Architecture . Intent A layer of Mappers that moves data between objects and a database while keeping them independent of each other and the mapper itself. Mapper means an object that sets up a communication between two independent objects. Applicability Use the Data Mapper in any of the following situations when you want to decouple data objects from DB access layer when you want to write multiple data retrieval/persistence implementations Explanation The Data Mapper is a layer of software that separates the in-memory objects from the database. Its responsibility is to transfer data between the two and also to isolate them from each other.  With Data Mapper the in-memory objects needn't know even that there's a database present; they need no SQL interface code, and certainly no knowledge of the database schema.  How It Works The separation betwee
Read more

Information Expert GRASP Pattern

Image
Information Expert is the  GRAS Patterns (General Responsibility Assignment Software Pattern) Read about GRASP Patterns:  GRASP Patterns Overview Problem What is a general principle of assigning responsibilities to objects? A Design Model may define hundreds or thousands of software classes, and an application may require hundreds or thousands of responsibilities to be fulfilled. During object design, when the interactions between objects are defined, we make choices about the assignment of responsibilities to software classes. Done well, systems tend to be easier to understand, maintain, and extend, and there is more opportunity to reuse components in future applications. Solution Assign a responsibility to the information expert - the class that has the information necessary to fulfill the responsibility. Example   Let's consider Point of Sale (POS) application: a Brief overview of POS application. Application for a shop, restaurant, etc. that registers sales. Each sale is of one
Read more