How gurau-anil/libmanease works
Project Type and Purpose
• Full-stack library-management application
• Implements Onion Architecture to isolate business rules from infrastructure and presentation
• Backend: ASP.NET Core Web API
• Frontend: Angular SPA
File Structure and Layers
• Presentation Layer
– LibManEase.Api (Controllers, HTTP endpoints)
– LibManEase.Client (Angular project)
• Dependency Injection
– LibManEase.DependencyInjection (resolves services across layers)
• Application Layer
– LibManEase.Application.Abstraction (DTOs, service & logger interfaces)
– LibManEase.Application (service implementations, FluentValidation, AutoMapper mappings)
• Domain Layer
– LibManEase.Domain (entity classes, repository interfaces)
• Infrastructure Layer
– LibManEase.Infrastructure (EF Core DbContext, repository implementations, Serilog logger, migrations)
• Angular Client (UI)
• Web API
– Controllers
– Dependency Resolver (DI container)
• Application Services
– IBookService, IMemberService, ILoanService and their implementations
– Validation & Mapping subcomponents
• Domain Entities & Interfaces
– Book, Member, Loan entities
– IRepository<T>, IBookRepository, etc.
• Infrastructure
– ApplicationDbContext (EF Core)
– Concrete repositories
– SerilogLogger
– Database (SQL Server or equivalent)
• External/Supporting Services
– Configuration (appsettings.json)
– HTTP client(s) if any (e.g., WeatherForecast sample)
Relationships and Data Flow
• Angular → HTTP calls → API Controllers
• Controller invokes → Application Services (via interfaces)
• Service uses → Domain Entities & Repository interfaces
• DependencyResolver binds → Service interfaces to implementations
• Repository implementation uses → DbContext → Database
• Cross-cutting concerns (Logging via IAppLogger/Serilog)
Architectural Patterns and Principles to Highlight
• Onion Architecture (layers depend only inward)
• Dependency Injection (inversion of control container in .DependencyInjection)
• Repository Pattern (abstraction of data access)
• DTOs & AutoMapper (mapping between domain and transport models)
• FluentValidation (input validation in Application layer)
Detailed Capture of Essential Architecture
• Do not omit the DependencyResolver layer—show how it wires interfaces to implementations
• Data-flow through AutoMapper & FluentValidation in the Application layer
• EF Core Migrations under Infrastructure to show schema management
• Configuration files (appsettings.json) feeding into the API for environment settings