Hi, We've decided to go for a customized json serializer with built in support for mapper (converter) classes. These mappers implement a common trait and do the conversion by pattern matching on the given json (previous version) and converting to new version. It is also configurable to force an application wide snapshotting by all persistent actors, in order to truncate old journals with previous formats and thus be able to keep a clean codebase (not having to keep all versions of an event definition in the source tree). We have so far done some limited testing on different versions and it worked out nicely.
On Sunday, October 19, 2014 at 3:35:32 AM UTC+2, rrodseth wrote: > > I'm hoping to build a case for using Akka Persistence, and expect the > event schema evolution to be a sticking point. People are quite used to > their database migration scripts. > > I've seen the threads on this list, but I'm wondering what the current > thinking is on the least painful option, and would also like pointers to > sample code. Do Protobuf, Avro and Thrift all require an IDL compiler? Is > Cap'n Proto a viable option? Would something based on Scala macros provide > a way to avoid an extra compilation? > > Anything on the horizon I should know about? > > Thanks. > -- >>>>>>>>>> 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.
