Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm wondering, if in your case DDD is a good idea. I mean forums are data oriented by nature. Maybe should you consider a simplest approach and just use classic data oriented technologies to query your data. (ie, LINQ, Hibernate, plain SQL, entity framework or whatever you want depending on your plateform)</p> <p>You program maybe doesn't need a domain layer, or you'll end up with a class ForumDTO which hold data, and Forum which hold business logic, same things for post or thread, to me it seems an anti-pattern.</p> <p>What do you think ?</p> <p><strong>Update</strong></p> <p>I recommend you reading the book from Eric Evans, it has great examples of complex domain where DDD fits really well. After reading this book I was vey enthusiastic to apply what I've learnt, but I've seen that is some case data oriented approach is more appropriate.</p> <p>To me, there is almost no complex domain logic for a Forum, so you'll endup having a 1&lt;->1 mapping between your data layer and domain layer, it means duplication and overhead as I said.</p> <p>Seeing the description of your domain, your approach seems data oriented. For example, intuitively a forum HAS threads and threads HAS posts, the domain as you describe it doesn't reflect that, and you seem to normalize your object model to fit your database schema (which will be normalized).</p> <p>Forum seems the best class to be the Root of the aggregate (it's the more intuitive)</p> <p>If you really want to use DDD approach, you can inject repositories in your entities, and give your domain object meaningfull name as thread.GetLastPostOf(User user), depending on your requirements.</p> <p>But I agree with you when you say that you should have a repository with a method GetPostById.</p>
    singulars
    1. This table or related slice is empty.
    1. PODomain Driven Design - Repositories and aggregate roots
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USNicolas Dorier
    1. USNicolas Dorier
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI admit I did think that this might not be the best solution but it seems people come up with examples for message boards and shopping systems and stuff all the time?
      singulars
      1. PO
      1. This table or related slice is empty.
    2. CO+1, I'm not sure if this will be the case here (I don't think we have enough information about the domain), and the general question this raises is still interesting, but passing on DDD is certainly something worth considering.
      singulars
      1. PO
      1. USJeff Sternal
    3. COSo why exactly pass on DDD? Is there a line where an application doesn't 'fit' into DDD?
      singulars
      1. PO
      1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload