Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with domain-driven-design
Search options not deleted
user 372608
Domain-driven design (DDD) is an approach to develop software for complex needs by connecting the implementation to an evolving model.
0
votes
Should queries in CQRS be designed based on external demand?
Your decision shouldn't depend on the architecture at all. The degree of reusability of your interface and query implementation (both of which you should be considering, since you are designing user-f …
- 125
1
vote
Where should the user access bounded context stands in DDD and Clean Architecture?
You sort of answered your own question right at the end. On most applications, The login system does not belong in the domain layer.
Unless your application focuses on authentication (e.g. you are dev …
- 125
0
votes
Does DDD and CQRS Make Sense for a application that is mostly Data Entry and Reporting
One issue with mixing DDD and CQRS:
If you were to use DDD as intended (as opposed to taking what you need) CQRS would not work, as this very principle sort of flies in the face of the "True domain mo …
- 125