How matthewrenze/clean-architecture-demo works
Main Components
a) Core Layers (Inside-Out):
• Domain Layer (Center)
• Contains entities (Customer, Employee, Product, Sale)
• Pure business logic and domain models
• Application Layer
• Contains business use cases
• Implements CQRS pattern (Commands and Queries)
• Interface definitions
b) Infrastructure Layers (Outside):
• Presentation Layer (MVC)
• Service Layer (Web API)
• Infrastructure Layer
• Persistence Layer
Detailed Component Breakdown
a) Domain Layer (Center):
• Core entities: Customer, Employee, Product, Sale
• IEntity interface connection
b) Application Layer:
• Split into Commands and Queries sections
• Main use cases:
• Customer Queries
• Employee Queries
• Product Queries
• Sale Commands/Queries
c) Infrastructure Components:
• Persistence: DatabaseService, Configurations
• Infrastructure: InventoryService, Network
• Presentation: MVC Controllers
• Service: Web API Controllers
Cross-Cutting Concerns
• Common utilities and services
• Dependency Injection (StructureMap)
• Date services
• Testing infrastructure
Important Elements to Highlight
a) CQRS Pattern Implementation:
• Separation of Commands and Queries
• Query models vs. command models
b) Interface Boundaries:
• IDatabaseService
• IInventoryService
• Query/Command interfaces
c) Factory Patterns:
• SaleFactory
• ViewModelFactory
Technical Details
• Framework: .NET Framework 4.8
• Key Technologies:
• ASP.NET MVC 5.2
• Entity Framework 6.4
• StructureMap 4.7
Testing Components
• Test projects relationship
• SpecFlow specifications
• Unit test coverage
Notes
• Clean Architecture principles
• Dependency flow
• Key design decisions
Remember to maintain a balance between detail and clarity, focusing on the architectural boundaries and dependencies while avoiding overwhelming detail at the implementation level.