zkavtaskin/Domain-Driven-Design-Example
Domain Driven Design Example
Domain-Driven-Design-Example is a C# sample project and reference pattern that demonstrates how to structure business logic and domain models using domain-driven design principles. It implements enterprise application architecture patterns by isolating core business rules and domain entities from technical infrastructure concerns through bounded contexts.
The codebase implements core domain concepts using immutable value objects defined entirely by their attributes, alongside entities and application services. It coordinates external requests, transaction boundaries, and domain model interactions through a dedicated service workflow layer, while handling state changes through event-driven messaging to manage side effects across bounded system contexts.
The project includes web service integration for handling external client requests and incorporates shopping cart management workflows. Automated unit testing verifies core business rules and application behavior across isolated domain components without external dependencies.
Features
- Domain-Driven Designs - Implements clean domain-driven architecture by separating core business logic from technical infrastructure concerns.
- Domain Driven Design Samples - Provides a complete reference implementation demonstrating domain-driven design principles in C#.
- Application Service Orchestration - Coordinates external requests and transaction boundaries through a dedicated application service layer.
- Domain Model Implementations - Structures business entities, value objects, and core domain logic into clean layers.
- Enterprise Application Architectures - Isolates core business rules from infrastructure concerns using enterprise architectural patterns.
- Immutable HTTP Message - Represents domain concepts using immutable value objects defined entirely by their attributes.
- Business Logic Testing - Verifies business logic correctness through automated unit testing of isolated components.
- Isolated Layer Testing - Verifies core business rules and behavior through isolated automated unit tests without external dependencies.
- Domain Event Emission - Triggers domain events to handle side effects reliably across bounded system contexts.
- Backend Domain Events - Triggers messages on state changes to coordinate behavior across bounded contexts.
- Side Effect Decoupling - Handles state changes through event-driven messaging to manage side effects across bounded contexts.
