# katereverie/librarymanager architecture

> Architecture diagram of the GitHub repository katereverie/librarymanager, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-04-18). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/katereverie/librarymanager
- Repository: https://github.com/katereverie/librarymanager

## Overview

##### Project type and purpose
- This is a full‑stack, cross‑platform Library Management system built in C#/.NET with two UIs (Console & MVC), a Web API, a business‑logic layer, a data‑access layer, and unit tests.
- Its goal is to let users manage borrowers, media, and checkouts via console, web UI, or external HTTP clients (Swagger/Postman).

##### File structure
- Top‑level projects:
– LibraryManager.Core: domain entities, DTOs, repository/service interfaces
– LibraryManager.Data: Entity Framework & Dapper repository implementations, DbContext
– LibraryManager.Application: concrete business services (BorrowerService, MediaService, CheckoutService), ServiceFactory for DI
– LibraryManager.WebApi: REST controllers exposing HTTP endpoints, Swagger, model validation
– LibraryManager.MVC: ASP.NET Core MVC web UI with controllers/views, calls Application layer directly via DI
– LibraryManager.ConsoleUI: Console app, holds API client implementations to talk over HTTP to WebApi
– LibraryManager.Tests.Unit: NUnit tests for services, using mock repositories
- Configuration files (appsettings.json, launchSettings.json), indicating separate runtime configs per tier.

##### README for additional insights
- Confirms an n‑tier architecture: UI, API, Application, Core, Data, UnitTest.
- Tech stack: ASP.NET Core (Web API & MVC), EF Core, Dapper, Swagger, FluentValidation, SQL Server.

##### Main components and interactions
a. Components:
1) ConsoleUI (Console app)
2) MVC (Web UI)
3) Web API
4) Application Layer (business services)
5) Core (domain entities & interfaces)
6) Data Layer (EF & Dapper repos, DbContext)
7) SQL Server Database
8) UnitTest project (not in runtime, but useful to show for completeness)
b. Relationships:
– ConsoleUI → HTTP → Web API Controllers
– MVC Controllers → direct in‑process call → Application services
– Web API Controllers → in‑process → Application services
– Application services ←→ Core entities & repository interfaces
– Application services → repository implementations (Data Layer)
– Data Layer → SQL Server
– UnitTest → mocks Application/Core and verifies logic (no database)
c. Architectural patterns:
– n‑Tier separation (Presentation, API, Business, Data, Persistence)
– Dependency Injection via ServiceFactory + ASP.NET Core DI
– Repository pattern (interfaces in Core, implementations in Data)
– Strategy for dual data‑access (Dapper vs EF implementations)
d. Key technologies:
– ASP.NET Core MVC & Web API
– EF Core (ORM), Dapper (lightweight ORM)
– Swagger for API docs
– FluentValidation for input validation
– NUnit for unit tests
– Microsoft SQL Server

##### Elements
– Clear labels for each rectangle (component/project name)
- Presentation (e.g., blue rectangles)
- Business Logic (yellow)
- Data Access (orange)
– Notes on ports or protocols (e.g., HTTP/JSON for WebApi)

## Diagram (Mermaid)

```mermaid
flowchart TB
    subgraph "Presentation Layer"
        ConsoleUI["LibraryManager.ConsoleUI\n(Console App)"]:::presentation
        MVC["LibraryManager.MVC\n(ASP.NET MVC UI)"]:::presentation
    end

    subgraph "API Layer"
        WebApi["LibraryManager.WebApi\n(Web API)"]:::api
    end

    subgraph "Business Logic Layer"
        Application["LibraryManager.Application\n(Business Services)"]:::business
    end

    subgraph "Domain Layer"
        Core["LibraryManager.Core\n(Core Entities & Interfaces)"]:::dataaccess
    end

    subgraph "Data Access Layer"
        DataLayer["LibraryManager.Data\n(EF & Dapper Repos)"]:::dataaccess
    end

    SQLServer["SQL Server Database"]:::database

    subgraph "Unit Tests"
        UnitTests["LibraryManager.Tests.Unit"]:::tests
    end

    ConsoleUI -->|HTTP/JSON| WebApi
    MVC -->|"in-process"| Application
    WebApi -->|"in-process"| Application
    Application -->|"uses"| Core
    Application -->|"uses"| DataLayer
    DataLayer -->|"connects"| SQLServer
    UnitTests -.-> Application
    UnitTests -.-> Core

    click ConsoleUI "https://github.com/katereverie/librarymanager/blob/main/LibraryManager.ConsoleUI"
    click MVC "https://github.com/katereverie/librarymanager/blob/main/LibraryManager.MVC"
    click WebApi "https://github.com/katereverie/librarymanager/blob/main/LibraryManager.WebApi"
    click Application "https://github.com/katereverie/librarymanager/blob/main/LibraryManager.Application/ServiceFactory.cs"
    click Core "https://github.com/katereverie/librarymanager/tree/main/LibraryManager.Core/Interfaces"
    click DataLayer "https://github.com/katereverie/librarymanager/blob/main/LibraryManager.Data/LibraryContext.cs"
    click UnitTests "https://github.com/katereverie/librarymanager/blob/main/LibraryManager.Tests.Unit/BorrowerServiceTests.cs"

    classDef presentation fill:#ADD8E6,stroke:#333,stroke-width:1px
    classDef api fill:#98FB98,stroke:#333,stroke-width:1px
    classDef business fill:#F0E68C,stroke:#333,stroke-width:1px
    classDef dataaccess fill:#FFDEAD,stroke:#333,stroke-width:1px
    classDef database fill:#D3D3D3,stroke:#333,stroke-width:1px,shape:cylinder
    classDef tests fill:#DCDCDC,stroke:#333,stroke-width:1px,stroke-dasharray: 5 5
```
