The concern is that if the same query is invoked every time for a particular entity and the table data is not liable to change for a particular time slot, we can possibly cache the query results with Hibernate.
hibernate performance tweaks Archive
Spring provides support for both programmatic and declarative transactions. With programmatic transactions, transaction management code needs to be explicitly written so as to commit when everything is successful and rolling back if anything goes wrong.
In normal scenarios, in an application using Hibernate, we don't bother retrieving the whole entity with all its properties even though we don't need all of them for a particular use case. A single entity might have 30 properties, while we might just need a few to be set in our web service response or
Get more stuff like this
in your inbox
Subscribe to our mailing list and get interesting stuff and updates to your email inbox.
Thank you for subscribing.
Something went wrong.