How spicycoder/cicdtemplate works
Main Components
a. Application Layers (Clean Architecture):
• API Layer (Presentation)
• Application Layer (Use Cases)
• Domain Layer (Business Logic)
• Infrastructure Layer (Data & External Services)
b. Cloud Native Components:
• DAPR Building Blocks
• .NET Aspire Dashboard
• Kubernetes Resources
• Docker Containers
┌─ Client Layer ─────────────────────────────────┐
• API Endpoints │
• Presentation Layer ──────────────────────────┐ │
• CICDTemplate.Api │ │
• Application Layer ──────────────────────────┐ │ │
• CQRS (Commands/Queries) │ │ │
• Validation Behaviors │ │ │
• Domain Layer ─────────────────────────────┐ │ │ │
• Entities, Repositories │ │ │ │
• Infrastructure Layer ────────────────────┐ │ │ │ │
• Database, Cache, External Services │ │ │ │ │
• ┴─┴─┴─┘
DAPR Sidecars and Building Blocks
• DAPR building blocks:
• State Store
• Pub/Sub
• Secret Store
• Configuration Store
Key Relationships
a. Internal Flow:
• API Controllers → Application Commands/Queries
• Application Layer → Domain Layer
• Domain Layer → Infrastructure Layer
b. External Interactions:
• API → DAPR Sidecar
• DAPR Sidecar → Building Blocks
• Infrastructure → External Services
Additional Elements
a. DevOps Components:
• GitHub Actions Workflows
• Docker Containers
• Kubernetes Deployments
b. Testing Components:
• Unit Tests
• Functional Tests
• Architecture Tests
Specific Implementation Details
Key architectural patterns:
• CQRS pattern (Commands/Queries folders)
• Mediator pattern (MediatR usage)
• Repository pattern
• Clean Architecture layers
Notes
• Clean architecture boundaries
• Clear separation of concerns
• Cloud-native aspects
• Deployment topology
• Testing boundaries
Remember to include version information for key components:
• ASP.NET 9
• .NET Aspire
• DAPR
• Docker
• Kubernetes
This will provide a comprehensive view of the system while maintaining the clean architecture principles and cloud-native capabilities that are central to this template.