On Sunday, January 11, 2015 at 9:10:21 PM UTC+1, Soumya Simanta wrote: > 2. Even if your core events don't change you may need to add information > later which effectively changes your event resulting in a new version. > Something like this is likely to happen at initial stages of your project > when the business concepts are are still in flux. One way to address this > is to replay the old events from start and create a new set of events with > the new version. >
Sounds like a plan. I was wondering about this approach and it forces us to have both (old and new) versions of events in class path. I might be wrong, but it seems like quite error prone process (remembering about removing unused versions for next release, but keeping n-1 so it can be replied etc.). Additionally, I'm also interested in "non blob" serialization, because I cant recall serializing non-binary information into blob and not regretting it soon enough :-] . Robert -- >>>>>>>>>> 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.
