A scope with no transaction is usually used as a try/catch block just to handle exceptions.
BizTalk Server supports two distinct types of transactions: atomic and long-running.
Transactions are implemented in Orchestrations using Atomic Scope. An Atomic Scope supports ACID properties of Transactions where as Long Running Scope Supports C&D (Consistency and Durability) properties of ACID.
Atomic: An atomic scope cant be placed within a Normal Scope.
There are two other Advantages of Atomic scope in addition to supporting Transactions.
1. Non-Serializable classes can be called from an Atomic Scope.
2. The number of Persistence points within an Orchestration can be reduced as an atomic scope will always induce one Persistence point (at the end of the scope).
Long running: A business process that might take seconds, minutes, or even days or weeks to complete. This is when a long-running transaction is more suitable.
BizTalk Server supports two distinct types of transactions: atomic and long-running.
Transactions are implemented in Orchestrations using Atomic Scope. An Atomic Scope supports ACID properties of Transactions where as Long Running Scope Supports C&D (Consistency and Durability) properties of ACID.
Atomic: An atomic scope cant be placed within a Normal Scope.
There are two other Advantages of Atomic scope in addition to supporting Transactions.
1. Non-Serializable classes can be called from an Atomic Scope.
2. The number of Persistence points within an Orchestration can be reduced as an atomic scope will always induce one Persistence point (at the end of the scope).
Long running: A business process that might take seconds, minutes, or even days or weeks to complete. This is when a long-running transaction is more suitable.
No comments:
Post a Comment