transactions - Handling transactional resources in reactive way -


i'm start new project in financial area, global , distributed transaction rule world, in reactive world things done in different threads , actors asynchronously classic approach won't work. here example. let's have ibm mq consumer receiving messages, guy reside in separate actor. transfer each message actor business logic or store in other transactional datasource oracle db. in case of disaster or exception in business logic need roll mq transaction , message polled again after recovery. how transactional data sources handled in reactive world? i'm looking in stm , seems solves problem, thing have explicitly handle exceptions (through supervising in akka) , rollback transaction in case of any. can see violation of reactive way of doing things, mq consumer actor must wait (block?!) until exception or success confirmation received actor (business logic or other transactional datasource) , commit or rollback mq transaction. correct understanding or i'm missing something? thanks.

you can use distributed transaction coordinator this. in .net, transactionscope help. (odp.net , msmq support transactionscope). might want use concept unit of work design pattern.

also have @ article: http://geekswithblogs.net/dotnetrodent/archive/2008/04/16/121279.aspx


Comments

Popular posts from this blog

1111. appearing after print sequence - php -

java - WARN : org.springframework.web.servlet.PageNotFound - No mapping found for HTTP request with URI [/board/] in DispatcherServlet with name 'appServlet' -

Ruby on Rails, ActiveRecord, Postgres, UTF-8 and ASCII-8BIT encodings -