Versioning event with complex type #5697
-
Hi I wanted to ask how do you solve problems with large objects (containing 6-7 fields) in Akka Persistance. For example, code below:
What should adding a new HouseActorModel look like?, with an eye to schema evolution for aka persistance. The second solution is to replace the entire House model with simple types, e.g. How do you deal with something like this? Do you change complex types to simple types, version multiple complex models, or maybe you have a different approach? Thank you in advance :) PS. I also asked on gitter too https://gitter.im/akkadotnet/akka.net?at=621cc1d50909252318003793, but no one answered to me :cry |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 10 replies
-
Hello @gaciv12 I saw the question you asked on |
Beta Was this translation helpful? Give feedback.
-
https://petabridge.com/cluster/lesson3 - I'll put together a YouTube video that explains how to do this in more detail, but basically you need to use custom serialization and apply https://aaronstannard.com/extend-only-design/ to your models. |
Beta Was this translation helpful? Give feedback.
-
More code below
But my main questions are: I consider to change Reply methods from |
Beta Was this translation helpful? Give feedback.
-
Bump, help please |
Beta Was this translation helpful? Give feedback.
-
Sorry for the delay on this, but my YouTube video explaining how to do this is finally finished: https://www.youtube.com/watch?v=oRll1Mzoyl4 It's about an hour long but covers the subject in detail, along with troubleshooting a live upgrade to existing event and state types. |
Beta Was this translation helpful? Give feedback.
Sorry for the delay on this, but my YouTube video explaining how to do this is finally finished: https://www.youtube.com/watch?v=oRll1Mzoyl4
It's about an hour long but covers the subject in detail, along with troubleshooting a live upgrade to existing event and state types.