0

I am trying to understand DDD and CQRS, but I am confused by the idea that commands and queries are part of the domain alongside domain events as messages. Others say that commands and queries are part of the application layer. In both perspectives, only the handlers are seen as part of the application layer. Does this mean that, according to the first perspective, you cannot invoke queries or commands directly from the API/presentation layer and therefore have to wrap this call in an application service? Where should commands and queries be placed? The first perspective certainly complicates things.

Improve this question
2
  • 2
    Most people go with approach 2 (commands/queries in application layer) because it's way simpler. The "commands as domain messages" thing sounds nice theoretically but usually just adds unnecessary layers. Why make your controllers go through another service when they could dispatch commands directly? Stick with the application layer approach - your CreateOrderCommand is about "what can this app do". keep it practical Commented Aug 19 at 13:03
  • DDD and its patterns fit more naturally with the command side of CQRS, not so well with the query side. Commented Aug 21 at 13:01
Related questions
50
CQRS Commands and Queries - Do they belong in the domain?
94
DDD - which layer DTO should be implemented
10
CQRS commands and queries. Do they belong to Application or Domain level in terms of DDD?
Load 7 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.