Book Image

Mastering Hibernate

Book Image

Mastering Hibernate

Overview of this book

Hibernate has been so successful since its inception that it even influenced the Java Enterprise Edition specification in that the Java Persistence API was dramatically changed to do it the Hibernate way. Hibernate is the tool that solves the complex problem of Object Relational Mapping. It can be used in both Java Enterprise applications as well as .Net applications. Additionally, it can be used for both SQL and NoSQL data stores. Some developers learn the basics of Hibernate and hit the ground quickly. But when demands go beyond the basics, they take a reactive approach instead of learning the fundamentals and core concepts. However, the secret to success for any good developer is knowing and understanding the tools at your disposal. It’s time to learn about your tool to use it better This book first explores the internals of Hibernate by discussing what occurs inside a Hibernate session and how Entities are managed. Then, we cover core topics such as mapping, querying, caching, and we demonstrate how to use a wide range of very useful annotations. Additionally, you will learn how to create event listeners or interceptors utilizing the improved architecture in the latest version of Hibernate.
Table of Contents (16 chapters)

Scalability


Large enterprise applications that serve large number of users, without a doubt, have to be able to scale to keep up with the demand. There are various ways of accommodating scalability requirements. Let's discuss those here.

Clustering

When working in a clustered environment, you need to be aware of how it could impact Hibernate. One thing that could be impacted by deploying in a clustered environment is identity generation. If you use an increment strategy for ID generation even in a thread-safe mode, you are still not guaranteed uniqueness. Even if you use UUID using java.util.UUID, the likelihood of collision is still there, though very minimal.

Another consideration is when dealing with detached entities. If you keep detached entities in your HTTP session, you have to ensure that either session affinity or sticky session is enabled, or session data is shared among the nodes in the cluster. This is typically done because one of the main reasons to use clustering is to support...