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.

Required fields*

12
  • DDD can model persistence, if persistense is a part of domain. For example, if there is a document that should be stored indefinitely, it can have archive() operation and access to an Archive repository. When persistence is not a part of domain, why would you need to persist an object? Commented Sep 3 at 12:29
  • 1
    This question is similar to: DDD repositories in application or domain service. If you believe it’s different, please edit the question, make it clear how it’s different and/or how the answers on that question are not helpful for your problem. Commented Sep 3 at 12:32
  • Tree model in Domain Driven Design Commented Sep 3 at 12:33
  • 1
    How could I map a complex DTO to a Domain Aggregate in a Repository? Commented Sep 3 at 12:48
  • @Basilevs, I am currently thinking about the design of a jira like ticketing system, in such a system persistence is not a part of the domain but it is required to read information from a database to display and or do operations on and then write back Commented Sep 3 at 13:43