Hi,
Thanks for your explanations. I've also found link you provided (long
running projects one) and looks like promotion is what suits me the most in
this particular case. I can also combine it with journal implementation
(which I somehow missed during my learning process). Being able to inject
ow
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 man
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
I'm not an expert and still learning how to design systems using this
approach.
Here are some suggestions:
1. If you design your domain using DDD properly you will end up with a
reasonable set of aggregates, entities and value objects. You should design
your events to mirror your business pr
