G.WCF Transactions
Implementing Transaction:
Add transaction support to the service contract. This is required.
Add transaction support to the code that implements the service contract. This is required.
Configure transactions in the implementation code. This is optional.
Enable transactions on the binding. This is required.
WCF Transaction Types
Long Running (Business) Transaction
ATOMIC transaction
Light Weight Protocols (Work in same app domain)
OLE TX : Support Distributed transaction in Windows Intranet environment, works within firewall and no cross platform support.
Web Service Atomic Transaction (WS-AT) : Almost like OLETX but work on cross platform and across the firewall, it is part of WS* specifications and uses Two Phase Commit protocols to implement Atomic transaction across various distributed parties.
WS Coordination: TBD
Transaction Managers
Light Weight Transaction Manager : Uses lightweight transaction protocol
Kernel Resource Manager : Same like LTM but uses advance features , shipped with server 2008
Distributed Transaction Manger : support distributed transaction and can use either OLETX or WSAT protocol as required.
Resource Managers: Theses are the application that usually stores data i.e. SQL Server.
Durable Resource Manger : Like SQL Server , MSMQ
Volatile Resource Manager : Handles in memory changes of the values of various data structures.
Transaction Flow or Propagation : It is a feature of distributed transaction in which client transaction scopes propagate to server.http://msdn.microsoft.com/en-us/library/ms733116(v=vs.110).aspx