Book Image

Mastering Hibernate

By : Ramin Rad, Koushik Srinivas Kothagal
Book Image

Mastering Hibernate

By: Ramin Rad, Koushik Srinivas Kothagal

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)

Caching benefits and pitfalls


In general, the caching mechanism is designed to improve the performance of the application. This is particularly true for data that doesn't change often. Reference data is a perfect example. Another example is articles posted on a discussion forum. Of course, if this data ever changes, you would have to implement the capability to invalidate and refresh the cache. It is a general belief that your application should perform reasonably well without caching enabled. However, there are many things you could do to improve the performance and responsiveness of your application, and caching is one of those things.

However, with this added feature come pitfalls. Caching persisted data is not a good idea if the data can be modified by another application, for example, if your application runs alongside a legacy application. Another thing to watch out for is using a second-level cache in a clustered environment. Not all second-level cache implementations support clustering...