I\'m having a debate with my coworkers in the design of the read side of a CQRS application. Option 1: The application read side of my CQRS application returns DTOs, e.g:
I understand that data is always stale. What is a way to handle a workflow task, like Approve Invoice. This task is allowed to execute once by the user. When this is processed by an async service it
When looking to JOlivers \"EventStore\", I see that StreamRevision and CommitSequence are the same if you only commit 1 event. And it is the StreamRevision that is used to select events with.
If I were to create a basic personal accounting system (because I\'m like that - it\'s a hobby project about a domain I\'m familiar enough with to avoid getting bogged-down in requirements), would a N
I\'d like to access my aggregate root by an interface it implements: repository.GetById[[IMyInterface]](id);
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references,or expertise, but this question will likely solicit debate, a
I decided to get acquainted with a concrete CQRS implementation on the example of Greg Young\'s implementation
I\'m using the NES sample which works out of the box. Then I have swapped the NServiceBus 2.5 version with an older 2.0 but this results in the following error when starting the MVC application:
Please explain the reasoning behind making EventStoreRepository.GetById create a new stream when an aggregate doesn\'t exist. This behavior appears to give GetById a dual responsibility which in my ca
We have an older installation running with NSB 2.0. I know NES is released for 2.5 but since it\'s just a layer on top I figure it should be possible to try NES with NSB 2.0. Also, for various reasons
加载中,请稍侯......