Transactions are the one feature which developers and architects alike seem to forget, until they find themselves in need of one. At that point, it can be too late to alter the data layer to support it because of the amount of regression testing needed to make sure the changes haven't broken anything. And that's when the phrase, "we can bypass the data layer just this once" starts to enter the conversation. Typical workarounds include writing custom data layer routines that pass a transaction object around, or moving all of the logic to a stored procedure and performing the transaction maintenance there.

EasyObjects.NET solves this problem for you by incorporating transaction support from the beginning. Rest assured, when you need them, you can incoporate transactions by adding less than 10 lines of code (and zero changes to your data layer). Built-in support includes:

1. Everytime Save is called, all batch updates occur within the same transaction. The Save will either succeed as a group or else the transaction is rolled back.
2. Multiple business objects can easily participate in the same transaction, without passing a transaction object around. The current transaction is stored in Thread Local Storage (TLS), and every object automatically pulls the current transaction from there (or creates one if it doesn't exist).
3. Transactions can span databases, so a rollback request will cause a rollback in all databases covered by the transaction.