-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Persistence of events as byte array #3
Comments
|
Instead of persisting Serialized object, it is related to Slack discussion, the long list of pain point from Damian, point 6. I'll report here for completeness.
Byte[] can be too low level, but it could be nice to have a pipeline and letting the user choose format for their Events. |
+1, got it. Thanks On Fri, Jun 5, 2015 at 9:49 AM, Gian Maria [email protected] wrote:
Mauro Servienti |
this way we can handle better upgrading / transformation because we are not forced to rely on class serialization (easy to broke). With opaque serialization in place we can configure any pipeline
We could add as a contrib project a simple denormalizer to write recombined streams (read model for the consumers) |
It would be probably better to handle persistence of events with low level format, such as byte[], but support a pipeline where the user can inject stages if needed (es. serialization, upgrading events, etc).
The text was updated successfully, but these errors were encountered: