They cross DB boundaries
by
Julian+Morrison
·
· Score: 4, Informative
A typical use of J2EE transactions would be an app that needs to modify in-memory objects, modify local SQL data, modify remote data via a defined abstract interface with limited permissions, and do it all as one transaction, succeed or fail atomically. J2EE transactions make that possible, and in some cases easy.
It's an "enterprise" thing. If your business is large enough to be horizontally partitioned into departments with seperate IT, then you'll probably need it. Otherwise, probably not.
A typical use of J2EE transactions would be an app that needs to modify in-memory objects, modify local SQL data, modify remote data via a defined abstract interface with limited permissions, and do it all as one transaction, succeed or fail atomically. J2EE transactions make that possible, and in some cases easy.
It's an "enterprise" thing. If your business is large enough to be horizontally partitioned into departments with seperate IT, then you'll probably need it. Otherwise, probably not.