ArchitectPoc

This is a showcase project for a ddd macro architecture implemented with nx and angular.

We have prepared two different approaches, each with different levels of abstraction. The level of abstraction is the main driver for maintainability, DX and code complexity.

You'll find the extended layered architecture over here

Simple Layered Architecture

Design Decisions & Patterns

We focus on maximum developer speed by removing all abstraction layers.

• Separation of Concerns (domain driven feature libraries)
• Domain Driven Design
• (simplified) Layered Architecture

Comparison to Extended Layered Architecture

• removed abstraction layer for DashboardFeatureState
• removed abstraction layer for DashboardSharedFeatureState
• removed use-cases library
• removed tokens since not needed anylonger
• moved Adapter logic directly to Components

Folder Structure and Constraints

dashboards/
    *domain/
        dashboard.model.ts
    *data/
      resource/
        dashboard.resource.ts <-- domain // does actual http calls
      store/
        dashboard.store.ts <-- domain // `DashboardFeatureState`
        dashboard-shared.store.ts <-- domain // `DashboardSharedFeatureState`
      index.ts
    public/
        *state
          public-dashboard-state.module.ts // `forRoot` defining @ddd/dashboard/data tokens.ts
          index.ts  // re-export domain, shared state

       *feature-list/
           list/
               feature-list.component.ts
               feature-list.adapter.ts <-- @ddd/dashboard/data // local provided `DashboardListAdapter`
           feature-list-module.ts

       *feature-show/
          show/
            feature-show.component.ts
            feature-show.adapter.ts <-- @ddd/dashboard/data // local provided `DashboardShowAdapter`
          feature-show-module.ts

       *ui/
        components/
          ui-dashboard-list.component.ts (display only)
        patterns/
        tokens/

Data Sharing and UI workflow Comparison