XAP .NET provides an explicit transaction management programing model. It allows developers to easily write transactional code with the lowest overhead possible while minimizing the amount of hand-crafted code and separating it from the application hosting environment and instance management.
Transaction concept and API
Locking and Blocking
Using optimistic and pessimistic locking to preserve the integrity of changes in a multi-user scenarios.
XAP’s ExclusiveReadLock, ReadCommitted, DirtyRead, and RepeatableRead modifiers.
The optimistic locking protocol provides better performance and scalability when having concurrent access to the same data. Optimistic locking offers higher concurrency and better performance than pessimistic locking. It also avoids deadlocks.
In the pessimistic locking approach, your program must explicitly obtain a lock using a transaction on one or more objects before making any changes.
You can view and inspect ongoing Space transactions with the Management Center.