Hi, I was looking for using single writer principle in our architecture for domain object persistence. Want to use event sourced persistent actor sharded in akka cluster by particular algorithm(ex. by particular ID), which will make sure CRUD's for *A* domian object happens through only one persistent actor.
A simple use case i.e. CRUD for A domain object can go through single writer. But consider a situation, if business evaluation requires to change multiple domain objects in one stroke, *what should be the solution?* Lets take this example, 3 domain objects belonging to 3 different single writers have to be changed in one stroke.In this single writer wont help, as all 3 domain object updates will go through *3 separate single writers*, and *will not be in one transaction*. Is it possible with event sourcing to involve *different/multiple single writer's in one transaction scope*? -Prakhyat M M -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
