@Transactional applicability for read methods

Question

I want to add Transactional support for my service class. If I add javax.transaction.Transactional annotation to Class which contains both read write methods how it behave?

By doing that for read methods in that class, does is make execution slow. Or does spring-boot ignore it for read methods?

Without using `@Transactional` for a read method, you might read data that's partially updated or inconsistent in some other way. — chrylis -cautiouslyoptimistic-, Jul 24 '19 at 04:19

score 1 · Accepted Answer · answered Jul 24 '19 at 04:17

For read operations, we use org.springframework.transaction.annotation.Transactional with parameter @Transactional(readOnly=true)

This just serves as a hint for the actual transaction subsystem; * it will not necessarily cause failure of write access attempts. and It will not slow execution.

score 0 · Answer 2 · answered Jul 24 '19 at 04:24

First thing you need make clear that the @Transactional in javax and Spring is different: https://stackoverflow.com/a/26387927/11827984
The second thing is that scope of @Transactional. When you write in top of a method, its scope will apply for this method, when you write in top of a class, its scope will apply for this class. (More about here: https://docs.spring.io/spring/docs/4.2.x/spring-framework-reference/html/transaction.html#transaction-declarative-annotations ). And annotation has option for it @Transactional(readOnly=true) when you want for read only.

@Transactional applicability for read methods

2 Answers2