1 / 13

Transactions in Orchestrations

Transactions in Orchestrations. Jan Eliasen, BizTalk MVP Twitter: @ jan_eliasen Blog: http://blog.eliasen.dk. Agenda. Jan Eliasen – who am I? Transactions and compensation Examples/Demos Questions. Jan Eliasen – who am I?.

nanda
Download Presentation

Transactions in Orchestrations

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Transactions in Orchestrations Jan Eliasen, BizTalk MVP Twitter: @jan_eliasen Blog: http://blog.eliasen.dk

  2. Agenda • Jan Eliasen – who am I? • Transactions and compensation • Examples/Demos • Questions

  3. Jan Eliasen – who am I? • Master of Science in Computer Science and Humanistic Computer Science • Work at Logica Denmark as an IT architect • Four times and current BizTalk MVP • Four exams (3 MCTS) in BizTalk • Swedish? Please don’t…  FOR MORE INFO... Email: jan@eliasen.dk, Personal blog: http://jan.eliasen.dk, BizTalk blog: http://blog.eliasen.dk, Twitter: @jan_eliasen

  4. Jan Eliasen – the author • Reviewers: • Randal van Splunteren • Gijsbert in ’t Veld • Available in January 2011. • I read four chapters of this book and lost 10 pounds (Jan Eliasen)

  5. Transactions • Buying snooker tickets • My friend: • Withdrawal • Deposit • Withdrawal • Deposit • Withdrawal • Deposit • Withdrawal • Me: • Withdrawal • Deposit • Withdrawal

  6. Transactions and compensation • Transactions • Atomic • Long Running • Exception handling • Compensation

  7. Atomic transactions (1/2) • ACID Properties • No persistence • Used for • Grouping Send shapes. • Leveraging classes that are not serializable. • Calling functionality in assemblies that must enlist in transaction. • No custom exception handler

  8. Atomic transactions (2/2) • Cannot have nested transactions. • Will retry automatically (21 times/2 sec) • If other transactional component is used and timeout expires • If you throw a Mirosoft.XLANGs.BaseTypes.RetryTransactionException • If a PersistenceException is thrown upon commit.

  9. Long running transactions • No ACID properties • We get Consistency and Durability • No automatic retries • Provides exception handling • Provides nested transactions • Do NOT consider this as an amputated atomic transaction

  10. Exception Handling • Exception handlers cannot be added to Atomic Transactional Scopes. • All Scopes have a default exception handler. • Catch the most specific first and remember to rethrow the exception. • Do compensation of LR transactions in custom exception handler

  11. Compensation • Compensation is NOT a rollback • How to determine compensation code? • All transactional Scopes have a default compensation block • Default DOESN’T do compensation. • You can override the default compensation block, but be aware…

  12. Demo – yeah!

  13. Questions? Feel free to evalulate me at http://speakerwiki.org/speakers/Jan_Eliasen

More Related