Hello Jason!
Sorry for not getting back to you earlier but I've just gotten back from
vacation. I have switched projects since the versioned event data prototype
was developed and in the current project we have taken a slightly different
approach. Instead of saving the version number along with
Hi everyone,
we've discussed about serialization formats a few times on this list,
I think the discussion here: Best practices using Akka Persistence with
long-running projects?
Martin, I'm curious about your protobuf recommendation. I plan to persist
events and snapshots, and evolve the schema over time. Protobuf seems to
have the best support for evolution, but it's not perfect, and I feel quite
constrained by the generated code. For example, if I'm persisting a
Odd, I just took a look at your code and I'm intrigued. I am very
interested in how in Akka Persistence we store events/snapshots over a long
period of time while the schema evolved, without creating a mess of code to
maintain. I've explored protobuf and Scalabuff, but it feels very
Hi Martin!
We haven't looked that close at protobuf yet (we don't use this for
remoting purposes, only for persistence), and we needed something that was
as simple as possible (i.e. departed from our regular data expressed as
case class-approach as little as possible), and also was fully
Hi!
We have a versioning extension that we are experimenting with at the moment
(it is quite experimental at this point and completely without tests):
https://github.com/odd/akka/tree/wip-persistence-odd/akka-contrib/src/main/scala/akka/contrib/persistence/versioning
The basic idea is to attach
Hi Odd,
why have you chosen this versioning approach instead of a protobuf based
one, for example? What are the advantages?
On 19.05.14 14:08, Odd Möller wrote:
Hi!
We have a versioning extension that we are experimenting with at the
moment (it is quite experimental at this point and
Hi
I've found a new thing to worry about :-)
If I use an eventsource model and content myself with the default
serialization and akka persistence, what's the likelihood of my serialized
objects becoming unreadable in the future? What's the long-term stability
of the default akka serialization
