Transactions: Philosophy

• Transactions will be large & small, short & long

  • Mechanisms should be unbounded

• They will be frequent and visible in user code

  • Easy to use
  • Not hidden in libraries

• Implemented with general-purpose mechanisms

  • In addition to synchronization, useful for fault tolerance, exception handling, backtracking, priority scheduling...

• Object-based transactions

  • Expose a richer abstraction
  • Move beyond emulating an unavailable HTM

Notes: