Databases
StackOverflow2013
Postsdbo
POService Oriented Architecture & Domain-Driven Design
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POService Oriented Architecture & Domain-Driven Design
    primarykey
    data
    text
    <p>I've always developed code in a SOA type of way. This year I've been trying to do more DDD but I keep getting the feeling that I'm not getting it. At work our systems are load balanced and designed not to have state. The architecture is:</p> <p>Website</p> <p>===Physical Layer==</p> <p>Main Service</p> <p>==Physical Layer==</p> <p>Server 1/Service 2/Service 3/Service 4</p> <p>Only Server 1,Service 2,Service 3 and Service 4 can talk to the database and the Main Service calls the correct service based on products ordered. Every physical layer is load balanced too.</p> <p>Now when I develop a new service, I try to think DDD in that service even though it doesn't really feel like it fits. </p> <p>I use good DDD principles like entities, value types, repositories, aggregates, factories and etc.</p> <p>I've even tried using ORM's but they just don't seem like they fit in a stateless architecture. I know there are ways around it, for example use IStatelessSession instead of ISession with NHibernate. However, ORM just feel like they don't fit in a stateless architecture. </p> <p>I've noticed I really only use some of the concepts and patterns DDD has taught me but the overall architecture is still SOA. </p> <p>I am starting to think DDD doesn't fit in large systems but I do think some of the patterns and concepts do fit in large systems.</p> <p>Like I said, maybe I'm just not grasping DDD or maybe I'm over analyzing my designs? Maybe by using the patterns and concepts DDD has taught me I am using DDD? Not sure if there is really a question to this post but more of thoughts I've had when trying to figure out where DDD fits in overall systems and how scalable it truly is. The truth is, I don't think I really even know what DDD is? </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJoseph Daigle
    1. USnull_pointer
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POService Oriented Architecture & Domain-Driven Design
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POService Oriented Architecture & Domain-Driven Design
      1. USRandy Levy
      1. VTFavorite
    3. VO
      singulars
      1. POService Oriented Architecture & Domain-Driven Design
      1. This table or related slice is empty.
      1. VTUpMod
    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