Please enable JavaScript.

Coggle requires JavaScript to display documents.

DDD - Coggle Diagram

- - - - put Repository in Domain Model violates Separation of Concerns
  - - - Infrastructure layer = low-level module
      - Application Layer, and the Domain Layer = high-level modules
  - - - pros: take advantage of many techstacks, such as ElasticSearch
    - - Synchronizing the Write Model with the Read Model
  - - - storing all Domain events in a consistent way
    - - The best way to overcome this situation is to take a snapshot from the aggregate and replay only the events in the eventstream that occurred after the snapshot was taken
- - - - Good for complex business (>30 use cases)
      - Grow and change often
  - - - Ubiquitous Language
        
        Domain Experts will be required to collaborate closely with developers, and developers will have to think in terms of the business
      - Strategic Design
      - TacticalDesign
  - - - is a workshop format for quickly exploring complex business domains
    - - the problem space
        
        Domains
        
        Subdomains
      - the solution space
        
        Bounded Contexts
        
        Context Maps
        
        Context Mappings
      - movements
        
        distributed architectures
        
        Microservices
        
        are implementations of Domain-Driven Design Bounded Contexts
        
        Self-Contained Systems
        
        Each SCS is an autonomous web application
        
        Each SCS is owned by one team
        
        Communication with other SCSs or third-party systems is asynchronous wherever possible
        
        An SCS should make its features usable to end users by its own
        
        an SCS should never share business code with other SCSs. To avoid tight coupling
- - - - static vs. self