EduardoPires/EquinoxProject
EquinoxProject
EquinoxProject is an ASP.NET 9 web application template and reference implementation for building enterprise software. It provides a structural boilerplate centered on clean architecture, domain-driven design, and the separation of read and write operations through a command query responsibility segregation framework.
The project incorporates event sourcing to track the history of business entities as a sequence of events for auditing and state reconstruction. It utilizes a layered approach to decouple business logic from external dependencies and frameworks.
The system includes capabilities for stateless token authentication to secure API endpoints and a fluent validation pipeline to enforce data integrity. It further supports the unit of work pattern for atomic transactions and automated architecture testing to verify structural boundaries and dependency rules.
Features
- Clean Architecture Frameworks - Serves as a reference implementation and template for building applications using Clean Architecture principles.
- ASP.NET Core Application Frameworks - Provides an opinionated architectural framework for building enterprise solutions using the ASP.NET Core stack.
- Command Query Responsibility Segregation Patterns - Implements Command Query Responsibility Segregation patterns to split data modification and retrieval into separate models.
- ASP.NET Core Solution Templates - Ships a standardized starter project implementing clean architecture patterns for .NET applications.
- CQRS Frameworks - Implements a framework that separates read and write operations to align software structure with business domains.
- State Tracking - Tracks the history of business entities as a sequence of events for auditing and state reconstruction.
- Event Sourcing - Incorporates event sourcing to store the state of business entities as a chronological sequence of immutable events.
- Scalability Patterns - Integrates CQRS patterns to improve data access performance and overall system scalability.
- Domain-Driven Designs - Utilizes Domain-Driven Design to structure the software around business domains using aggregate roots and domain events.
- Layered Architectures - Organizes code into distinct functional layers to keep the system maintainable and independent of external dependencies.
- Authentication and Security - Provides an integrated approach to securing web service endpoints and managing user identity.
- API Access Security - Secures web service access by verifying user identity through stateless JWT tokens.
- Token Authentication - Secures API endpoints using stateless token-based authentication to verify user identity.
- Validation Pipelines - Includes a fluent validation pipeline to enforce business rules and data integrity in the application layer.
- Dependency Boundary Enforcers - Uses automated tests to restrict project imports and verify that code adheres to structural architectural boundaries.
- Unit of Work Patterns - Implements the Unit of Work pattern to group multiple database operations into single atomic transactions.
- Architectural Boundary Testing - Provides automated architecture tests to ensure code adheres to defined dependency rules and structural boundaries.
- Fluent Validation Rules - Enforces data integrity using a fluent interface to ensure only valid information enters the system.
- Domain Driven Design Samples - Full stack application with Clean Architecture and event sourcing.
- Sample Projects - Full application with DDD, CQRS, and Event Sourcing.
