2

I might sound dumb with this question but i am really confused. Does creating a command,query,commandhanlder,queryhandler and repositories and using dependency injection to resolve queryhandlers and commandhandlers based on query and command respectively qualify as cqs or cqrs ?

Or Using Task Parallel library for command and query handlers qualify as cqrs than cqs ?

Or Is it really based on Use Case whether there is a scenario of collaborative domain --> Multiple users trying to access limited data.

Dave Schweisguth
  • 36,475
  • 10
  • 98
  • 121
Dilip Nandakumar
  • 198
  • 2
  • 14
  • This is not at all a dumb question. This is a very common question when you start looking at the CQRS-pattern. I think that the answer from Alexey Zimarev explains well on a higher lever the differences. – user707727 Apr 16 '15 at 12:19

2 Answers2

12

CQS says your command methods should not return anything (be void) and only mutate the object state. Query methods should return results and query method calls should be immutable, query method does not change the object state. This is it.

CQRS is "splitting a model object into two". You will have one model to write and one model to read, which are completely separate. You might store your data in the same database, but where you write to using your commands is separated from where you read from using your queries, they use different models (write and read).

LJNielsenDk
  • 1,414
  • 1
  • 16
  • 32
Alexey Zimarev
  • 17,944
  • 2
  • 55
  • 83
2

CQRS is an architectural pattern. For me, CQS is more of a class design principle.

David Osborne
  • 6,436
  • 1
  • 21
  • 35