Hi Robert, You could implement a journal which serializes differently, it's up to the journal implementation really. The Journals are given the payload: Any and are free to serialize how they see fit.
For optimal performance binary encoding is the obvious choice, and also for schema evolution many binary formats have things in their impls ready for it, please refer to this discussion for more information where we discussed many formats in depth: akka-user: Best practices using Akka Persistence with long-running projects? <https://groups.google.com/forum/#!searchin/akka-user/akka$20persistence$20long$20running/akka-user/xNtxm8sLtO0/6FcJNbbgoY0J> . Also, the above linked thread should help you figuring out how you want to keep old versions of events (there's 3 ways basically: evolve the schema non-breakingly, "promote" during old schema event replay to new schema event, versioning and multiple event types). The choice on how to deal with this goes hand in hand with which serialisation format you are going to pick (and non-binary doesn't really solve these problems magically - the same problems remain, except it's easier to look at them). Hope this helps, cheers! On Mon, Jan 12, 2015 at 3:59 PM, Robert Budźko < [email protected]> wrote: > 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. > -- Akka Team Typesafe - The software stack for applications that scale Blog: letitcrash.com Twitter: @akkateam -- >>>>>>>>>> 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.
