Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 2
    If you weren't writing this in DDD, which approach would you take and why? Commented Jan 26, 2021 at 21:00
  • @RobertHarvey, thanks, I was hoping you would notice this question. That said, I don't want to answer your question because, in all honesty and humility, I don't think I have ever gotten this right in all these years. Ugh. Anyway, to answer your question, if no DDD, I would put it in the "query" to the database, wherever that be, only to avoid load ALL objects in memory.OR, I would load all Product IDs by query, pass it to Business Logic layer, let that layer run the filter and pass them back to App layer, and finally query database to bring whole entities for the filtered IDs. Commented Jan 27, 2021 at 21:09
  • Hmm.. maybe I misunderstood your question. So... Not thinking about "DDD", I would probably choose Approach 4 as it has the cleanest and most flexible design. But it is complex, no doubt. So until I can buy time to implement it, I would settle for Approach 1 as it will be the most performant. Commented Jan 27, 2021 at 21:19
  • 1
    I don't understand why you chose to use two separate domains. The products for both use cases / user stories are the same products, so to me the difference in usage for these two users does not justify making it a separate domain. Coupling between domains should be as little as possible and by making this two separate domains, you have the entire product as coupling. I would make it one domain with two functions in an aggregate root. Commented Jan 28, 2021 at 10:45
  • Got your point. Consider them as sub-domains if not domains. The primary motivation was that Admin operations are auxiliary to the final Store App. In other words, the Store App can exist independent of how its Products data is populated. Anyway, if I go with your approach and merge them, the question still remains: where should I place that domain query logic? Combining your reasoning to have a single domain and the answer from Fabio below, I feel that I am getting closer to understanding my domain better. I'll add further comments and mark an answer soon. Thx! Commented Jan 29, 2021 at 4:24