Java – transaction isolation level in financial applications

I'm reading about transaction isolation levels (serializable, repeatable, committed, uncommitted) and I'm a little confused about their respective uses Do I understand that this is correct, for example, in banking applications (remittances, etc.), the isolation level used may be serializable because it is not allowed to relax this rule?

Solution

You can choose the isolation level based on how your application works You may need different isolation levels for different database calls, depending on what you do with the data

There are no strict rules for any specific industry (such as banking), but some data (such as financial transaction data) is obviously important. You want to do everything possible to avoid data loss and data inconsistency

The level of isolation is better explained than I am here http://en.wikipedia.org/wiki/Isolation_%28database_systems%29