There is a quite nice approach that Rickard Öberg uses for Qi4J. He uses _two_ versions for each message. "old" and "new" old events needs to be able to be promoted to new events. so each time you deploy, you promote old messages to new messages, and the system will run with only the new version. this way, you never ever have to have code for more than two versions at any given time. Not sure how this plays with Akka persistence, but I Think its a nice approach since you dont have to deal with 10 year old versions in long lived systems. (Then again, people may object to the fact that you need to tansform old to new and that it might alter the history.. but thats a different story :) )
Den onsdagen den 26:e februari 2014 kl. 18:53:49 UTC+1 skrev rrodseth: > Now that we're getting excited about using akka persistence for > event-sourced DDD applications, can anyone provide any insights or > resources about handling versioning? Anything specific to akka persistence? > For example I have a book (produced by Microsoft) that talks about > mapping/filtering events in the infrastructure before they reach the > domain. How would we do that with akka persistence? > > Thanks in advance. > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>>>>>>> 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/groups/opt_out.
