Hi,
On Wed, May 06, 2015 at 10:13:38AM +0100, Sanne Grinovero wrote:
I do agree with you that it's kind of weird that people write
code
without making transactional requirements explicit in the code, but it
seems that the trend is to abstract from that and use the
"Transaction" term as a "Unit of work".
What are you referring to? Where do you see this trend.
For example I find it strange that - in Java - one has to configure
the isolation levels of transactions to the safest (least efficient)
option possible among the types his *various* use cases require. It's
pretty obvious that it would be more efficient to choose those levels
as "profiles" based on use case, possibly bean or even method level.
I guess that's were complex applications split up in multiple deployments..
I am not sure I am quite following you on this.
--Hardy