Friday, 15 July 2011

Need help to understanding CQRS architecture -


I try under cqrs architecture style. I found the sample image of the cqrs architecture.

If the command handling data continues in the database, then why is the event handling update storage?

Example:

If I have command handling or event handling, then where uusur is a commodity.

Thanks

With diagram, this is for me a CQRS and an event source architecture Looks like. This means that the domain will produce events in response to the model command. Unlike DTO or to view the models, you store them in the event store. State transit for the domain in the event store, but the front end is not used for the front end, you need a reading model. You generate a read model from the events, so the event controllers need to write in the database. Of course, they are writing a reading model, not an event store. With a more detailed explanation on my blog, I have a similar diagram. You can find the post here: I hope you find it helpful.


No comments:

Post a Comment