Hibernate Open Session in View: Pitfalls and Alternatives
Open Session in View, despite its apparent simplicity, suffers from several drawbacks that warrant caution in its use.
Issues with Open Session in View
While the approach may alleviate pain points in isolated JVM scenarios, it comes at a cost:
-
Auto-commit mode in UI rendering: After service-layer transaction completion and Session closure, subsequent UI rendering triggers auto-commit for every statement, increasing database load due to excessive I/O.
-
Loss of separation of concerns: Statement generation spans both service and UI layers, complicating integration testing and the isolation of business logic.
-
Potential N 1 query problems: UI navigation is limited to traversing associations, which can exacerbate performance issues when associations are not eagerly fetched.
-
Connection lease time increase: The database connection can remain open throughout UI rendering, leading to congestion and limited transaction throughput.
Alternative Strategies
To avoid the pitfalls of Open Session in View, consider these alternatives:
-
Eager fetching: Fetch all necessary associations within the EntityManager scope, ensuring lazy initialization is not triggered during UI rendering.
-
Fetch mode customization: Use Hibernate's @BatchSize and FetchMode.SUBSELECT annotations judiciously to optimize association fetching without impacting all business scenarios.
-
Data access layer queries: Create tailored queries that specifically address the specific data fetch requirements of a particular use case.
Spring Boot Configuration
In Spring Boot, Open Session in View is enabled by default. To disable it, set the following property in the application.properties configuration:
spring.jpa.open-in-view=false
Copy after login
This will force proper handling of LazyInitializationExceptions, avoiding the undesirable consequences associated with Open Session in View.
The above is the detailed content of Is Open Session in View the Right Choice? Pitfalls and Better Alternatives. For more information, please follow other related articles on the PHP Chinese website!