Hi everyone, This is my first post on this group so for starters I'd like to thank the Akka team for the awesome product. Love it.
I was just going through the Akka Persistence documentation and I was wondering how to achieve the event sourcing functionality as it is used in Domain Driven Design. For example, when I get a command to modify an aggregate with some particular id, is it a good idea to instantiate an actor for that aggregate and additionally a processor to retrieve the current state and then persist the new event? I guess my insecurity comes from the statement in docs that "A processor must have an identifier that doesn't change across different actor incarnations.". Additionally how this solution will be represented in MongoDB? Will all the events for the aggregate type will land in the same collection? Sorry if I'm asking these qestions too early in my own research and I could have found a solution myself, but maybe someone has already done it and could shed some light on this particular use case. Thanks, Jakub -- >>>>>>>>>> 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
