Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If I'm not mistaken, you are asking two questions:</p> <ol> <li>How to structure a DDD application?</li> <li>What about those long namespace names?</li> </ol> <p>My answer is rather lengthy - I took the liberty of splitting it into two anwsers.</p> <p>This is an answer to the second question:</p> <p><strong>2. What about those long namespace names</strong></p> <p>I don't think long namespace names are necessarily messy. IMHO what looks messy in your names are:</p> <ul> <li>the repeating of the words "Product" and "Core"</li> <li>The use of the general term "Impl"</li> </ul> <p>A first improvement could be:</p> <pre><code>// The Domain objects go here; MyCompany.MyProduct.Core.Domain; // DataAccess interfaces go here: MyCompany.MyProduct.Core.DataAccess; // a Linq implementation of the DataAcces interfaces go here: MyCompany.MyProduct.Core.DataAccess.LinqImpl; // The Core service go here: MyCompany.MyProduct.Core.Services; // Some general purpose infrastructure goes here (e.g. emailing code) Mycompany.MyProduct.Infra; </code></pre> <p>Furthermore, I find that the use of a commercial product name (such as MyProduct) in the code structure is bad (what if marketing chooses a different name?); I like to use the name of logical subsystems instead. Let's assume your building car rental system. Then <code>CarRental</code> will be considered the core functionality of this app. Then I'd use the following namespace structure (Serra is the name of my company):</p> <pre><code>// For classes Customer, Account, Car Serra.CarRental.Domain; // I use Dao as a general abbreviation for "Data Access Objects" // Dao interfaces go here: Serra.CarRental.Dao; // Linq implementation for Dao interfaces Serra.CarRental.Dao.Linq; // For Services specific to the car rental domain: // AccountService and RentalService and CarAvailabilityService Serra.CarRental.Services; // For UI objects (not relevant in you situation?) Serra.CarRental.UI; // general service code; ignorant of the CarRental domain (e.g. an EmailService) Serra.Infra.Service; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POSome Questions about structuring domain-driven-design namespaces
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMarijn
    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'll try to answer your other question later today.
      singulars
      1. PO
      1. USMarijn
    2. CO@Code Sherpa: _are_ you questioning how structure a DDD app? After re-reading your question, I'm not so sure anymore.
      singulars
      1. PO
      1. USMarijn
    3. COHi again Marijn, thanks. Well, I am really looking for a good approach but since I have already started with DDD, it would probably make sense that I don't change anyhthing around at this point. Unless somebody points out that DDD is simply "wrong" for what I am trying to do. Thanks again!
      singulars
      1. PO
      1. USPeter
 

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