though i am late to the party, since it s like about month i have been deliberating on building an application based on cqrs+event sourcing. here your example is been total brainer. many thanks.

my self not an expert an average coder who is attempting to shift to architectural  context beyond all routine coding. with this entry i d like emphasize on your implementation with directbus (servicebus). how you come up with such idea. i mean is there any example how to build such architecture. as such you came with componentizing as router+message using queues. i know you said that purpose just demonstrative but i found it concise. however i continuously finding myself – aha that s like that  but why? – is it normal? or am missing something? like having no clue?
 
thank you.

When I read through the above I could see the whole thing applying perfectly to a web app, but not the sort of app I’ve just described above. Tantilizingly I sort of can, but I’m at risk of blurring the distinction between read and write here. Any thoughts?

If you serialize the whole event into a single column in DB, what happens if after some time you refactor the event object in your code?

For example, you add a new required field to an event or change an event’s field from name to title? If this happened, you wouldn’t be able to replay those events, would you?

Also, if the whole event is stored in a single DB column, you will not be able to run data mining queries like: show me all the transfer money events where the transfered amount is within a range? (I’m not familiar with data mining, so there’s a chance there’s no need for such queries)

Hope that helps.

In this case you could choose to implement a view model that assumes certain behavior from the domain. So it will do some basic checks to verify that the command is ok, then after sending the command and receiving a OK back (command either receive an Ok or Exception back) it assumes that the order is added and it will add it to its local representation of the list with orders (if it matches the filter criteria).

But to be honest there are other options as well all depending on how critical it is that you need the last data in each client vs only the client that submitted it. Anyway surely a whole new post

Hope this helps.

though i am late to the party, since it s like about month i have been deliberating on building an application based on cqrs+event sourcing. here your example is been total brainer. many thanks.

my self not an expert an average coder who is attempting to shift to architectural  context beyond all routine coding. with this entry i d like emphasize on your implementation with directbus (servicebus). how you come up with such idea. i mean is there any example how to build such architecture. as such you came with componentizing as router+message using queues. i know you said that purpose just demonstrative but i found it concise. however i continuously finding myself – aha that s like that  but why? – is it normal? or am missing something? like having no clue?
 
thank you.