Hi,
We are using CQRS in our project and we really appreciate the benefits that it gives in terms of developing the UI without being dependent on domain model. We are currently in process of generating commands from UI and handling those commands. The tricky part about our UI is we perform multiple actions before we want to persist to database. In sense we want to create composite command which in turn containg multiple sub commands when calling save. We are struggling on how to dervie the sub coammand within the composite commands?
Should the sub command be created as part of any UI action on the screen or should it happen at the end when final save is called by comparing the current view with the view that the UI should have started with? Is there any other alternative approach for the same?
Anusha.
I wanted to thank you for
This blogs has very
This is a really good read
Thanks for the information. A
rosetta stone
Well, the post is actually
MBT, MBT Shoes, 60%
nothing is impossible.
This is nice post which I was
cookware of china
Keep up the good
Thanks for sharing this. high
For most couples who are
how awful
We have the latest coach bags
you
you
Hi Anusha, I have been
Hi Anusha,
I have been working with the CQRS pattern for a while, and hope I can help you with your question.
What I sense in your explanation is that you have multiple steps in your UI to do a single thing in your system.
In DDD, and even more so in CQRS, it is very important to see the Application perspective differently than your UI perspective. If it is 1 atomic operation for your application, you will have only 1 command. That command may be built up using several screens. In such case, you could use a command builder (builder pattern) and attach that to the user's session. When the command is completely built, send it to your command handler and deal with it the CQRS way.
In other words, a form submit does not have to be translated to a command one-to-one. You could perfectly have a wizard-like process to build up a single command.
Hope this helps.
hi
If you can write unit tests
sticker printing | folder printing