[Discussion] Commands could be serialisable like events are. about eventsauce HOT 7 CLOSED

@dmecke "the worst thing ever" is a bit of an over statement. But in general deferred command handling doesn't reflect what's actually going on. Actions should always happen when dispatched and events can be handled later. This means we can more accurately model what's going on when we dispatch the command, which only results in an event that this was initiated/requested. The actual processing of said request would then be done in a process manager. Modelling is like this ensures the program behaves predictably and changes to the behaviour don't result in fragmented handling. For instance: what if a request also need to process an uploaded file? Now you deferred command need to either contain the file in a serialized way or some kind of middleware needs to be introduced in order to extract and re-attach the file. This introduces needless accidental complexity and makes it harder to see what is actually happening. All in all, it comes down to personal taste. I don't like it and won't use it because I find it harder to wrap my mind around.

from eventsauce.

Why not? I do this often to create a command log which can also be interesting for doing some command sourcing for testing.

from eventsauce.

If we have non-destructive code-gen, people can do this for themselves. Initially the idea was deferred command handling, which I then realized was the worst thing ever. But it does make sense from a logging perspective. But the fact that we don't have a command interface is beneficial because it doesn't conflict with anything either.

from eventsauce.

Perhaps having a default implementation of JsonSerializable would be good?

from eventsauce.

Why is deferred command handling so bad? I rely heavily on it and it causes no problems so far, but now I am a bit worried.

from eventsauce.

Thank you very much for the explanation!

from eventsauce.

This was implemented in the last version. Tracing and logging are nice use-cases for this. It's implemented as an optional "opt-in" feature in the CodeGen section.

from eventsauce.