ncqrs

问题 I have a layered application that send commands to the business layer (actually, the application is based on ncqrs framework, but I don't think it's important here). A command looks like this : public class RegisterUserCommand : CommandBase { public string UserName { get; set; } public string Email{ get; set; } public DateTime RegistrationDate { get; set; } public string ApiKey {get; set;} // edit } There is no logic in this class, only data. I want to have the users type their user name,

问题 I think I understand the idea of the read model in the context of ES + CQRS (please correct me if not). However, I still have a few doubts about using it in the context of ‘serious’ reporting. Let us say I use a relational db plus some ORM to crud my read models. One basic ‘summary stats read model’ could look like this: class SummaryStats1 { public Guid TypeId { get; set; } public string TypeName { get; set; } public Guid SubTypeId { get; set; } public string SubTypeName { get; set; } public

问题 Besides missing some of the benefits of Event Sourcing, are there any other drawbacks to adapting an existing architecture to CQRS without the Event Sourcing piece? I'm working on large application and the developers should be able to handle separating the existing architecture into Commands and Queries over the next few months, but asking them to also add in the Event Sourcing at this stage would be a HUGE problem from a resourcing perspective. Am I committing sacrilege by not including