How jgmelon22/fileuploaderdocspider works
Project type and purpose
• This is a full-stack ASP.NET Core MVC application (“FileUploaderDocspider”) that implements CRUD operations for uploading and managing documents.
• It follows a clean, layered architecture (Web → Application → Core → Infrastructure), backed by PostgreSQL, and uses Entity Framework Core plus MediatR for command/query handling.
File structure
• FileUploaderDocspider.Web: ASP.NET Core MVC project (Controllers, Views, static assets, DI setup in Startup/Program).
• FileUploaderDocspider.Application: Mediator-based command/query definitions and handlers (Create, Update, Delete, GetAll, GetById).
• FileUploaderDocspider.Core: Domain models (Document), view-models, mapping extensions, shared Result<T> type.
• FileUploaderDocspider.Infrastructure: EF Core DbContext, entity configuration, repository & service implementations, database migrations.
• UnitTests: xUnit/Moq tests for Application layer handlers and Web controllers.
Architectural patterns & design principles
• Layered/Clean Architecture: Clear separation of concerns across Web, Application, Core, Infrastructure.
• Mediator Pattern (via NetDevPack.SimpleMediator): decouples controllers from business logic by sending commands/queries to handlers.
• Repository Pattern: IDocumentRepository abstracts data access behind EF Core.
• Dependency Injection: Wired in Startup, all components registered via IocExtensions.
Main components & their interactions
a. Presentation Layer (Web MVC)
• Controllers (DocumentController, HomeController) accept HTTP requests.
• Controllers call IMediator.Send(Create/Update/DeleteDocumentCommand or GetAll/GetByIdDocumentQuery).
• Views render HTML and include Bootstrap, jQuery for client-side behavior and file uploads.
b. Application Layer
• Command/Query objects define operations.
• Handlers implement business rules (e.g., unique title, file type validation, max length).
• Handlers call domain-agnostic services (IDocumentService) or repositories.
c. Domain/Core Layer
• Document aggregate (ID, Title, Description, FileName, CreatedAt).
• ViewModels for data transfer to/from the UI.
• MappingExtensions to map between Domain and ViewModels.
d. Infrastructure Layer
• AppDbContext with DbSet<Document> and Fluent API configurations (DocumentConfiguration).
• DocumentRepository implements IDocumentRepository using EF Core.
• DocumentService implements IDocumentService to encapsulate higher-level data operations.
• Migrations target PostgreSQL.
e. Database
• PostgreSQL for persistence, accessed via Npgsql provider in EF Core.
f. External/Supporting
• NetDevPack.SimpleMediator, EF Core NuGet packages, coverlet/xUnit/Moq for tests.
• Clear component labels (e.g., DocumentController, CreateDocumentCommandHandler).
• UI (Views, Controllers)
• Application (Mediators, Handlers)
• Domain (Models, Mappings)
• Infrastructure (Repositories, DbContext)
• Database
• Call out major NuGet/technologies at each layer boundary.