Hands-On High Performance with Spring 5

Transaction

Hibernate does the grimy checking just when it needs to, to keep in mind the execution cost. The cost increments when a specific substance has a relating table with an expansive number of segments. To try and limit the filthy checking cost, it's better we help Spring by determining an exchange to be perused, which enhances the execution stunningly better, wiping out the requirement for any grimy checks.

The following is an example use of the @Transactional annotation, which indicates that the method runs within the Hibernate transaction:

@Transactional(readOnly=true)public void someBusinessMethod() {    ....}